[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fQT_n-QTFNXcfRUdXFF0syOezd_euOf0_LQdCsSlklNU":3},{"slug":4,"display_name":5,"profile_url":6,"plugin_count":7,"total_installs":8,"avg_security_score":9,"avg_patch_time_days":10,"trust_score":11,"computed_at":12,"plugins":13},"enricosorcinelli","Enrico Sorcinelli","https:\u002F\u002Fprofiles.wordpress.org\u002Fenricosorcinelli\u002F",5,1090,88,30,86,"2026-04-04T01:08:20.575Z",[14,40,58,75,91],{"slug":15,"name":16,"version":17,"author":5,"author_profile":6,"description":18,"short_description":19,"active_installs":20,"downloaded":21,"rating":22,"num_ratings":23,"last_updated":24,"tested_up_to":25,"requires_at_least":26,"requires_php":27,"tags":28,"homepage":34,"download_link":35,"security_score":36,"vuln_count":37,"unpatched_count":37,"last_vuln_date":38,"fetched_at":39},"rest-xmlrpc-data-checker","REST XML-RPC Data Checker","1.4.0","\u003Cp>JSON REST API and XML-RPC API are powerful ways to remotely interact with WordPress.\u003C\u002Fp>\n\u003Cp>If you don’t have external applications that need to communicate with your WordPress instance using JSON REST API or XML-RPC API you should disable access to them for external requests.\u003C\u002Fp>\n\u003Cp>In the standard WordPress installation JSON REST API and XML-RPC API are enabled by default.\u003Cbr \u002F>\nIn particular the REST API is turned on also for unlogged users. This means that your WordPress instance is potentially leaking data, for example anyone could be able to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>copy easily your published contents natively with the REST API (and not with a web crawler);\u003C\u002Fli>\n\u003Cli>get the list of all users (with their ID, nickname and name);\u003C\u002Fli>\n\u003Cli>retrieve other information that you didn’t want to be public (such as an unlisted published page or a saved media not yet used).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Even if you could do the stuff by writing your own code using native filters, this plugin aims to help you to control JSON REST API and XML-RPC API accesses from the administration panel or programmatically by a simple API filter.\u003C\u002Fp>\n\u003Ch3>Basic Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Cstrong>Disable REST API\u003C\u002Fstrong> interface for unlogged users.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Disable JSONP support\u003C\u002Fstrong> on REST API.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Add Basic Authentication\u003C\u002Fstrong> to REST API.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Remove\u003C\u002Fstrong> REST \u003Ccode>\u003Clink>\u003C\u002Fcode> tags, REST \u003Ccode>Link\u003C\u002Fcode> HTTP header and REST Really Simple Discovery (RSD) informations.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Setup trusted users, IP\u002FNetworks and endpoints\u003C\u002Fstrong> for unlogged users REST requests.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Change REST endpoint prefix\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Disable XML-RPC API\u003C\u002Fstrong> interface.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Remove\u003C\u002Fstrong> \u003Ccode>\u003Clink>\u003C\u002Fcode> to the Really Simple Discovery (RDS) informations.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Remove\u003C\u002Fstrong> \u003Ccode>X-Pingback\u003C\u002Fcode> HTTP header.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Setup trusted users, IP\u002FNetworks and methods\u003C\u002Fstrong> for XML-RPC requests.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Show user’s access informations\u003C\u002Fstrong> in users list administration screen.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cp>Once the plugin is installed you can control settings in the following ways:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Using the \u003Cem>Settings->REST XML-RPC Data Checker\u003C\u002Fem> administration screen.\u003C\u002Fli>\n\u003Cli>Programmatically, by using \u003Ccode>rest_xmlrpc_data_checker_settings\u003C\u002Fcode> filter (see below).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>API\u003C\u002Fh3>\n\u003Ch4>Hooks\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>\u003Ccode>rest_xmlrpc_data_checker_settings\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Filters plugin settings values.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>apply_filters( 'rest_xmlrpc_data_checker_settings', array $settings )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>rest_xmlrpc_data_checker_admin_settings\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Filter allowing to display or not the plugin settings page in the administration.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>apply_filters( 'rest_xmlrpc_data_checker_admin_settings', boolean $display )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>rest_xmlrpc_data_checker_rest_error\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Filter JSON REST authentication error after plugin checks.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>apply_filters( 'rest_xmlrpc_data_checker_rest_error', WP_Error|boolean $result )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>xmlrpc_before_insert_post\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Filter XML-RPC post data to be inserted via XML-RPC before to insert post into database.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>apply_filters( 'xmlrpc_before_insert_post', array|IXR_Error $content_struct, WP_User $user )\n\u003C\u002Fcode>\u003C\u002Fpre>\n","REST XML-RPC Data Checker allow to check JSON REST and XML-RPC API requests and grant access permissions.",1000,10954,100,3,"2022-08-04T06:44:00.000Z","6.0.11","4.4","5.2.4",[29,30,31,32,33],"api","json","rest","security","xmlrpc","https:\u002F\u002Fgithub.com\u002Fenrico-sorcinelli\u002Frest-xmlrpc-data-checker","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Frest-xmlrpc-data-checker.1.4.0.zip",85,0,null,"2026-03-15T15:16:48.613Z",{"slug":41,"name":42,"version":43,"author":5,"author_profile":6,"description":44,"short_description":45,"active_installs":46,"downloaded":47,"rating":37,"num_ratings":37,"last_updated":48,"tested_up_to":49,"requires_at_least":26,"requires_php":27,"tags":50,"homepage":56,"download_link":57,"security_score":36,"vuln_count":37,"unpatched_count":37,"last_vuln_date":38,"fetched_at":39},"seo-writing-assistant-semrush-custom-fields","SEO Writing Assistant SEMrush Custom Fields","1.1.0","\u003Cp>The \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsemrush-seo-writing-assistant\u002F\" rel=\"ugc\">SEMrush SEO Writing Assistant\u003C\u002Fa> plugin read only from post \u003Ccode>title\u003C\u002Fcode> and post \u003Ccode>content\u003C\u002Fcode> elements for the real time check.\u003C\u002Fp>\n\u003Cp>This lightweight plugin allows you to use an arbitrary value for that check in addition to those values.\u003C\u002Fp>\n\u003Cp>So, if you are using some kind of a page builders, field managers and so on, you have only to define a constant in your \u003Cem>wp_config.php\u003C\u002Fem> file and eventually to write a little bit of JavaScript code in order to specify which fields.\u003C\u002Fp>\n\u003Cp>Note that the plugin don’t replace \u003Cem>SEMrush SEO Writing Assistant\u003C\u002Fem> but is intended to be used together.\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cp>Once the plugin is activated you can configure it by defining following constants in your \u003Cem>wp-config.php\u003C\u002Fem>:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>SWA_SEMRUSH_CUSTOM_FIELDS_PLUGIN_AUTOENABLE\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Automatically enable use of additional text value for SEMrush check. The default value is \u003Ccode>false\u003C\u002Fcode>.\u003Cbr \u002F>\nThis is the only configuration you have to do in order to have the plugin feature working.\u003Cbr \u002F>\nFor example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'SWA_SEMRUSH_CUSTOM_FIELDS_PLUGIN_AUTOENABLE', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cul>\n\u003Cli>\u003Ccode>SWA_SEMRUSH_CUSTOM_FIELDS_PLUGIN_INTERVAL\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Allows to change the interval between automatic updates of the text used by SEMrush checks.\u003Cbr \u002F>\nThe default value is \u003Ccode>5\u003C\u002Fcode> seconds.For example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'SWA_SEMRUSH_CUSTOM_FIELDS_PLUGIN_INTERVAL', 10 );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You can alernatavely control the plugins programmatically, by using\u003Cbr \u002F>\n    semrush_seo_writing_assistant_post_types (optional) filter and \u003Ccode>SeoWritingAssistantSEMrushCustomFields\u003C\u002Fcode> JavaScript object (see below).\u003C\u002Fp>\n\u003Ch3>API\u003C\u002Fh3>\n\u003Ch4>WordPress Hooks\u003C\u002Fh4>\n\u003Cp>**\u003Ccode>swa_semrush_custom_fields_settings\u003C\u002Fcode>  **\u003C\u002Fp>\n\u003Cp>Filters plugin settings values.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>apply_filters( 'swa_semrush_custom_fields_settings', array $settings )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>semrush_seo_writing_assistant_post_types\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Filters post types where to enable plugin. Default to \u003Ccode>array( 'post', 'page', 'product' )\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>apply_filters( 'semrush_seo_writing_assistant_post_types', array $post_types )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The filter has the same name as the one used by \u003Cem>SEMrush SEO Writing Assistant\u003C\u002Fem> plugin (since version 1.0.4) used for the same purpose.\u003C\u002Fp>\n\u003Ch4>JavaScript Event\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>\u003Ccode>seo-writing-assistant-semrush\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This event allows you to update the text for SEMrush analysis.\u003Cbr \u002F>\nThe following example will update text for SEMrush check every 5 seconds, using \u003Ccode>excerpt\u003C\u002Fcode> and \u003Ccode>my_custom_fields\u003C\u002Fcode> custom field values (working both with block and classic editors):\u003C\u002Fp>\n\u003Cpre>\u003Ccode>jQuery( document ).ready( function() {\n    var swa = new SeoWritingAssistantSEMrushCustomFields( { interval: 5 } );\n    jQuery( document ).on( 'seo-writing-assistant-semrush', function( event, data ) {\n        data.html += jQuery( '#excerpt' ).val() + \"\\n\"\n            + jQuery( '.editor-post-excerpt__textarea textarea').val() + \"\\n\"\n            + jQuery( '#my_custom_fields' ).val();\n    } )\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Note that if you have previously defined constant \u003Ccode>SWA_SEMRUSH_CUSTOM_FIELDS_PLUGIN_AUTOENABLE\u003C\u002Fcode> to \u003Ccode>true\u003C\u002Fcode>,\u003Cbr \u002F>\nyou don’t have to create new \u003Ccode>SeoWritingAssistantSEMrushCustomFields\u003C\u002Fcode> object.\u003C\u002Fp>\n\u003Ch4>JavaScript API\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>\u003Ccode>setHtml()\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The following example will update programmatically the text used by SEMrush check with an arbitrary value:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>jQuery( document ).ready( function() {\n    var swa = new SeoWritingAssistantSEMrushCustomFields( { interval: 0 } );\n    swa.setHtml( 'foo baz bar' );\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Advanced Custom Fields\u003C\u002Fh4>\n\u003Cp>The plugin checks if \u003Cem>Advanced Custom Fields\u003C\u002Fem> is active in your WordPress instance and adds a custom setting to each field\u003Cbr \u002F>\n(only for \u003Ccode>input\u003C\u002Fcode> within \u003Cem>text\u003C\u002Fem>, \u003Cem>radio\u003C\u002Fem> and \u003Cem>checkbox\u003C\u002Fem> type, \u003Ccode>textarea\u003C\u002Fcode> and \u003Ccode>select\u003C\u002Fcode> elements) allowing you to add his value\u003Cbr \u002F>\nto SEMrush check without having to write any additional JavaScript code.\u003C\u002Fp>\n\u003Ch4>Autodiscovery\u003C\u002Fh4>\n\u003Cp>The plugin also automatically add to text used by SEMrush checks, the values of all HTML elements\u003Cbr \u002F>\nwith \u003Ccode>swa-scf\u003C\u002Fcode> class or \u003Ccode>data-swa-scf\u003C\u002Fcode> attribute.\u003Cbr \u002F>\nThis will applied only for \u003Ccode>input\u003C\u002Fcode> (within \u003Cem>text\u003C\u002Fem>, \u003Cem>radio\u003C\u002Fem> and \u003Cem>checkbox\u003C\u002Fem> type), \u003Ccode>textarea\u003C\u002Fcode>, and \u003Ccode>select\u003C\u002Fcode> elements.\u003C\u002Fp>\n","The SEMrush SEO Writing Assistant plugin read only from post title and post content elements for the real time check.",70,3262,"2019-06-17T15:53:00.000Z","5.2.24",[51,52,53,54,55],"content-analysis","content-marketing","custom-fields","readability","seo","https:\u002F\u002Fgithub.com\u002Fenrico-sorcinelli\u002Fseo-writing-assistant-semrush-custom-fields","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fseo-writing-assistant-semrush-custom-fields.1.1.0.zip",{"slug":59,"name":60,"version":61,"author":5,"author_profile":6,"description":62,"short_description":63,"active_installs":64,"downloaded":65,"rating":37,"num_ratings":37,"last_updated":66,"tested_up_to":25,"requires_at_least":26,"requires_php":27,"tags":67,"homepage":73,"download_link":74,"security_score":36,"vuln_count":37,"unpatched_count":37,"last_vuln_date":38,"fetched_at":39},"sticky-postbox","Sticky Postbox","1.3.0","\u003Cp>\u003Cstrong>Sticky Postbox\u003C\u002Fstrong> is a piece of code written few years ago as exercise to learn how WordPress handles administration meta boxes’s availables statuses (closed, hidden and sortings).\u003C\u002Fp>\n\u003Cp>This very lightweight plugin adds the \u003Cem>sticky\u003C\u002Fem> feature to administration meta boxes allowing them to be sticky at top right corner of the browser window.\u003C\u002Fp>\n\u003Cp>Only one meta box can be sticky at once, so a new sticky meta box unstick the current one (if there is one).\u003C\u002Fp>\n\u003Ch3>Basic Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Per-user settings.\u003C\u002Fli>\n\u003Cli>Multisite support.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cp>Once the plugin is installed and activated you can sticky administration meta boxes using sticky icon (it appears on the top right corner of each box).\u003C\u002Fp>\n\u003Ch3>API\u003C\u002Fh3>\n\u003Ch4>Constants\u003C\u002Fh4>\n\u003Cp>You can use define following constants in your \u003Cem>wp-config.php\u003C\u002Fem> file.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>\u003Ccode>STICKY_POSTBOX_DEBUG\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Turn on debug messages (also \u003Ccode>WP_DEBUG\u003C\u002Fcode> has to be \u003Ccode>true\u003C\u002Fcode>).\u003Cbr \u002F>\nDefault to \u003Ccode>false\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>\u003Ccode>STICKY_POSTBOX_GLOBAL_OPTIONS\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>In a Multisite installation, allows to shares user’s sticky meta boxes settings across all his sites. For example, if you sticky \u003Cem>Publish\u003C\u002Fem> box in editing Pages in a specific site, it will be sticky on all Pages of all sites.\u003Cbr \u002F>\nDefault to \u003Ccode>false\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>\u003Ccode>STICKY_POSTBOX_AUTOENABLE\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>By default if the plugin has been activated, it starts automatically.\u003Cbr \u002F>\nDefine to \u003Ccode>false\u003C\u002Fcode> if you want to init it manually, for example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F\u002F Activate manually the plugin once all plugin have been loaded.\nadd_action( 'plugins_loaded', function() {\n    \\Sticky_Postbox::get_instance( \n        array(\n            'debug'          => WP_DEBUG,\n            'global_options' => false,\n        )\n    );\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Hooks\u003C\u002Fh4>\n\u003Cp>Currently the plugin doesn’t have actions or filters.\u003C\u002Fp>\n","Add sticky feature to administration meta boxes.",20,1176,"2022-07-13T15:38:00.000Z",[68,69,70,71,72],"administration","dashboard","options","post","sticky","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fsticky-postbox","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsticky-postbox.1.3.0.zip",{"slug":76,"name":77,"version":78,"author":5,"author_profile":6,"description":79,"short_description":80,"active_installs":37,"downloaded":81,"rating":37,"num_ratings":37,"last_updated":82,"tested_up_to":83,"requires_at_least":26,"requires_php":27,"tags":84,"homepage":89,"download_link":90,"security_score":36,"vuln_count":37,"unpatched_count":37,"last_vuln_date":38,"fetched_at":39},"featured-image-extended","Featured Image Extended","1.0.2","\u003Cp>Feature Image Extended extends featured image functionality allowing:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Hiding featured image in your themes for all post types.\u003C\u002Fli>\n\u003Cli>Adding link to the featured image.\u003C\u002Fli>\n\u003Cli>Adding thumbnail featured image in administration screens listing.\u003C\u002Fli>\n\u003Cli>Featured image quick-editing.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cp>Once the plugin is installed you can control settings in the following ways:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Programmatically by using \u003Ccode>featured_image_extended_settings\u003C\u002Fcode> filter (see below).\u003C\u002Fli>\n\u003Cli>Using the \u003Cem>Settings->Featured Image Extended\u003C\u002Fem> administration screen.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If your theme uses a different call other than \u003Ccode>the_post_thumbnail()\u003C\u002Fcode>\u002F\u003Ccode>get_the_post_thumbnail()\u003C\u002Fcode> in order to get the featured image, this plugin might not work.\u003Cbr \u002F>\nSo, in order to get extended featured image settings and apply to your pages, you should use \u003Ccode>featured_image_extended()\u003C\u002Fcode> (see below).\u003C\u002Fp>\n\u003Ch3>API\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>\u003Ccode>featured_image_extended( integer $post_id = null )\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>It returns an array containing featured image extended information of \u003Ccode>$post_id\u003C\u002Fcode> post (or current post if you don’t supply an argument) like following:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>array(\n    'show'   => true,\n    'url'    => 'https:\u002F\u002Fmyurl.com',\n    'target' => '_blank',\n    'title'  => 'Image title',\n)\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Hooks\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>\u003Ccode>featured_image_extended_settings\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Filter plugin settings values.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>apply_filters( 'featured_image_extended_settings', array $settings )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>featured_image_extended_admin_settings\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Filter allowing to display or not the plugin settings page in the administration.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>apply_filters( 'featured_image_extended_admin_settings', boolean $display )\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Feature Image Extended extends featured image builtin functionality.",1336,"2018-06-28T08:47:00.000Z","4.9.29",[85,86,71,87,88],"category","featured-image","theme","thumbnail","https:\u002F\u002Fgithub.com\u002Fenrico-sorcinelli\u002Ffeatured-image-extended","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffeatured-image-extended.1.0.2.zip",{"slug":92,"name":93,"version":94,"author":5,"author_profile":6,"description":95,"short_description":96,"active_installs":37,"downloaded":97,"rating":37,"num_ratings":37,"last_updated":98,"tested_up_to":83,"requires_at_least":26,"requires_php":27,"tags":99,"homepage":102,"download_link":103,"security_score":22,"vuln_count":37,"unpatched_count":37,"last_vuln_date":38,"fetched_at":104},"taxonomies-sortable","Taxonomies Sortable","1.0.1","\u003Cp>Taxonomies Sortable allow to sort non-hierarchical taxonomy terms associated to objects by drag&drop them on the administration interface.\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cp>Once the plugin is installed you can make a taxonomy sortable in the following ways:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Programmatically by adding \u003Ccode>'sortable' => true\u003C\u002Fcode> argument in \u003Ccode>register_taxonomy()\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>Programmatically by using \u003Ccode>taxonomies_sortable\u003C\u002Fcode> filter below.\u003C\u002Fli>\n\u003Cli>Using the \u003Cem>Settings->Taxonomies Sortable\u003C\u002Fem> administration screen by selecting non-hierarchical taxonomies you want to make sortable.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Note that making a taxonomy sortable, implicitly means also setting \u003Ccode>sort => true\u003C\u002Fcode> for that taxonomy.\u003C\u002Fp>\n\u003Ch3>Hooks\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>\u003Ccode>taxonomies_sortable\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Filter allowing to programmatically set sortable taxonomies.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>apply_filters( 'taxonomies_sortable', array $taxonomies )\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>taxonomies_sortable_admin_settings\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Filter allowing to display or not the plugin settings page in the administration.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>apply_filters( 'taxonomies_sortable_admin_settings', boolean $display )\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Allows to sort taxonomy terms associated to objects.",1142,"",[100,101],"admin","taxonomy","https:\u002F\u002Fgithub.com\u002Fenrico-sorcinelli\u002Ftaxonomies-sortable","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftaxonomies-sortable.1.0.1.zip","2026-03-15T14:44:11.924Z"]