[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f8MiLiCysB6t-vEZLzOfFoNYMOOTqoPyzWB6paupXfxA":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"vicchi","https:\u002F\u002Fprofiles.wordpress.org\u002Fvicchi\u002F",4,70,85,30,84,"2026-04-04T16:24:41.001Z",[13,36,55,73],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":9,"downloaded":19,"rating":20,"num_ratings":21,"last_updated":22,"tested_up_to":23,"requires_at_least":24,"requires_php":25,"tags":26,"homepage":31,"download_link":32,"security_score":8,"vuln_count":33,"unpatched_count":33,"last_vuln_date":34,"fetched_at":35},"wp-avertere","WP Avertere","1.1.0","\u003Cp>This plugin allows you to easily set up redirections from the URL of any post, page or other post type on your WordPress site to another URL, either on your site or external to your site. Redirections can either be permanent (HTTP 301) or temporary (HTTP 302) and can easily be changed or deleted entirely.\u003C\u002Fp>\n\u003Cp>Settings and options include:\u003C\u002Fp>\n\u003Col>\n\u003Cli>The URL you want to redirect to.\u003C\u002Fli>\n\u003Cli>The type of redirection, permanent or temporary\u003C\u002Fli>\n\u003Cli>Validation of the redirect URL to ensure it is well formed.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>In addition to setting up a redirect, the plugin replaces the original post’s or page’s permalink with the redirected permalink or external URL; when you hover your mouse pointer over a redirected permalink you will see the new permalink or external URL not the original.\u003C\u002Fp>\n\u003Cp>Once installed and activated, the plugin adds a \u003Cem>Redirect This Post\u002FPage\u002Fetc\u003C\u002Fem> meta box to the admin \u003Cem>Edit Post\u002FPage\u003C\u002Fem>. Simply create a new post, or edit an existing one, add the URL you want to redirect to (copying and pasting is a good idea here to ensure there’s no typing errors), choose whether the redirection is permanent or temporary, click on the \u003Cem>Check URL\u003C\u002Fem> button to ensure your URL is well formed and save the post. You’re done.\u003C\u002Fp>\n\u003Cp>While the main use of the plugin is to redirect posts and pages, you can also use it to:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Convert a post to a page; useful for when the post needs to be kept updated regularly and is more suited to be a page on your site.\u003C\u002Fli>\n\u003Cli>Add a menu bar link to an external site; you can create a new blank page as a menu bar link and then redirect that page to the external URL with no need to edit any code in your theme’s \u003Ccode>functions.php\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>Create a shortcut category or tag archive link; you can create a new blank page, such as \u003Ccode>\u002Fplugins\u003C\u002Fcode> and then redirect that page to \u003Ccode>\u002Ftags\u002Fplugins\u003C\u002Fcode>.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Filter Support And Usage\u003C\u002Fh3>\n\u003Cp>WP Avertere supports a single filter, \u003Ccode>wp_avertere_protocols\u003C\u002Fcode> that allows you to change the set of acceptable URL protocols that WordPress and the plugin permits.\u003C\u002Fp>\n\u003Cp>\u003Cem>Example:\u003C\u002Fem> Add support for GitHub repositories to the plugin.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_filter ('wp_avertere_protocols', 'add_github_protocol');\n\nfunction add_github_protocol ($protocols) {\n    \u002F\u002F protocols = array ('name', 'name', ...)\n    $protocols[] = 'git';\n\n    return $protocols;\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Set up and manage an HTTP 301\u002F302 Redirect from the URL of any post type to another URL, either on your site or externally.",3435,100,1,"2012-11-08T14:32:00.000Z","3.4.2","3.4","",[27,28,29,30,14],"301","http","redirect","redirection","http:\u002F\u002Fwww.vicchi.org\u002Fcodeage\u002Fwp-avertere\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-avertere.1.1.0.zip",0,null,"2026-03-15T15:16:48.613Z",{"slug":37,"name":38,"version":39,"author":4,"author_profile":5,"description":40,"short_description":41,"active_installs":42,"downloaded":43,"rating":20,"num_ratings":44,"last_updated":45,"tested_up_to":46,"requires_at_least":47,"requires_php":25,"tags":48,"homepage":53,"download_link":54,"security_score":8,"vuln_count":33,"unpatched_count":33,"last_vuln_date":34,"fetched_at":35},"wp-customizer","WP Customizer","1.0.2","\u003Cp>This plugin allows you to manage and load site specific functions, scripts and CSS files into your WordPress site without the need to edit your theme’s \u003Ccode>functions.php\u003C\u002Fcode> or any other source file.\u003C\u002Fp>\n\u003Cp>Settings and options include:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Choose the type of customization you want to load; functions, scripts, CSS in any combination.\u003C\u002Fli>\n\u003Cli>Choose where you want the customizations to load; in the WordPress front-end, in the WordPress admin screens or both.\u003C\u002Fli>\n\u003Cli>Choose where you want to store your customization files, without the need to add to or modify your theme’s or your plugin’s source files.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>Filter Support And Usage\u003C\u002Fh3>\n\u003Cp>WP Customizer supports multiple filters; the plugin’s filters allow you to\u003C\u002Fp>\n\u003Cul>\n\u003Cli>modify the set of functions files that are about to be loaded\u003C\u002Fli>\n\u003Cli>modify the set of script files that are about to be loaded\u003C\u002Fli>\n\u003Cli>modify the characteristics of each script file that is about to be loaded and which will be passed as arguments to \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FFunction_Reference\u002Fwp_enqueue_script\" rel=\"nofollow ugc\">\u003Ccode>wp_enqueue_script\u003C\u002Fcode>\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>modify the set of CSS files that are about to be loaded\u003C\u002Fli>\n\u003Cli>modify the characteristics of each CSS file that is about to be loaded and which will be passed as arguments to \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FFunction_Reference\u002Fwp_enqueue_style\" rel=\"nofollow ugc\">\u003Ccode>wp_enqueue_style\u003C\u002Fcode>\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Each filter will be only be called if the customization type is enabled in the plugin’s options; if a customization type is enabled but no files are found to be loaded, the filter will still be called but will be passed an empty argument.\u003C\u002Fp>\n\u003Cp>As with all WordPress filters, any filter hook function should either return the modified argument or the original argument if no modification were made.\u003C\u002Fp>\n\u003Ch4>wp_customizer_functions, wp_customizer_admin_functions, wp_customizer_common_functions\u003C\u002Fh4>\n\u003Cp>The \u003Cem>functions\u003C\u002Fem> filters are called when preparing to load the list of front-end functions (\u003Ccode>wp_customizer_functions\u003C\u002Fcode>), of admin functions (\u003Ccode>wp_customizer_admin_functions\u003C\u002Fcode>) and of common functions (\u003Ccode>wp_customizer_common_functions\u003C\u002Fcode>). The arguments that each filter hook function receives is identical in all cases. The filter hook function takes a single argument which is an array of file names.\u003C\u002Fp>\n\u003Cp>\u003Cem>Example:\u003C\u002Fem> Prevent all function files from loading by returning an empty file list.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_filter('wp_customizer_functions', 'function_handler', 10, 1);\n\nfunction function_handler($files) {\n    \u002F\u002F $files = array(\n    \u002F\u002F      array(\n    \u002F\u002F          'file' => (absolute path of function file)\n    \u002F\u002F      ),\n    \u002F\u002F      array(...)\n    \u002F\u002F  );\n\n    return array();\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>wp_customizer_scripts, wp_customizer_admin_scripts, wp_customizer_common_scripts\u003C\u002Fh4>\n\u003Cp>The \u003Cem>scripts\u003C\u002Fem> filters are called when preparing to load the list of front-end scripts (\u003Ccode>wp_customizer_scripts\u003C\u002Fcode>), of admin scripts (\u003Ccode>wp_customizer_admin_scripts\u003C\u002Fcode>) and of common scripts (\u003Ccode>wp_customizer_common_scripts\u003C\u002Fcode>). The arguments that each filter hook function receives is identical in all cases. The filter hook function takes a single argument which is an array of file details.\u003C\u002Fp>\n\u003Cp>\u003Cem>Example:\u003C\u002Fem> Add jQuery as a dependency to all scripts and enable each script to load in the post’s footer.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_filter('wp_customizer_scripts', 'script_handler', 10, 1);\n\nfunction script_handler($files) {\n    \u002F\u002F $files = array(\n    \u002F\u002F      array(\n    \u002F\u002F          'file' => (absolute path of script file),\n    \u002F\u002F          'handle' => (auto-generated handle for script),\n    \u002F\u002F          'src' => (URL of script file),\n    \u002F\u002F          'deps' => (dependencies, defaults to an empty array),\n    \u002F\u002F          'ver' => (version, defaults to false),\n    \u002F\u002F          'in_footer' => (load in footer, defaults to false),\n    \u002F\u002F      ),\n    \u002F\u002F      array(...)\n    \u002F\u002F );\n\n    foreach ($files as $file) {\n        $file['deps'] = array('jquery');\n        $file['in_footer'] = true;\n    }\n\n    return $files;\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>wp_customizer_css, wp_customizer_admin_css, wp_customizer_common_css\u003C\u002Fh4>\n\u003Cp>The \u003Cem>CSS\u003C\u002Fem> filters are called when preparing to load the list of front-end CSS (\u003Ccode>wp_customizer_css\u003C\u002Fcode>), of admin CSS (\u003Ccode>wp_customizer_admin_css\u003C\u002Fcode>) and of common CSS (\u003Ccode>wp_customizer_common_css\u003C\u002Fcode>). The arguments that each filter hook function receives is identical in all cases. The filter hook function takes a single argument which is an array of file details.\u003C\u002Fp>\n\u003Cp>\u003Cem>Example:\u003C\u002Fem> Override the media type for all CSS files to use the \u003Ccode>screen\u003C\u002Fcode> media type.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_filter('wp_customizer_css', 'css_handler', 10, 1);\n\nfunction css_handler($files) {\n    \u002F\u002F $files = array(\n    \u002F\u002F      array(\n    \u002F\u002F          'file' => (absolute path of css file),\n    \u002F\u002F          'handle' => (auto-generated handle for CSS),\n    \u002F\u002F          'src' => (URL of CSS file),\n    \u002F\u002F          'deps' => (dependencies, defaults to an empty array),\n    \u002F\u002F          'ver' => (version, defaults to false),\n    \u002F\u002F          'media' => (media type, defaults to 'all')\n    \u002F\u002F      ),\n    \u002F\u002F      array(...)\n    \u002F\u002F );\n\n    foreach ($files as $file) {\n        $file['media'] = 'screen';\n    }\n\n    return $files;\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Easily load site specific functions, scripts and CSS files into your site without editing your theme's functions.php or other source files.",20,4421,2,"2017-11-09T17:31:00.000Z","4.8.28","4.8",[49,50,51,52,37],"customise","customize","functions","scripts","http:\u002F\u002Fwww.vicchi.org\u002Fcodeage\u002Fwp-customizer\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-customizer.1.0.2.zip",{"slug":56,"name":57,"version":58,"author":4,"author_profile":5,"description":59,"short_description":60,"active_installs":61,"downloaded":62,"rating":33,"num_ratings":33,"last_updated":63,"tested_up_to":64,"requires_at_least":65,"requires_php":25,"tags":66,"homepage":71,"download_link":72,"security_score":8,"vuln_count":33,"unpatched_count":33,"last_vuln_date":34,"fetched_at":35},"wp-quadratum","WP Quadratum","1.3.1.4","\u003Cp>This plugin allows you to display your last Swarm checkin as a map widget on the sidebar or embedded via a shortcode in a post or page of your WordPress powered site.\u003C\u002Fp>\n\u003Cp>Setting and options include:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Associate your WordPress powered site with your \u003Ca href=\"https:\u002F\u002Ffoursquare.com\u002F\" rel=\"nofollow ugc\">Foursquare\u003C\u002Fa> account using \u003Ca href=\"http:\u002F\u002Foauth.net\u002F2\u002F\" rel=\"nofollow ugc\">OAuth 2.0\u003C\u002Fa>, which keeps your personal information safe and secure.\u003C\u002Fli>\n\u003Cli>Choose which map provider you want your checkin shown on; you can choose from:\n\u003Col>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fdeveloper.here.com\u002Fjavascript_api\" rel=\"nofollow ugc\">HERE Maps\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdevelopers.google.com\u002Fmaps\u002Fdocumentation\u002Fjavascript\u002F\" rel=\"nofollow ugc\">Google Maps v3\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fmsdn.microsoft.com\u002Fen-us\u002Flibrary\u002Fgg427610.aspx\" rel=\"nofollow ugc\">Bing Maps v7\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fwww.openstreetmap.org\" rel=\"nofollow ugc\">OpenStreetMap\u003C\u002Fa> from \u003Ca href=\"http:\u002F\u002Fleafletjs.com\u002F\" rel=\"nofollow ugc\">Leaflet\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"http:\u002F\u002Fwww.openstreetmap.org\" rel=\"nofollow ugc\">OpenStreetMap\u003C\u002Fa> from \u003Ca href=\"http:\u002F\u002Fopenlayers.org\" rel=\"nofollow ugc\">OpenLayers\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\" rel=\"nofollow ugc\">OpenStreetMap\u003C\u002Fa> from \u003Ca href=\"http:\u002F\u002Fdeveloper.mapquest.com\u002Fweb\u002Fproducts\u002Fopen\u002Fsdk\" rel=\"nofollow ugc\">MapQuest\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Fol>\n\u003C\u002Fli>\n\u003Cli>Add your maps API key(s) for your chosen map provider; HERE, Google, Bing and MapQuest maps all require API keys.\u003C\u002Fli>\n\u003Cli>Choose the width and height of the widget and map on the sidebar. The width and height can be specified either as pixels (\u003Ccode>px\u003C\u002Fcode>) or as a percentage.\u003C\u002Fli>\n\u003Cli>Choose the zoom level of the map display.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>The \u003Cem>strapline\u003C\u002Fem> text containing the venue name, venue URL and timestamp of your last Swarm checkin can be customised via the plugin’s filters. See the \u003Cem>Filter Support And Usage\u003C\u002Fem> section for more information.\u003C\u002Fp>\n\u003Cp>The current version of this plugin allows you to associate a single Foursquare account with your WordPress site; associating multiple Foursquare accounts, one per user account is not currently supported.\u003C\u002Fp>\n\u003Ch3>Shortcode Support And Usage\u003C\u002Fh3>\n\u003Cp>WP Quadratum supports two shortcodes and three shortcode aliases; \u003Ccode>[wp_quadratum_map]\u003C\u002Fcode> to expand the shortcode in a post or page and replace it with the checkin map and \u003Ccode>[wp_quadratum_locality]\u003C\u002Fcode> to allow you to embed aspects of your last checkin in a post or page.\u003C\u002Fp>\n\u003Ch4>[wp_quadratum_map]\u003C\u002Fh4>\n\u003Cp>Adding this shortcode to the content of a post or page as content, expands the shortcode and replaces it with a checkin map.\u003C\u002Fp>\n\u003Cp>The shortcode also supports multiple \u003Cem>attributes\u003C\u002Fem> which allow you to customise the way in which the shortcode is expanded into the checkin map:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>the \u003Ccode>width\u003C\u002Fcode> attribute\u003C\u002Fli>\n\u003Cli>the \u003Ccode>width_units\u003C\u002Fcode> attribute\u003C\u002Fli>\n\u003Cli>the \u003Ccode>height\u003C\u002Fcode> attribute\u003C\u002Fli>\n\u003Cli>the \u003Ccode>height_units\u003C\u002Fcode> attribute\u003C\u002Fli>\n\u003Cli>the \u003Ccode>zoom\u003C\u002Fcode> attribute\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>** The “width” Attribute **\u003C\u002Fp>\n\u003Cp>The \u003Ccode>width\u003C\u002Fcode> attribute, in conjunction with the \u003Ccode>height\u003C\u002Fcode> attribute specifies the width of the map to be inserted into a post or page. If omitted, the map width defaults to a value of \u003Ccode>300\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>** The “width_units” Attribute **\u003C\u002Fp>\n\u003Cp>The \u003Ccode>width_units\u003C\u002Fcode> attribute, specifies how the value specified in the \u003Ccode>width\u003C\u002Fcode> attribute should be interpreted. Valid values for this attribute as \u003Ccode>px\u003C\u002Fcode> and \u003Ccode>%\u003C\u002Fcode>, denoting that the \u003Ccode>width\u003C\u002Fcode> attribute should be interpreted in pixels or as a percentage respectively. If omitted, this attribute defaults to a value of \u003Ccode>px\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>** The “height” Attribute **\u003C\u002Fp>\n\u003Cp>The \u003Ccode>height\u003C\u002Fcode> attribute, in conjunction with the \u003Ccode>width\u003C\u002Fcode> attribute specifies the height of the map to be inserted into a post or page. If omitted, the map height defaults to a value of \u003Ccode>300\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>** The “height_units” Attribute **\u003C\u002Fp>\n\u003Cp>The \u003Ccode>height_units\u003C\u002Fcode> attribute, specifies how the value specified in the \u003Ccode>height\u003C\u002Fcode> attribute should be interpreted. Valid values for this attribute as \u003Ccode>px\u003C\u002Fcode> and \u003Ccode>%\u003C\u002Fcode>, denoting that the \u003Ccode>height\u003C\u002Fcode> attribute should be interpreted in pixels or as a percentage respectively. If omitted, this attribute defaults to a value of \u003Ccode>px\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>** The “zoom” Attribute **\u003C\u002Fp>\n\u003Cp>The \u003Ccode>zoom\u003C\u002Fcode> attribute specifies the zoom level to be used when displaying the checkin map. If omitted, the zoom level defaults to a value of \u003Ccode>16\u003C\u002Fcode> which is roughly analogous to a neighbourhood zoom.\u003C\u002Fp>\n\u003Ch4>[wp_quadratum]\u003C\u002Fh4>\n\u003Cp>The \u003Ccode>[wp_quadratum]\u003C\u002Fcode> shortcode is an alias for the \u003Ccode>[wp_quadratum_map]\u003C\u002Fcode> shortcode and has the same functionality.\u003C\u002Fp>\n\u003Ch4>[wpq_map]\u003C\u002Fh4>\n\u003Cp>The \u003Ccode>[wpq_map]\u003C\u002Fcode> shortcode is an alias for the \u003Ccode>[wp_quadratum_map]\u003C\u002Fcode> shortcode and has the same functionality.\u003C\u002Fp>\n\u003Ch4>[wp_quadratum_locality]\u003C\u002Fh4>\n\u003Cp>Adding this shortcode to the content of a post or page, expands the shortcode and replaces it with information about your last Foursquare checkin. The information to be displayed is selected by the shortcode’s \u003Ccode>type\u003C\u002Fcode> attribute, which allows you to select the venue name, address, region, postal code, coordinates, timezone or timezone offset.\u003C\u002Fp>\n\u003Cp>By default, the \u003Ccode>[wp_quadratum_locality]\u003C\u002Fcode> shortcode and the \u003Ccode>[wpq_locality]\u003C\u002Fcode> alias are disabled. This is because not all Foursquare venues contain the full scope of locality elements that the shortcode supports (the minimum requirements for a Foursquare venue are name, category and coordinates). To backfill any missing venue elements, WP Quadratum uses a \u003Cem>reverse geocoding\u003C\u002Fem> service from \u003Ca href=\"http:\u002F\u002Fwww.factual.com\u002F\" rel=\"nofollow ugc\">Factual\u003C\u002Fa> to supply the missing information.\u003C\u002Fp>\n\u003Cp>To enable the \u003Ccode>[wp_quadratum_locality]\u003C\u002Fcode> shortcode, from the Dashboard navigate to \u003Cem>Settings \u002F WP Quadratum\u003C\u002Fem> and click on the \u003Cem>Shortcodes\u003C\u002Fem> tab. Select the \u003Cem>Enable Locality Shortcode Usage\u003C\u002Fem> checkbox and the \u003Cem>Factual OAuth Settings\u003C\u002Fem> meta-box will appear. You’ll then need to sign up for a \u003Ca href=\"https:\u002F\u002Fwww.factual.com\u002Fapi-keys\u002Frequest\" rel=\"nofollow ugc\">Factual API key\u003C\u002Fa> after which you’ll be given an \u003Cem>OAuth Key\u003C\u002Fem> and \u003Cem>OAuth Secret\u003C\u002Fem>. Copy and paste these into the \u003Cem>Factual OAuth\u003C\u002Fem> text fields and click on \u003Cem>Save Shortcode Settings\u003C\u002Fem>. You’ll now be able to use the \u003Ccode>[wp_quadratum_locality]\u003C\u002Fcode> shortcode or its alias.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>The “type” Attribute\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The \u003Ccode>type\u003C\u002Fcode> attribute specifies the element of your last Foursquare checkin that is to be displayed in a post or page and can take one of the following values:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>venue\u003C\u002Fcode> – the name of the last Foursquare venue you checked into.\u003C\u002Fli>\n\u003Cli>\u003Ccode>address\u003C\u002Fcode> – the street address of the venue; not including the region, locality or postal code.\u003C\u002Fli>\n\u003Cli>\u003Ccode>region\u003C\u002Fcode> – the region of the venue; the geographic context of the region will vary from country to country but is roughly analogous to the venue’s city.\u003C\u002Fli>\n\u003Cli>\u003Ccode>postcode\u003C\u002Fcode> – the postal code of the venue, if the country or region supports postal codes.\u003C\u002Fli>\n\u003Cli>\u003Ccode>coordinates\u003C\u002Fcode> – the geographic coordinates of the venue, in the form latitude,longitude.\u003C\u002Fli>\n\u003Cli>\u003Ccode>timezone\u003C\u002Fcode> – the timezone name of the time of the checkin, such as \u003Ccode>Europe\u002FLondon\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Ccode>tzoffset\u003C\u002Fcode> – the offset from GMT of the time of the checkin, in the form GMT[-+]hours, such as GMT-1 or GMT+2.\u003C\u002Fli>\n\u003Cli>\u003Ccode>locality\u003C\u002Fcode> – the locality of the venue; the geographic context of the locality will vary according to country, but is roughly analogous to the town or neighbourhood.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If the \u003Ccode>type\u003C\u002Fcode> attribute is not supplied, or if the value of this attribute is not one of the above values, \u003Ccode>type=\"locality\"\u003C\u002Fcode> will be assumed. The shortcode’s replacement value can be modified via the plugin’s \u003Ccode>wp_quadratum_locality\u003C\u002Fcode> filter; see the \u003Cem>Filter Support and Usage\u003C\u002Fem> section for more information.\u003C\u002Fp>\n\u003Ch4>[wpq_locality]\u003C\u002Fh4>\n\u003Cp>The \u003Ccode>[wpq_locality]\u003C\u002Fcode> shortcode is an alias for the \u003Ccode>[wp_quadratum_locality]\u003C\u002Fcode> shortcode and has the same functionality.\u003C\u002Fp>\n\u003Ch3>Filter Support And Usage\u003C\u002Fh3>\n\u003Cp>WP Quadratum supports three filters, which are described in more detail below. The plugin’s filters allow you to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>change the descriptive text that appears immediately below the map when displayed via the plugin’s widget or shortcode.\u003C\u002Fli>\n\u003Cli>gain access to the checkin metadata that is returned from the Foursquare API\u003C\u002Fli>\n\u003Cli>change the output of the [wp_quadratum_locality]` shortcode\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>wp_quadratum_checkin\u003C\u002Fh4>\n\u003Cp>Allow a filter hook function to gain access to the checkin metadata that is returned from the Foursquare API and which is used to build the checkin map and strapline. It’s important to note that the implementation of this filter isn’t strictly a WordPress filter per se. The user defined hook function is passed only the checkin metadata. Any changes made to the metadata will not be reflected in the output of the plugin’s or shortcode’s map, nor will any return value from the hook function be honoured by the plugin. The filter will be called before the \u003Ccode>wp_quadratum_strapline\u003C\u002Fcode> filter, if used, allowing you to store the checkin contents and use them within the \u003Ccode>wp_quadratum_strapline\u003C\u002Fcode> filter hook.\u003C\u002Fp>\n\u003Cp>The contents of the checkin data this filter can access are a \u003Ccode>Checkin Response\u003C\u002Fcode> object, which is documented on the \u003Ca href=\"https:\u002F\u002Fdeveloper.foursquare.com\u002Fdocs\u002Fresponses\u002Fcheckin\" rel=\"nofollow ugc\">Foursquare Developer Site\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cem>Example:\u003C\u002Fem> Store the contents of the Foursquare checkin that the plugin will be to display the checkin map.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$last_checkin = null;\nadd_filter('wp_quadratum_checkin', store_last_checkin, 10, 1);\nfunction store_last_checkin($checkin) {\n    $last_checkin = $checkin;\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>wp_quadratum_strapline\u003C\u002Fh4>\n\u003Cp>Applied to the strapline that is displayed via the plugin’s widget or shortcode. The strapline is the text that appears immediately below the checkin map.\u003C\u002Fp>\n\u003Cp>\u003Cem>Example:\u003C\u002Fem> Change the date and time formatting in the strapline\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_filter('wp_quadratum_strapline', 'format_strapline', 10, 2);\nfunction format_strapline($content, $params) {\n    \u002F\u002F $params = array (\n    \u002F\u002F      'venue-url' => '4Sq venue url for checkin',\n    \u002F\u002F      'venue-name' => 'checkin venue name',\n    \u002F\u002F      'checked-in-at' => 'timestamp of checkin'\n    \u002F\u002F  );\n\n    $strapline = '\u003Ch5>Last seen at \u003Ca href=\"' . $params['venue-url'] . '\" target=\"_blank\">' . $params['venue-name'] . '\u003C\u002Fa> on ' . date('l jS \\of F Y h:i:s A', $params['checked-in-at']) . '\u003C\u002Fh5>';\n    return $strapline;\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>wp_quadratum_locality\u003C\u002Fh4>\n\u003Cp>Applied to the replacement content of the \u003Ccode>[wp_quadratum_locality]\u003C\u002Fcode> shortcode immediately before the shortcode is replaced. The filter’s hook function is passed two arguments; the shortcode’s value and corresponding \u003Ccode>type\u003C\u002Fcode> attribute.\u003C\u002Fp>\n\u003Cp>\u003Cem>Example:\u003C\u002Fem> Wrap each invocation of the \u003Ccode>[wp_quadratum_locality]\u003C\u002Fcode> shortcode in a \u003Ccode>div\u003C\u002Fcode> whose class includes the attribute type.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_filter('wp_quadratum_locality', 'format_locality', 10, 2);\nfunction format_locality($value, $type) {\n    $class = 'wp-quadratum-locality-' . $type;\n    return '\u003Cdiv class=\"' . $class . '\">' . $value . '\u003C\u002Fdiv>';\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Display your last Swarm checkin as a map widget in the sidebar or embedded in a post or page, fully authenticated via OAuth 2.0.",10,3962,"2015-02-05T13:06:00.000Z","4.1.0","3.9.0",[67,68,69,70,56],"checkins","foursquare","map","maps","http:\u002F\u002Fwww.vicchi.org\u002Fcodeage\u002Fwp-quadratum\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-quadratum.1.3.1.4.zip",{"slug":74,"name":75,"version":16,"author":4,"author_profile":5,"description":76,"short_description":77,"active_installs":61,"downloaded":78,"rating":20,"num_ratings":21,"last_updated":79,"tested_up_to":23,"requires_at_least":24,"requires_php":25,"tags":80,"homepage":85,"download_link":86,"security_score":8,"vuln_count":33,"unpatched_count":33,"last_vuln_date":34,"fetched_at":35},"wp-shortcode-shield","WP Shortcode Shield","\u003Cp>This plugin allows you to refer to a WordPress shortcode within the content of posts and pages without that shortcode being automagically expanded by WordPress. The plugin takes advantage of the fact that the \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FShortcode_API\" rel=\"nofollow ugc\">WordPress ShortCode API\u003C\u002Fa> does not support nested shortcodes to allow this plugin’s shortcode to wrap the shortcode being documented.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>The shortcode parser uses a single pass on the post content. This means that if\u003Cbr \u002F>\n  the $content parameter of a shortcode handler contains another shortcode, it won’t\u003Cbr \u002F>\n  be parsed\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>The plugin supports both the self closing \u003Ccode>[shortcode]\u003C\u002Fcode> and enclosing \u003Ccode>[shortcode]content[\u002Fshortcode]\u003C\u002Fcode> forms and supports a short form name of the shortcode, \u003Ccode>[wp_scs]\u003C\u002Fcode> as well as the more verbose \u003Ccode>[wp_shortcode_shield]\u003C\u002Fcode> form. For the sake of brevity, the remainder of this documentation will use the \u003Ccode>[wp_scs]\u003C\u002Fcode> short form name.\u003C\u002Fp>\n\u003Cp>If using the self-closing form of the shortcode, you need to supply the name of the shortcode you are documenting using the \u003Ccode>code\u003C\u002Fcode> attribute but without using the enclosing \u003Ccode>[\u003C\u002Fcode> and \u003Ccode>]\u003C\u002Fcode> characters. This is because when parsing shortcodes, WordPress looks for the first occurrence of the ‘]’ character to terminate the shortcode. As a result of this, usage such as\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[wp_scs code=\"[another-shortcode-name]\"]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>… WordPress will use the ‘]’ character inside the \u003Ccode>code\u003C\u002Fcode> attribute to try and terminate the shortcode name, which is not what is desired. Instead, the plugin automagically adds the terminating ‘[‘ and ‘]’ characters to the plugin’s output, so that usage such as\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[wp_scs code=\"another-shortcode-name\"]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>… will display \u003Cem>[another-shortcode-name]\u003C\u002Fem> in your post’s of page’s content.\u003C\u002Fp>\n\u003Cp>If you are using the enclosing form of the shortcode, you can either supply the shortcode to be documented with or without enclosing ‘[‘ and ‘]’ characters; if they are omitted, the plugin will add them for you, so that usage such as\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[wp_scs][another-shortcode-name][\u002Fwp_scs]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>… and\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[wp_scs]another-shortcode-name[\u002Fwp_scs]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>… will display the same results, namely \u003Cem>[another-shortcode-name]\u003C\u002Fem>.\u003C\u002Fp>\n\u003Cp>Finally a note of caution, you cannot mix the enclosing and self closing form of the plugin’s shortcode within the same post or page; this is not a limitation of the plugin, but the way in which WordPress implements the \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FShortcode_API\" rel=\"nofollow ugc\">ShortCode API\u003C\u002Fa> …\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>The parser does not handle mixing of enclosing and non-enclosing forms of the same\u003Cbr \u002F>\n  shortcode as you would want it to. For example, if you have:\u003C\u002Fp>\n\u003Cp>\u003Ccode>[myshortcode example='non-enclosing' \u002F] non-enclosed content [myshortcode] enclosed content\u003Cbr \u002F>\n  [\u002Fmyshortcode]\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>Instead of being treated as two shortcodes separated by the text ” non-enclosed content “,\u003Cbr \u002F>\n  the parser treats this as a single shortcode enclosing ” non-enclosed content [myshortcode]\u003Cbr \u002F>\n  enclosed content”.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n","Allows posts and pages to easily document WordPress shortcodes without the shortcode being expanded.",2613,"2012-11-12T06:00:00.000Z",[81,82,83,84],"documentation","page","post","shortcode","http:\u002F\u002Fwww.vicchi.org\u002Fcodeage\u002Fwp-shortcode-shield\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-shortcode-shield.1.1.0.zip"]