[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fa_s1UP_MxCR3d_PKwMazch_hq1PbD3ZqfItWvnuF1aQ":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},"tfrommen","Thorsten Frommen","https:\u002F\u002Fprofiles.wordpress.org\u002Ftfrommen\u002F",6,2140,85,30,84,"2026-04-05T02:22:55.235Z",[14,37,55,74,93,108],{"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":32,"download_link":33,"security_score":9,"vuln_count":34,"unpatched_count":34,"last_vuln_date":35,"fetched_at":36},"bring-back-the-get-shortlink-button","Bring Back the Get Shortlink Button","2.1.0","\u003Cp>As of WordPress 4.4, the \u003Cem>Get Shortlink\u003C\u002Fem> button is hidden by default. This plugin brings it back. Yay.\u003C\u002Fp>\n\u003Cp>Please note that the button does not exist at all in a Block Editor context. It will only show up when using the Classic Editor, for example, when editing a single attachment.\u003C\u002Fp>\n","This plugin brings back the Get Shortlink button, which is hidden by default since WordPress 4.4.",1000,17625,100,7,"2023-02-24T21:00:00.000Z","6.1.10","4.4","7.4",[29,30,31],"link","short","shortlink","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fbring-back-the-get-shortlink-button\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fbring-back-the-get-shortlink-button.2.1.0.zip",0,null,"2026-03-15T15:16:48.613Z",{"slug":38,"name":39,"version":40,"author":5,"author_profile":6,"description":41,"short_description":42,"active_installs":20,"downloaded":43,"rating":44,"num_ratings":45,"last_updated":46,"tested_up_to":47,"requires_at_least":48,"requires_php":49,"tags":50,"homepage":53,"download_link":54,"security_score":9,"vuln_count":34,"unpatched_count":34,"last_vuln_date":35,"fetched_at":36},"wp-dobby","Dobby","1.4.0","\u003Cp>Dobby, the friendly Admin Elf, takes care of all your (unwanted) admin notices.\u003C\u002Fp>\n\u003Ch4>Contribution\u003C\u002Fh4>\n\u003Cp>To \u003Cstrong>contribute\u003C\u002Fstrong> to this plugin, please see its \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ftfrommen\u002FDobby\" rel=\"nofollow ugc\">\u003Cstrong>GitHub repository\u003C\u002Fstrong>\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>If you have a feature request, or if you have developed the feature already, please feel free to use the Issues and\u002For Pull Requests section.\u003C\u002Fp>\n\u003Cp>Of course, you can also provide me with \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fwp-dobby\" rel=\"nofollow ugc\">translations\u003C\u002Fa> if you would like to use the plugin in another not yet included language.\u003C\u002Fp>\n","Dobby, the friendly Admin Elf, takes care of all your (unwanted) admin notices.",9414,98,10,"2021-03-16T22:39:00.000Z","5.7.15","3.1","5.4",[51,52],"admin","notices","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-dobby\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-dobby.1.4.0.zip",{"slug":56,"name":57,"version":40,"author":5,"author_profile":6,"description":58,"short_description":59,"active_installs":60,"downloaded":61,"rating":62,"num_ratings":63,"last_updated":64,"tested_up_to":65,"requires_at_least":66,"requires_php":67,"tags":68,"homepage":72,"download_link":73,"security_score":9,"vuln_count":34,"unpatched_count":34,"last_vuln_date":35,"fetched_at":36},"external-content","External Content","\u003Cp>Have you ever wanted to integrate external content such as a specific post of an external website into your WordPress website? But treat it like any other post? That is, have it appear as teaser or part of a specific (pseudo) archive?\u003C\u002Fp>\n\u003Cp>This is exactly when \u003Cem>External Content\u003C\u002Fem> kicks in.\u003C\u002Fp>\n\u003Ch4>Usage\u003C\u002Fh4>\n\u003Cp>\u003Cem>External Content\u003C\u002Fem> registers a custom post type that, by default, supports title, content, excerpt and thumbnail. This can be customized, though. Managing your posts in your backend is no different from any other post type. Create a new post, give it a title, write some text, define an individual excerpt, and set a post thumbnail, if you wish. Then assign each post an individual external URL by means of the according meta box. This external URL will be used as the post’s permalink.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Filters\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>In order to customize certain aspects of the plugin, it provides you with several filters. For each of these, a short description as well as a code example on how to alter the default behavior is given below. Just put the according code snippet in your theme’s \u003Ccode>functions.php\u003C\u002Fcode> file or your \u003Cem>customization\u003C\u002Fem> plugin, or to some other appropriate place.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>\u003Ccode>external_content_args\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>If you want to alter a specific post type argument but you can’t find a fitting filter, there’s \u003Ccode>external_content_args\u003C\u002Fcode>, which provides you with the complete args array.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the post type args.\n *\n * @param array $args Post type args.\n *\u002F\nadd_filter( 'external_content_args', function( $args ) {\n\n    \u002F\u002F Use hierarchical external content\n    $args[ 'hierarchical' ] = TRUE;\n\n    return $args;\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>external_content_description\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The post type description can be customized by using the \u003Ccode>external_content_description\u003C\u002Fcode> filter.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the post type description.\n *\n * @param string $description Post type description.\n *\u002F\nadd_filter( 'external_content_description', function() {\n\n    \u002F\u002F Provide a description\n    return 'Simple post type for handling external content like any other post.';\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>external_content_labels\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>In case you don’t like the labels, easily adapt them to your liking.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the post type labels.\n *\n * @param array $labels Post type labels.\n *\u002F\nadd_filter( 'external_content_labels', function( $labels ) {\n\n    \u002F\u002F A little more horror, please...\n    $labels[ 'not_found' ] = 'ZOMG, no external content found!!1!!1!!oneone!!!1!eleven!1!';\n\n    return $labels;\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>external_content_meta_key\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>If you want to alter the meta key for the external URL, feel free to do it via this filter.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the meta key.\n *\n * @param string $meta_key Meta key.\n *\u002F\nadd_filter( 'external_content_meta_key', function() {\n\n    \u002F\u002F Let's Shrekify the meta key\n    return 'far_far_away';\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>external_content_post_type\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Yes, you can also alter the post type (slug).\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the post type.\n *\n * @param string $post_type Post type.\n *\u002F\nadd_filter( 'external_content_post_type', function() {\n\n    return 'exotic_stuff';\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>external_content_supports\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This filter provides you with the post type supports.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the post type supports.\n *\n * @param array $supports Post type supports.\n *\u002F\nadd_filter( 'external_content_supports', function( $supports ) {\n\n    \u002F\u002F If your theme uses the excerpt for teasers, just remove the editor to prevent confusion\n    foreach ( $supports as $key => $value ) {\n        if ( 'editor' === $value ) {\n            unset( $supports[ $key ] );\n        }\n    }\n\n    return $supports;\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>external_content_use_external_url\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The permalink of external content is, by default, replaced with the post’s according external URL (i.e., post meta). To disable this behavior, just do the following:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the usage of the external URL as permalink.\n *\n * @param bool $use_external_url Use the external URL as permalink?\n *\u002F\nadd_filter( 'external_content_use_external_url', '__return_false' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Contribution\u003C\u002Fh4>\n\u003Cp>To \u003Cstrong>contribute\u003C\u002Fstrong> to this plugin, please see its \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ftfrommen\u002Fexternal-content\" rel=\"nofollow ugc\">\u003Cstrong>GitHub repository\u003C\u002Fstrong>\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>If you have a feature request, or if you have developed the feature already, please feel free to use the Issues and\u002For Pull Requests section.\u003C\u002Fp>\n\u003Cp>Of course, you can also provide me with translations if you would like to use the plugin in another not yet included language.\u003C\u002Fp>\n","This plugin registers a custom post type to handle external content like any other post. The post permalink is replaced by a custom post meta that hol …",70,4302,80,1,"2016-01-03T17:48:00.000Z","4.4.34","2.9.0","",[69,70,71],"content","external","url","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fexternal-content\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fexternal-content.zip",{"slug":75,"name":76,"version":77,"author":5,"author_profile":6,"description":78,"short_description":79,"active_installs":80,"downloaded":81,"rating":22,"num_ratings":63,"last_updated":82,"tested_up_to":83,"requires_at_least":84,"requires_php":67,"tags":85,"homepage":91,"download_link":92,"security_score":9,"vuln_count":34,"unpatched_count":34,"last_vuln_date":35,"fetched_at":36},"text-modules","Text Modules","1.0.1","\u003Cp>\u003Cstrong>Use the new Text Modules custom post type and display a text module by either shortcode or widget.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Have you ever wanted to use some pieces of text information more than once? For instance, contact information such as a postal address? Or some slogan, motto or claim?\u003C\u002Fp>\n\u003Cp>This is exactly when \u003Cem>Text Modules\u003C\u002Fem> kicks in.\u003C\u002Fp>\n\u003Ch4>Usage\u003C\u002Fh4>\n\u003Cp>This plugin registers a simple post type for text modules. A text module can be accessed either via shortcode (by means of the text module’s ID or slug) or via a new Tex Modules widget.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Filters\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>In order to customize certain aspects of the plugin, it provides you with several filters. For each of these, a short description as well as a code example on how to alter the default behavior is given below. Just put the according code snippet in your theme’s \u003Ccode>functions.php\u003C\u002Fcode> file or your \u003Cem>customization\u003C\u002Fem> plugin, or to some other appropriate place.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>\u003Ccode>text_modules_after_widget_content\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This filter lets you alter the HTML after the widget content.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the HTML after the widget content.\n *\n * @param string $after_widget_content Some HTML after the widget content.\n *\u002F\nadd_filter( 'text_modules_after_widget_content', function() {\n\n    return '\u003C!-- End of Text Modules widget content -->';\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>text_modules_before_widget_content\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This filter lets you alter the HTML before the widget content.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the HTML before the widget content.\n *\n * @param string $before_widget_content Some HTML before the widget content.\n *\u002F\nadd_filter( 'text_modules_before_widget_content', function() {\n\n    return '\u003C!-- Start of Text Modules widget content -->';\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>text_modules_post_type\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Yes, you can alter the post type (slug).\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the post type.\n *\n * @param string $post_type Post type.\n *\u002F\nadd_filter( 'text_modules_post_type', function() {\n\n    return 'exotic_stuff';\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>text_modules_post_type_args\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>If you want to alter a specific post type argument but you can’t find a fitting filter, there’s \u003Ccode>text_modules_post_type_args\u003C\u002Fcode>, which provides you with the complete args array.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the post type args.\n *\n * @param array $args Post type args.\n *\u002F\nadd_filter( 'text_modules_post_type_args', function( $args ) {\n\n    \u002F\u002F Use hierarchical external content\n    $args[ 'hierarchical' ] = TRUE;\n\n    return $args;\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>text_modules_post_type_description\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The post type description can be customized by using the \u003Ccode>text_modules_post_type_description\u003C\u002Fcode> filter.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the post type description.\n *\n * @param string $description Post type description.\n *\u002F\nadd_filter( 'text_modules_post_type_description', function() {\n\n    \u002F\u002F Provide a description\n    return 'Simple post type for text modules.';\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>text_modules_post_type_labels\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>In case you don’t like the labels, easily adapt them to your liking.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the post type labels.\n *\n * @param array $labels Post type labels.\n *\u002F\nadd_filter( 'text_modules_post_type_labels', function( $labels ) {\n\n    \u002F\u002F A little more horror, please...\n    $labels[ 'not_found' ] = 'ZOMG, no text module found!!1!!1!!oneone!!!1!eleven!1!';\n\n    return $labels;\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>text_modules_post_type_supports\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This filter provides you with the post type supports.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the post type supports.\n *\n * @param array $supports Post type supports.\n *\u002F\nadd_filter( 'text_modules_post_type_supports', function( $supports ) {\n\n    \u002F\u002F Let's add revisions for our post type\n    if ( ! in_array( 'revisions', $supports ) ) {\n        $supports[] = 'revisions';\n    }\n\n    return $supports;\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>text_modules_shortcode_apply_do_shortcode\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>By default, do_shortcode() will be called on the shortcode output. Of course, you can change that.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter if the shortcode should apply do_shortcode() to the output.\n *\n * @param bool $do_shortcode Should the shortcode apply do_shortcode()?\n *\u002F\nadd_filter( 'text_modules_shortcode_apply_do_shortcode', '__return_false' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>text_modules_shortcode_callback\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>In case you would like to adapt how the shortcode data is handled, you can provide your own shortcode callback. This can either be a string holding the function name, or an array with either a class name or an object, and the according method.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the shortcode callback.\n *\n * @param array|string $callback Shortcode callback.\n *\u002F\nadd_filter( 'text_modules_shortcode_callback', function() {\n\n    return 'my_text_modules_shortcode_callback';\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>text_modules_shortcode_id_attribute_name\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This filter lets you alter the shortcode’s ‘id’ attribute name.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the 'id' shortcode attribute name.\n *\n * @param string $name Attribute name.\n *\u002F\nadd_filter( 'text_modules_shortcode_id_attribute_name', function() {\n\n    return 'post_id';\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>text_modules_shortcode_output\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This filter lets you alter the shortcode output. The second parameter holds the shortcode attributes array.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the shortcode output.\n *\n * @param string $output Shortcode output.\n * @param array  $atts   Shortcode attributes array.\n *\u002F\nadd_filter( 'text_modules_shortcode_output', function( $output ) {\n\n    return $output . ' Over and out.';\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>text_modules_shortcode_query_args\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Also, there’s \u003Ccode>text_modules_shortcode_query_args\u003C\u002Fcode>, which provides you with the complete args array for the shortcode’s query.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the shortcode query args.\n *\n * @param array $args Shortcode query args.\n *\u002F\nadd_filter( 'text_modules_shortcode_query_args', function( $args ) {\n\n    \u002F\u002F Exclude some text modules by ID\n    $args[ 'post__not_in' ] = array( 4, 8, 15, 16, 23, 42 );\n\n    return $args;\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>text_modules_shortcode_slug_attribute_name\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This filter lets you alter the shortcode’s ‘slug’ attribute name.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the 'slug' shortcode attribute name.\n *\n * @param string $name Attribute name.\n *\u002F\nadd_filter( 'text_modules_shortcode_slug_attribute_name', function() {\n\n    return 'post_slug';\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>text_modules_shortcode_tag\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>This filter lets you alter the shortcode’s tag.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the shortcode tag.\n *\n * @param string $shortcode_tag Shortcode tag.\n *\u002F\nadd_filter( 'text_modules_shortcode_tag', function() {\n\n    return 'text_block';\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>text_modules_shortcode_use_slug\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>By default, text modules are being queried by their post ID first. Of course, you can change that and use the post slug instead.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter if the shortcode (query) should use the post slug instead of the post ID.\n *\n * @param bool $use_slug Use slug instead of ID?\n *\u002F\nadd_filter( 'text_modules_shortcode_use_slug', '__return_true' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>\u003Ccode>text_modules_widget_form_query_args\u003C\u002Fcode>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Also, there’s \u003Ccode>text_modules_widget_form_query_args\u003C\u002Fcode>, which provides you with the complete args array for the widget form’s query.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u002F**\n * Filter the widget form query args.\n *\n * @param array $args Query args.\n *\u002F\nadd_filter( 'text_modules_widget_form_query_args', function( $args ) {\n\n    \u002F\u002F Exclude some text modules by ID\n    $args[ 'post__not_in' ] = array( 4, 8, 15, 16, 23, 42 );\n\n    return $args;\n} );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Contribution\u003C\u002Fh4>\n\u003Cp>To \u003Cstrong>contribute\u003C\u002Fstrong> to this plugin, please see its \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ftfrommen\u002Ftext-modules\" rel=\"nofollow ugc\">\u003Cstrong>GitHub repository\u003C\u002Fstrong>\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>If you have a feature request, or if you have developed the feature already, please feel free to use the Issues and\u002For Pull Requests section.\u003C\u002Fp>\n\u003Cp>Of course, you can also provide me with translations if you would like to use the plugin in another not yet included language.\u003C\u002Fp>\n","Use the new Text Modules custom post type and display a text module by either shortcode or widget.",50,2326,"2015-08-20T00:32:00.000Z","4.3.34","3.0.0",[86,87,88,89,90],"custom-post-type","module","modules","post","text","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Ftext-modules\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftext-modules.zip",{"slug":94,"name":95,"version":17,"author":5,"author_profile":6,"description":96,"short_description":97,"active_installs":45,"downloaded":98,"rating":34,"num_ratings":34,"last_updated":99,"tested_up_to":100,"requires_at_least":66,"requires_php":67,"tags":101,"homepage":106,"download_link":107,"security_score":9,"vuln_count":34,"unpatched_count":34,"last_vuln_date":35,"fetched_at":36},"adorable-avatars","Adorable Avatars","\u003Cp>This plugin integrates the \u003Ca href=\"http:\u002F\u002Favatars.adorable.io\u002F\" rel=\"nofollow ugc\">Adorable Avatars\u003C\u002Fa> avatar placeholder service into WordPress.\u003C\u002Fp>\n\u003Ch4>Contribution\u003C\u002Fh4>\n\u003Cp>To \u003Cstrong>contribute\u003C\u002Fstrong> to this plugin, please see its \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ftfrommen\u002Fadorable-avatars\" rel=\"nofollow ugc\">\u003Cstrong>GitHub repository\u003C\u002Fstrong>\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>If you have a feature request, or if you have developed the feature already, please feel free to use the Issues and\u002For Pull Requests section.\u003C\u002Fp>\n\u003Cp>Of course, you can also provide me with \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fadorable-avatars\" rel=\"nofollow ugc\">translations\u003C\u002Fa> if you would like to use the plugin in another not yet included language.\u003C\u002Fp>\n","This plugin integrates the Adorable Avatars avatar placeholder service into WordPress.",4502,"2017-01-04T15:47:00.000Z","4.7.32",[102,103,104,105],"avatar","image","profile","user","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fadorable-avatars\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fadorable-avatars.v2.1.0.zip",{"slug":109,"name":110,"version":111,"author":5,"author_profile":6,"description":112,"short_description":113,"active_installs":45,"downloaded":114,"rating":34,"num_ratings":34,"last_updated":115,"tested_up_to":65,"requires_at_least":66,"requires_php":67,"tags":116,"homepage":121,"download_link":122,"security_score":9,"vuln_count":34,"unpatched_count":34,"last_vuln_date":35,"fetched_at":36},"default-post-date","Default Post Date","1.5.1","\u003Cp>\u003Cstrong>Define an individual default post date that is to be used when adding a new post.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Have you ever had to create a fair amount of posts that all should be published on an individual date other than today?\u003C\u002Fp>\n\u003Cp>Maybe some reviews of an event a while back? Or a bunch of essays scheduled for the day after tomorrow?\u003C\u002Fp>\n\u003Cp>This is exactly when \u003Cem>Default Post Date\u003C\u002Fem> kicks in.\u003C\u002Fp>\n\u003Ch4>Contribution\u003C\u002Fh4>\n\u003Cp>To \u003Cstrong>contribute\u003C\u002Fstrong> to this plugin, please see its \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ftfrommen\u002Fdefault-post-date\" rel=\"nofollow ugc\">\u003Cstrong>GitHub repository\u003C\u002Fstrong>\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>If you have a feature request, or if you have developed the feature already, please feel free to use the Issues and\u002For Pull Requests section.\u003C\u002Fp>\n\u003Cp>Of course, you can also provide me with translations if you would like to use the plugin in another not yet included language.\u003C\u002Fp>\n","Define an individual default post date that is to be used when adding a new post.",2034,"2015-12-15T07:37:00.000Z",[117,118,89,119,120],"bulk","date","posts","publish","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdefault-post-date\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdefault-post-date.1.5.1.zip"]