[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f58RwME1xQD1atqju0Tx_X2TabbdNED_83ZGfR88Us4E":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},"dougwollison","Doug Wollison","https:\u002F\u002Fprofiles.wordpress.org\u002Fdougwollison\u002F",7,1170,90,30,87,"2026-04-04T09:11:40.382Z",[14,35,55,74,91,103,120],{"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":29,"download_link":30,"security_score":31,"vuln_count":32,"unpatched_count":32,"last_vuln_date":33,"fetched_at":34},"pomo-editor","PO\u002FMO Editor","1.4.2","\u003Cp>\u003Cstrong>This plugin is no longer being developed. I personally recommend using \u003Ca href=\"https:\u002F\u002Fpoedit.net\u002F\" rel=\"nofollow ugc\">POEdit\u003C\u002Fa> for a more robust, external solution. Anyone interested in \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fdougwollison\u002Fpomo-editor\" rel=\"nofollow ugc\">taking over development\u003C\u002Fa> is welcome to.\u003C\u002Fstrong>\u003C\u002Fp>\n","This plugin is no longer being developed. I personally recommend using POEdit for a more robust, external solution. Anyone interested in taking over d …",1000,37579,84,13,"2018-06-06T15:16:00.000Z","0.0.0","99.99.99","",[],"https:\u002F\u002Fgithub.com\u002Fdougwollison\u002Fpomo-editor","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpomo-editor.zip",85,0,null,"2026-03-15T15:16:48.613Z",{"slug":36,"name":37,"version":38,"author":5,"author_profile":6,"description":39,"short_description":40,"active_installs":41,"downloaded":42,"rating":32,"num_ratings":32,"last_updated":43,"tested_up_to":44,"requires_at_least":45,"requires_php":46,"tags":47,"homepage":52,"download_link":53,"security_score":54,"vuln_count":32,"unpatched_count":32,"last_vuln_date":33,"fetched_at":34},"index-pages","Index Pages","1.3.0.1","\u003Cp>The Index Pages system allows you to designate pages as the index page for a particular post type.\u003C\u002Fp>\n\u003Cp>This allows you to have a custom title, text content, and other information displayed on your\u003Cbr \u002F>\npost type archives, should your current theme support it.\u003C\u002Fp>\n\u003Cp>For theme developers, the plugin offers some template functions for loading the post object for the\u003Cbr \u002F>\ncurrent index page (including the posts page), in a similar fashion to \u003Ccode>the_post();\u003C\u002Fcode>, to create things\u003Cbr \u002F>\nlike a customizable introductory banner that appears above the listing, using the index page’s data.\u003C\u002Fp>\n\u003Cp>Designated index pages are flagged as such in the Pages manager, for easy recognition.\u003C\u002Fp>\n\u003Ch3>Usage Documentation\u003C\u002Fh3>\n\u003Cp>The Index Page assignment interface can be found under Settings > Reading. By default, all post types\u003Cbr \u002F>\nregistered with the \u003Ccode>has_archive\u003C\u002Fcode> argument set to true will be available for assignment.\u003C\u002Fp>\n\u003Cp>For theme and plugin developers, you can register support for your custom post types like so:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>IndexPages\\Registry::add_post_types( $post_types ); \u002F\u002F a single post type or array of post types\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>When an index page is assigned, it’s permalink will point to the associated post type’s archive, with\u003Cbr \u002F>\nthe page title updated appropriately.\u003C\u002Fp>\n\u003Cp>For theme and plugin developers, you can access the index page’s post object with the following.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>the_index_page();\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This works exactly like \u003Ccode>the_post();\u003C\u002Fcode>, populating the \u003Ccode>$post\u003C\u002Fcode> variable with the index page’s data.\u003C\u002Fp>\n","Assign pages as the index page for WordPress custom post types, similar to the Posts Page.",60,2810,"2024-10-14T22:04:00.000Z","6.6.5","4.0.0","5.4.0",[48,49,50,51],"custom-index","custom-post-type","index-page","page-for-posts","https:\u002F\u002Fgithub.com\u002Fdougwollison\u002Findex-pages","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Findex-pages.1.3.0.1.zip",92,{"slug":56,"name":57,"version":58,"author":5,"author_profile":6,"description":59,"short_description":60,"active_installs":10,"downloaded":61,"rating":62,"num_ratings":63,"last_updated":64,"tested_up_to":44,"requires_at_least":65,"requires_php":66,"tags":67,"homepage":72,"download_link":73,"security_score":54,"vuln_count":32,"unpatched_count":32,"last_vuln_date":33,"fetched_at":34},"nlingual","nLingual","2.10.0.1","\u003Cp>The nLingual system allows for flexible multilingual support and translation management for WordPress. The system handles translations on a per-post basis, and can be set to be synchronized so changes to certain details on one are copied to the others. It offers you control over what can be translated and how, with a number of utilities available for 3rd party themes and plugins to utilize.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>nLingual 2 offers more robust control of translation management, better extensibility, and fixes to numerous core issues with the previous incarnation.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>Translation for Almost Anything\u003C\u002Fh4>\n\u003Cp>When setting up, you have control over what content supports translation. Any UI-enabled post types or taxonomies will be available for enabling, along with any navigation menus or sidebar locations registered. In addition, nLingual includes a LocalizeThis API that can be enabled on nearly any text field found in the admin, allowing just about any option or meta field to support separate values in each language.\u003C\u002Fp>\n\u003Ch4>Simple Translation Creation and Management\u003C\u002Fh4>\n\u003Cp>Assigning a language and translations to a post can be done on either the post editor screen or the posts management screen via Quick Edit (language can also be set for multiple post via Bulk Edit). You can also easily create new translations for existing posts on the fly; select “New [language] [post type]”, provide a translated title if you wish, and a new draft post will be created that is an exact copy of the original, ready for translation.\u003C\u002Fp>\n\u003Cp>Translations are stored as independent posts, associated with their counterparts via a custom table. This allows you to translate the custom fields and other metadata associated with a post, and can assign them their own separate terms if desired. However, since there are plenty of occasions where you want the same information used between posts, nLingual offers \u003Cem>post synchronization\u003C\u002Fem>.\u003C\u002Fp>\n\u003Ch4>Post Synchronization\u003C\u002Fh4>\n\u003Cp>Each post type has it’s own rules for what data is synchronized between translations. When changes are saved to a post, it’s translations will be updated with to have the same data in the approved fields. This covers post data (e.g. date, status, and menu order), terms of specified taxonomies, and any meta fields you specify (e.g. the thumbnail image used, or a custom field value).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Note: Currently, there is no per-post basis override for the synchronization rules\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>Free-form Language Management\u003C\u002Fh4>\n\u003Cp>Admittedly, this is a feature few will need, but it’s a godsend to those that do. When setting up the languages nLingual will use, you can define you own languages from scratch or based on numerous presets. Each language has a number of fields:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>System Name: the name to use when referring to the language within the admin.\u003C\u002Fli>\n\u003Cli>Native Name: the name of the language as it appears to native speakers on the site.\u003C\u002Fli>\n\u003Cli>Short Name: a shorthand version of the native name, if applicable.\u003C\u002Fli>\n\u003Cli>Locale: the language\u002Fcountry code to represent this language, as well identify the .mo file to load for text domains.\u003C\u002Fli>\n\u003Cli>ISO Code: the official ISO 639-1 code for the language (2 letters)\u003C\u002Fli>\n\u003Cli>Slug: the value to use when localizing a URL for the language (typically the same as the ISO code).\u003C\u002Fli>\n\u003Cli>Text Direction: the text direction the language should be rendered in (Left-to-right or right-to-left). Will override the one specified in the text domain files.\u003C\u002Fli>\n\u003Cli>Active State: whether or not to allow public access to content in the language.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Flexible Language Detection\u002FSwitching\u003C\u002Fh4>\n\u003Cp>When the public-facing side of the site is loaded, nLingual will attempt to detect what language to serve the page in, using the following process:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Use the language code in the \u003Ccode>$_REQUEST\u003C\u002Fcode> array for the specified key, if present.\u003C\u002Fli>\n\u003Cli>Use the language code in either the subdomain or directory path, depending on method specified.\u003C\u002Fli>\n\u003Cli>Use the browser’s preferred language setting and find the closest match, falling back to the default language.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Once the language is set, it can be overridden by the language belonging to the requested post. This override is an configurable option.\u003C\u002Fp>\n\u003Cp>In addition, the language can temporarily be switched to another by 3rd party theme or plugin code, similar to switching blogs in a multisite installation. When the language is switched, all text domain files will be reloaded in the desired language (the originals cached for when it’s restored), so any gettext translations will reflect the current language.\u003C\u002Fp>\n\u003Ch4>Extensibility and 3rd Party Development\u003C\u002Fh4>\n\u003Cp>In addition to numerous hooks to modify the functionality of nLingual, this plugin also includes some useful gettext utilities: \u003Ccode>_f\u003C\u002Fcode>, \u003Ccode>_ef\u003C\u002Fcode>, \u003Ccode>_fx\u003C\u002Fcode>, \u003Ccode>_efx\u003C\u002Fcode>, \u003Ccode>_a\u003C\u002Fcode>, and \u003Ccode>_xa\u003C\u002Fcode>, all of which are documented in \u003Ccode>includes\u002Ffunctions-gettext.php\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Ch4>Backwards Compatibility\u003C\u002Fh4>\n\u003Cp>Although nLingual 2 has be rewritten from scratch, most if not all of the functions and filters are still available via the backwards compatibility feature, which is automatically enabled upon upgrading. However, any code that directly queries the database using the old nLingual language and translation tables will need to be updated to reflect the new structure.\u003C\u002Fp>\n","A simple but flexible multilingual system. Features custom language management, post data synchronization and theme\u002Fplugin development utilities.",11956,80,4,"2024-11-07T14:39:00.000Z","6.2.0","7.0.0",[68,69,70,71],"bilingual","language","multilingual","translation","https:\u002F\u002Fgithub.com\u002Fdougwollison\u002Fnlingual","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fnlingual.2.10.0.1.zip",{"slug":75,"name":76,"version":77,"author":5,"author_profile":6,"description":78,"short_description":79,"active_installs":10,"downloaded":80,"rating":32,"num_ratings":32,"last_updated":81,"tested_up_to":44,"requires_at_least":82,"requires_php":83,"tags":84,"homepage":89,"download_link":90,"security_score":54,"vuln_count":32,"unpatched_count":32,"last_vuln_date":33,"fetched_at":34},"order-manager","Order Manager","1.1.0","\u003Cp>Order Manager allows you sort posts and terms belonging to any post type or any taxonomy,\u003Cbr \u002F>\nas well as posts tagged with a specific term.\u003C\u002Fp>\n\u003Ch4>Options\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Enable order manager for all posts\u002Fterms\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This will add a new page to the WordPress menu under the associated post type.\u003Cbr \u002F>\nIt provides you with a straightforward drag-and-drop interface to organize your\u003Cbr \u002F>\nposts or terms. If the post type or taxonomy supports a hierarchy, it will also\u003Cbr \u002F>\nlet you easily reassign items to different parents by dragging them just below\u003Cbr \u002F>\nthe intended parent.\u003C\u002Fp>\n\u003Cp>This adds a new \u003Ccode>'orderby'\u003C\u002Fcode> value when using \u003Ccode>get_terms()\u003C\u002Fcode>: \u003Ccode>'menu_order'\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Enable post order manager for each term\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Taxonomies with this option enabled will now offer a post order interface on\u003Cbr \u002F>\neach term’s edit screen, allowing you to set a unique order for posts in that\u003Cbr \u002F>\nterm.\u003C\u002Fp>\n\u003Cp>This adds a new \u003Ccode>'orderby'\u003C\u002Fcode> value when using \u003Ccode>get_posts()\u003C\u002Fcode>: \u003Ccode>'term_order'\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>\u003Cem>Note: this unique order will only take effect when listing posts belonging to\u003Cbr \u002F>\na specific term that uses this.\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Override order on \u003Ccode>get_posts()\u002Fget_terms()\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This will cause all queries for posts\u002Fterms of that type to use the custom\u003Cbr \u002F>\norder by default, rather than by date\u002Fname. In the case of a query for posts\u003Cbr \u002F>\nbelonging to a term with post-sorting enabled, it will use that order by default.\u003C\u002Fp>\n","Adds order controls for posts and terms",1915,"2024-10-14T23:01:00.000Z","5.2","7.1.0",[75,85,86,87,88],"post-order","sort-posts","sort-terms","term-order","https:\u002F\u002Fgithub.com\u002Fdougwollison\u002Forder-manager","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Forder-manager.1.1.0.zip",{"slug":92,"name":93,"version":94,"author":5,"author_profile":6,"description":95,"short_description":96,"active_installs":10,"downloaded":97,"rating":32,"num_ratings":32,"last_updated":98,"tested_up_to":99,"requires_at_least":45,"requires_php":27,"tags":100,"homepage":101,"download_link":102,"security_score":31,"vuln_count":32,"unpatched_count":32,"last_vuln_date":33,"fetched_at":34},"unpublish","Unpublish","1.0.0","\u003Cp>Unpublish is a very simple plugin that does one simple thing: it adds a button to the Edit Post screen.\u003C\u002Fp>\n\u003Cp>This button will appear on published posts\u002Fpages\u002Fetc, which on click will save the post as pending rather than keeping it published.\u003C\u002Fp>\n\u003Ch3>Usage Documentation\u003C\u002Fh3>\n\u003Cp>Click the button if you no longer want the post published.\u003C\u002Fp>\n","Adds a one click \"Unpublish\" button to the WordPress edit screen; switches the status to pending.",16147,"2018-08-10T13:34:00.000Z","4.9.29",[92],"https:\u002F\u002Fgithub.com\u002Fdougwollison\u002Funpublish","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Funpublish.zip",{"slug":104,"name":105,"version":106,"author":5,"author_profile":6,"description":107,"short_description":108,"active_installs":109,"downloaded":110,"rating":111,"num_ratings":112,"last_updated":113,"tested_up_to":25,"requires_at_least":27,"requires_php":27,"tags":114,"homepage":118,"download_link":119,"security_score":54,"vuln_count":32,"unpatched_count":32,"last_vuln_date":33,"fetched_at":34},"domainer","Domainer","1.2.1","\u003Cp>\u003Cstrong>This plugin is no longer being developed.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>WordPress core more or less handles this out of the box \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Fadvanced-administration\u002Fmultisite\u002Fdomain-mapping\u002F\" rel=\"nofollow ugc\">since version 4.5\u003C\u002Fa>.\u003C\u002Fp>\n","This plugin is no longer being developed.",10,4625,86,12,"2024-10-18T16:59:00.000Z",[115,116,117],"domain-management","domain-mapping","multisite","https:\u002F\u002Fgithub.com\u002Fdougwollison\u002Fdomainer","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdomainer.zip",{"slug":121,"name":122,"version":123,"author":5,"author_profile":6,"description":124,"short_description":108,"active_installs":109,"downloaded":125,"rating":32,"num_ratings":32,"last_updated":126,"tested_up_to":25,"requires_at_least":27,"requires_php":27,"tags":127,"homepage":133,"download_link":134,"security_score":54,"vuln_count":32,"unpatched_count":32,"last_vuln_date":33,"fetched_at":34},"quickstart","QuickStart","1.13.0","\u003Cp>\u003Cstrong>This plugin is no longer being developed.\u003C\u002Fstrong>\u003C\u002Fp>\n",4310,"2024-10-18T16:58:00.000Z",[128,129,130,131,132],"development","framework","function","utilities","utility","https:\u002F\u002Fgithub.com\u002Fdougwollison\u002Fquickstart","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fquickstart.zip"]