How do I detect a click outside an element?

You can listen for a click event on document and then make sure #dropdownmenu is not an ancestor or the target of the clicked element by using .closest().

$(document).click(function(event) { 
  $target = $(event.target);
  if(!$target.closest('#dropdownmenu').length && 
  $('#dropdownmenu').is(":visible")) {
    $('#dropdownmenu').hide();
  }        
});

For those who don’t want to use jQuery. Here’s the above code in plain vanillaJS (ECMAScript6).

function hideOnClickOutside(element) {
    const outsideClickListener = event => {
        if (!element.contains(event.target) && isVisible(element)) { // or use: event.target.closest(selector) === null
          element.style.display = 'none'
          removeClickListener()
        }
    }

    const removeClickListener = () => {
        document.removeEventListener('click', outsideClickListener)
    }

    document.addEventListener('click', outsideClickListener)
}

const isVisible = elem => !!elem && !!( elem.offsetWidth || elem.offsetHeight || elem.getClientRects().length ) // source (2018-03-11): https://github.com/jquery/jquery/blob/master/src/css/hiddenVisibleSelectors.js

Source: https://stackoverflow.com/questions/152975/how-do-i-detect-a-click-outside-an-element

Generating a WordPress plugin activation link url

As I might need it again I’ve put together a gist for a WordPress function that will generate a plugin activation url like the ones WordPress will generate in the plugins administration screen

Activate link

The function will require a string input like my-plugin/my-plugin.php which can be hard-coded knowing a specific plugin folder and main plugin file information or using another function that will check for an installed plugin using its title.

/**
 * Generate an activation URL for a plugin like the ones found in WordPress plugin administration screen.
 *
 * @param  string $plugin A plugin-folder/plugin-main-file.php path (e.g. "my-plugin/my-plugin.php")
 *
 * @return string         The plugin activation url
 */
function generatePluginActivationLinkUrl($plugin)
{
    // the plugin might be located in the plugin folder directly

    if (strpos($plugin, '/')) {
        $plugin = str_replace('/', '%2F', $plugin);
    }

    $activateUrl = sprintf(admin_url('plugins.php?action=activate&plugin=%s&plugin_status=all&paged=1&s'), $plugin);

    // change the plugin request to the plugin to pass the nonce check
    $_REQUEST['plugin'] = $plugin;
    $activateUrl = wp_nonce_url($activateUrl, 'activate-plugin_' . $plugin);

    return $activateUrl;
}

Source: https://www.theaveragedev.com/generating-a-wordpress-plugin-activation-link-url/

How to retrieve all localStorage items without knowing the keys in advance?

Show all of the keys and storage written before.

function allStorage() {

    var values = [],
        keys = Object.keys(localStorage),
        i = keys.length;

    while ( i-- ) {
        values.push( localStorage.getItem(keys[i]) );
    }

    return values;
}

OR

function allStorage() {

    var archive = {}, // Notice change here
        keys = Object.keys(localStorage),
        i = keys.length;

    while ( i-- ) {
        archive[ keys[i] ] = localStorage.getItem( keys[i] );
    }

    return archive;
}

Creating NGINX Rewrite Rules

Comparing the returnrewrite, and try_filesDirectives

The two directives for general‑purpose NGINX rewrite are return and rewrite, and the try_files directive is a handy way to direct requests to application servers. Let’s review what the directives do and how they differ.

The return Directive

The return directive is the simpler of the two general‑purpose directives and for that reason we recommend using it instead of rewrite when possible (more later about the why and when). You enclose the return in a server or location context that specifies the URLs to be rewritten, and it defines the corrected (rewritten) URL for the client to use in future requests for the resource.

Here’s a very simple example that redirects clients to a new domain name:

server {
    listen 80;
    listen 443 ssl;
    server_name www.old-name.com;
    return 301 $scheme://www.new-name.com$request_uri;
}

Source: https://www.nginx.com/blog/creating-nginx-rewrite-rules/

Tool: http://www.anilcetin.com/

How to replace post name slug with post ID in Custom Post Types

Here is a way to replace the post slug with the post ID in a custom post type permalink structure.

Example.

Change

somedomain.com/some-permalink 

To

somedomain.com/123

Assuming the post type already exists with

'rewrite' => array('slug' => 'book') ...
/**
 * Add new rewrite for post type
 * Add permalink structure
 */
function book_post_type_rewrite() {
    global $wp_rewrite;
 
    // Set the query arguments used by WordPress
    $queryarg = 'post_type=book&p=';
 
    // Concatenate %book_id% to $queryarg (eg.. &p=123)
    $wp_rewrite->add_rewrite_tag( '%book_id%', '([^/]+)', $queryarg );
 
    // Add the permalink structure
    $wp_rewrite->add_permastruct( 'book', '/book/%book_id%/', false );
}
add_action( 'init', 'book_post_type_rewrite' );
 
/**
 * Replace permalink segment with post ID
 *
 */
function book_post_type_permalink( $post_link, $id = 0, $leavename ) {
    global $wp_rewrite;
    $post = get_post( $id );
    if ( is_wp_error( $post ) )
        return $post;
 
        // Get post permalink (should be something like /book/%book_id%/
        $newlink = $wp_rewrite->get_extra_permastruct( 'book' );
 
        // Replace %book_id% in permalink structure with actual post ID
        $newlink = str_replace( '%book_id%', $post->ID, $newlink );
        $newlink = home_url( user_trailingslashit( $newlink ) );
    return $newlink;
}
add_filter('post_type_link', 'book_post_type_permalink', 1, 3);

Refresh permalinks

Refer http://stackoverflow.com/questions/25199501/wordpress-custom-type-append-post-id-at-the-end?answertab=votes#tab-top