[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fd0xwBHgxv21oQn1QDlnHAc-CMrJmqEYk7tWZNiqQS3Y":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},"batmoo","Mohammad Jangda","https:\u002F\u002Fprofiles.wordpress.org\u002Fbatmoo\u002F",5,1340,85,30,84,"2026-04-04T06:22:23.272Z",[14,37,56,75,94],{"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":7,"last_updated":23,"tested_up_to":24,"requires_at_least":25,"requires_php":26,"tags":27,"homepage":32,"download_link":33,"security_score":9,"vuln_count":34,"unpatched_count":34,"last_vuln_date":35,"fetched_at":36},"custom-metadata","Custom Metadata Manager","0.7.1","\u003Cp>An easy way to add custom fields to your object types (post, pages, custom post types, users) & to generate option pages.\u003C\u002Fp>\n\u003Cp>The goal of this plugin is to help you rapidly build familiar, intuitive interfaces for your users in a very WordPress-native way.\u003C\u002Fp>\n\u003Cp>The custom field panel is nice, but not quite the easiest thing for users to work with. Adding your own metaboxes and fields involves a lot of time and repetitive code that could be better used elsewhere.\u003C\u002Fp>\n\u003Cp>This plugin handles all that heavy-lifting for you behind-the-scenes, so that you can focus on more on building out and connecting your data rather than all the minor details. This single piece of code \u003Ccode>x_add_metadata_field( 'my-field-name', 'post' );\u003C\u002Fcode> generates a metabox with a text field inside it, with the necessary hooks to save the entered values.\u003C\u002Fp>\n\u003Cp>The API is similar to that used for registering custom post types and taxonomies so it should be familiar territory.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>NOTE\u003C\u002Fstrong>: The plugin now requires WordPress 3.3+ (chiefly for the wysiwyg & datepicker fields)\u003C\u002Fp>\n\u003Cp>Like what you see? Want more field types and features added? \u003Ca href=\"mailto:tech@stresslimitdesign.com\" rel=\"nofollow ugc\">Get in touch\u003C\u002Fa> or \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fjkudish\u002Fcustom-metadata\" rel=\"nofollow ugc\">contribute on github\u003C\u002Fa>\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>\u003Cem>See “Other Notes” section for usage information\u003C\u002Fem>\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Ch4>Object Types\u003C\u002Fh4>\n\u003Cp>The main idea behind this plugin is to have a single API to work with regardless of the object type. Currently, Custom Metadata Manager works with \u003Ccode>user\u003C\u002Fcode>, \u003Ccode>comment\u003C\u002Fcode> and any built-in or custom post types, e.g. \u003Ccode>post\u003C\u002Fcode>, \u003Ccode>page\u003C\u002Fcode>, etc.\u003C\u002Fp>\n\u003Ch4>Registering your fields\u003C\u002Fh4>\n\u003Cp>For the sake of performance (and to avoid potential race conditions), always register your custom fields in the \u003Ccode>admin_menu\u003C\u002Fcode> hook. This way your front-end doesn’t get bogged down with unnecessary processing and you can be sure that your fields will be registered safely. Here’s a code sample:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_action( 'admin_menu', 'my_theme_init_custom_fields' );\n\nfunction my_theme_init_custom_fields() {\n    if( function_exists( 'x_add_metadata_field' ) && function_exists( 'x_add_metadata_group' ) ) {\n        x_add_metadata_field( 'my_field', array( 'user', 'post' ) );\n    }\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Getting the data\u003C\u002Fh4>\n\u003Cp>You can get the data as you normally would using the \u003Ccode>get_metadata\u003C\u002Fcode> function. Custom Metadata manager stores all data using the WordPress metadata APIs using the slug name you provide. That way, even if you decide to deactivate this wonderful plugin, your data is safe and accessible. For options, you can use \u003Ccode>get_option\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$value = get_metadata( 'post', get_the_ID(), 'featured', true ); \u002F\u002F Returns post metadata value for the field 'featured'\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Adding Metadata Groups\u003C\u002Fh4>\n\u003Cp>A group is essentially a metabox that groups together multiple fields. Register the group before any fields\u003C\u002Fp>\n\u003Cpre>\u003Ccode>x_add_metadata_group( $slug, $object_types, $args );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Parameters\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>$slug\u003C\u002Fcode> (string) The key under which the metadata will be stored.\u003C\u002Fli>\n\u003Cli>\u003Ccode>$object_types\u003C\u002Fcode> (string|array) The object types to which this field should be added. Supported: post, page, any custom post type, user, comment.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Options and Overrides\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$args = array(\n    'label' => $group_slug, \u002F\u002F Label for the group\n    'context' => 'normal', \u002F\u002F (post only)\n    'priority' => 'default', \u002F\u002F (post only)\n    'autosave' => false, \u002F\u002F (post only) Should the group be saved in autosave? NOT IMPLEMENTED YET!\n    'exclude' => '', \u002F\u002F see below for details\n    'include' => '', \u002F\u002F see below for details\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Adding Metadata Fields\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>x_add_metadata_field( $slug, $object_types, $args );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Parameters\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>$slug\u003C\u002Fcode> (string) The key under which the metadata will be stored. For post_types, prefix the slug with an underscore (e.g. \u003Ccode>_hidden\u003C\u002Fcode>) to hide it from the the Custom Fields box.\u003C\u002Fli>\n\u003Cli>\u003Ccode>$object_types\u003C\u002Fcode> (string|array) The object types to which this field should be added. Supported: post, page, any custom post type, user, comment.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Options and Overrides\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$args = array(\n    'group' => '', \u002F\u002F The slug of group the field should be added to. This needs to be registered with x_add_metadata_group first.\n    'field_type' => 'text', \u002F\u002F The type of field; 'text', 'textarea', 'password', 'checkbox', 'radio', 'select', 'upload', 'wysiwyg', 'datepicker', 'taxonomy_select', 'taxonomy_radio'\n    'label' => '', \u002F\u002F Label for the field\n    'description' => '', \u002F\u002F Description of the field, displayed below the input\n    'values' => array(), \u002F\u002F Values for select and radio buttons. Associative array\n    'display_callback' => '', \u002F\u002F Callback to custom render the field\n    'sanitize_callback' => '', \u002F\u002F Callback to sanitize data before it's saved\n    'display_column' => false, \u002F\u002F Add the field to the columns when viewing all posts\n    'display_column_callback' => '', \u002F\u002F Callback to render output for the custom column\n    'required_cap' => '', \u002F\u002F The cap required to view and edit the field\n    'exclude' => '', \u002F\u002F see below for details\n    'include' => '', \u002F\u002F see below for details\n    'multiple' => false, \u002F\u002F true or false, can the field be duplicated with a click of a button?\n    'readonly' => false, \u002F\u002F makes the field be readonly (works with text, textarea, password, upload and datepicker fields)\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Include \u002F Exclude\u003C\u002Fh4>\n\u003Cp>You can exclude fields and groups from specific object. For example, with the following, field-1 will show up for all posts except post #123:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$args = array(\n    'exclude' => 123\n);\nx_add_metadata_field( 'field-1', 'post', $args );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Alternatively, you can limit (“include”) fields and groups to specific objects. The following will ”only” show group-1 to post #456:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$args = array(\n    'include' => 123\n);\nx_add_metadata_group( 'group-1', 'post', $args );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You can pass in an array of IDs:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$args = array(\n    'include' => array( 123, 456, 789 );\n);\n\nWith multiple object types, you can pass in an associative array:\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>$args = array(\u003Cbr \u002F>\n    ‘exclude’ => array(\u003Cbr \u002F>\n        ‘post’ => 123,\u003Cbr \u002F>\n        ‘user’ => array( 123, 456, 789 )\u003Cbr \u002F>\n    )\u003Cbr \u002F>\n);\u003C\u002Fp>\n\u003Ch4>Examples\u003C\u002Fh4>\n\u003Cp>For examples, please see the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fjkudish\u002Fcustom-metadata\u002Fblob\u002Fmaster\u002Fcustom_metadata_examples.php\" rel=\"nofollow ugc\">custom_metadata_examples.php\u003C\u002Fa> file included with the plugin. Add a constant to your wp-config.php called \u003Ccode>CUSTOM_METADATA_MANAGER_DEBUG\u003C\u002Fcode> with a value of \u003Ccode>true\u003C\u002Fcode> to see it in action:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'CUSTOM_METADATA_MANAGER_DEBUG', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>TODOs\u003C\u002Fh4>\n\u003Cp>Stuff we have planned for the future:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Ability to clone (multiple) groups of fields\u003C\u002Fli>\n\u003Cli>Ability Pass in attributes for built-in fields (e.g. class, data-*, etc.)\u003C\u002Fli>\n\u003Cli>Additional field types (multi-select, multi-checkbox)\u003C\u002Fli>\n\u003Cli>Limit or exclude groups and fields using a custom callback\u003C\u002Fli>\n\u003Cli>Autosave support for fields on post types\u003C\u002Fli>\n\u003Cli>Client- and server-side validation support\u003C\u002Fli>\n\u003Cli>Add groups and fields to Quick Edit\u003C\u002Fli>\n\u003C\u002Ful>\n","An easy way to add custom fields to your object types (post, pages, custom post types, users)",800,16509,88,"2012-07-11T19:02:00.000Z","3.4.2","3.3","",[15,28,29,30,31],"custom-metadata-manager-metadata","post-meta","postmeta","user-meta","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fcustom-metadata\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcustom-metadata.0.7.1.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":43,"downloaded":44,"rating":45,"num_ratings":46,"last_updated":47,"tested_up_to":48,"requires_at_least":49,"requires_php":26,"tags":50,"homepage":54,"download_link":55,"security_score":9,"vuln_count":34,"unpatched_count":34,"last_vuln_date":35,"fetched_at":36},"plugin-notes","Plugin Notes","1.6","\u003Cp>Allows you to add notes to plugins. Useful when you’re using lots of plugins and\u002For make modifications to a plugin and want to make a note of them, and\u002For work on your WordPress install with a group of people. This plugin was inspired by a post by \u003Ca href=\"http:\u002F\u002Fdigwp.com\" rel=\"nofollow ugc\">Chris Coyier\u003C\u002Fa>: (http:\u002F\u002Fdigwp.com\u002F2009\u002F10\u002Fideas-for-plugins\u002F)\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Add\u002Fedit\u002Fdelete notes for each plugin on the plugin page\u003C\u002Fli>\n\u003Cli>You can use HTML in notes (v1.1+)\u003C\u002Fli>\n\u003Cli>You can use \u003Ca href=\"http:\u002F\u002Fdaringfireball.net\u002Fprojects\u002Fmarkdown\u002Fsyntax\" rel=\"nofollow ugc\">markdown syntax\u003C\u002Fa> in notes (v1.5+)\u003C\u002Fli>\n\u003Cli>You can use a number of variables which will be automagically replaced when the note displays (v1.5+)\u003C\u002Fli>\n\u003Cli>Save a note as a template for new notes (v1.5+)\u003C\u002Fli>\n\u003Cli>You can color-code notes to see in one glance what’s up or down (v1.6+)\u003C\u002Fli>\n\u003Cli>Links within note automagically have \u003Ccode>target=\"_blank\"\u003C\u002Fcode> added so you won’t accidently leave your site while working with the plugins.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Please have a look at the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fplugin-notes\u002Ffaq\u002F\" rel=\"ugc\">FAQ\u003C\u002Fa> for more information about these features.\u003C\u002Fp>\n\u003Ch4>Credits\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Markdown script\u003C\u002Fstrong>: \u003Ca href=\"http:\u002F\u002Fmichelf.ca\u002Fprojects\u002Fphp-markdown\u002F\" rel=\"nofollow ugc\">PHP Markdown 1.0.1.o\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>External link indicator\u003C\u002Fstrong>: liberally nicked from the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fbwp-external-links\u002F\" rel=\"ugc\">Better WP External Links\u003C\u002Fa> plugin\u003C\u002Fp>\n\u003Ch4>Translations\u003C\u002Fh4>\n\u003Cp>Dutch – \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fprofile\u002Fjrf\" rel=\"ugc\">jrf\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Please help us make this plugin available in more language by translating it. See the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fplugin-notes\u002Ffaq\u002F\" rel=\"ugc\">FAQ\u003C\u002Fa> for more info.\u003C\u002Fp>\n","Allows you to add notes to plugins.",500,14446,100,26,"2015-07-16T22:45:00.000Z","4.2.39","3.5",[51,52,38,53],"memo","meta","plugins","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fplugin-notes\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fplugin-notes.1.6.zip",{"slug":57,"name":58,"version":59,"author":5,"author_profile":6,"description":60,"short_description":61,"active_installs":62,"downloaded":63,"rating":62,"num_ratings":64,"last_updated":65,"tested_up_to":66,"requires_at_least":67,"requires_php":26,"tags":68,"homepage":73,"download_link":74,"security_score":9,"vuln_count":34,"unpatched_count":34,"last_vuln_date":35,"fetched_at":36},"html-emails","HTML Emails","1.0","\u003Cp>Converts the default plain-text email notifications into fully customizable, sweet-lookin’ HTML emails.\u003C\u002Fp>\n\u003Cp>Multi-site support (for WordPress 3.0) will be added soon.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Notes:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Emails are sent with readable plain-text versions for email clients that don’t support HTML emails. Note: they’re somewhat crude because they’re auto-generated. I may decide to add decent-looking plain-text versions in the future, but that’s low priority.\u003C\u002Fli>\n\u003Cli>Emails have only been tested on Gmail, Gmail on Android, and Outlook, but should work on most email clients (including clients without HTML support). If you’re using a client other than the 3 I’ve listed, I would appreciate \u003Ca href=\"mailto:batmoo@gmail.com\" rel=\"nofollow ugc\">an email\u003C\u002Fa> with info on whether the email looks like it should and works correctly.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Send your questions, comments, suggestions \u003Ca href=\"mailto:batmoo@gmail.com\" rel=\"nofollow ugc\">via email\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Customizing Templates\u003C\u002Fh3>\n\u003Cp>You can fully customize the look of any of the emails by creating your own templates. Emails have two pieces:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Email Wrapper (content common across all emails)\u003C\u002Fli>\n\u003Cli>Email Message (content unique to each email)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Custom templates can be created an placed in either your theme directory or your Content directory (\u002Fwp-content\u002F on most sites). See utils.php for a number of useful functions that you can use in your templates.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Email Wrapper\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The Email Wrapper includes elements and markup that are common across all email notifications. It contains your html, head and body tags and any other elements that are shared across emails.\u003C\u002Fp>\n\u003Cp>To customize the email template, create a file called \u003Ccode>html_email.php\u003C\u002Fcode> and add it to either your theme or content directory.\u003C\u002Fp>\n\u003Cp>Note: you must include the following code in the template to work:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003C?php htmlize_message_body($email_templates, $email_data); ?>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The Email Wrapper has access to the following variables:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>$email_title: (string) title of the email\u003C\u002Fli>\n\u003Cli>$email_subtitle: (string) subtitle of the email\u003C\u002Fli>\n\u003Cli>$email_data: (array) Associative array of various data passed by the calling function\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Email Message: New Comment\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>By default, new comment and comment moderation emails share the same template. You can create separate templates for both for each comment type by creating the following files:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>notify_postauthor_comment.php\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>notify_postauthor_trackback.php\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>notify_postauthor_pingback.php\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>notify_moderator_comment.php\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>notify_moderator_trackback.php\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>notify_moderator_pingback.php\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you don’t want to customize the emails by comment type, just create the following two templates:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>notify_postauthor.php\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>\u003Ccode>notify_moderator.php\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>If you just want a custom template shared between the two notification types, just create the following:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>notify_comment.php\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>New Comment email messages have the following data variables available:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>$comment              – (obj) comment object\u003C\u002Fli>\n\u003Cli>$post                 – (obj) post object \u003C\u002Fli>\n\u003Cli>$comment_type         – (string) slug for the comment_type\u003C\u002Fli>\n\u003Cli>$comment_type_text    – (string) friendly name for the comment_type\u003C\u002Fli>\n\u003Cli>$comment_moderate     – (bool) Whether the comment needs moderation or not\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Using HTML Emails in your plugin\u003C\u002Fh3>\n\u003Cp>It’s pretty easy to use. The main call you need to make is htmlize_message() and pass the return into your wp_mail object. Details to come.\u003C\u002Fp>\n\u003Ch3>Credits\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Blockquote image borrowed from the amazing \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fthemes\u002Fwu-wei\" rel=\"ugc\">Wu Wei theme by Jeff Ngan\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Plain Text conversion script by \u003Ca href=\"http:\u002F\u002Fwww.chuggnutt.com\u002Fhtml2text.php\" rel=\"nofollow ugc\">Jon Abernathy aka Chuggnutt\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Email styling inspired by \u003Ca href=\"http:\u002F\u002Fen.support.wordpress.com\u002Fblog-subscriptions\u002F\" rel=\"nofollow ugc\">WordPress.com Blog Subscription Notifications\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Converts the default plain text email notifications into fully customizable, sweet-lookin' HTML emails.",20,7680,1,"2010-05-05T16:06:00.000Z","3.0.5","2.9",[69,70,71,57,72],"email","html","html-email","notification","http:\u002F\u002Fdigitalize.ca","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhtml-emails.1.0.zip",{"slug":76,"name":77,"version":78,"author":5,"author_profile":6,"description":79,"short_description":80,"active_installs":81,"downloaded":82,"rating":83,"num_ratings":64,"last_updated":84,"tested_up_to":26,"requires_at_least":85,"requires_php":26,"tags":86,"homepage":92,"download_link":93,"security_score":9,"vuln_count":34,"unpatched_count":34,"last_vuln_date":35,"fetched_at":36},"in-over-your-archives","In Over Your Archives","1.4.3","\u003Cp>This plugin will display your archive page in a nice way, just like on inoveryourhead.net\u003C\u002Fp>\n\u003Ch4>Shortcode filtering\u003C\u002Fh4>\n\u003Cp>If you are using the In Over Your Archives shortcode [ioya] to embed the plugin on a page and would like to do category filtering on\u003Cbr \u002F>\nyour archive results, you may do so by providing the category slug(s) or ID(s), (or a mix) like so:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[ioya cat='trees']\n[ioya cat='03,45']\n[ioya cat='trees,45,trucks']\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Customizing the template\u003C\u002Fh4>\n\u003Cp>You can customize the look and feel of the archives pages.\u003C\u002Fp>\n\u003Cp>Add a file called \u003Ccode>ioya_month.php\u003C\u002Fcode> to your theme directory and add a basic loop in it as follows:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003C?php while (have_posts()) : the_post(); ?>\n\n    \u003Cdiv class=\"post\">    \n        \u003Cdiv class=\"date\">\n            \u003Cdiv class=\"date-day\">\u003C?php the_time('j') ?>\u003C\u002Fdiv>\n            \u003Cdiv class=\"date-month\">\u003C?php the_time('M') ?>\u003C\u002Fdiv>\n        \u003C\u002Fdiv>\n        \u003Ch2>\u003Ca href=\"\u003C?php the_permalink() ?>\" rel=\"bookmark\" title=\"Permanent Link to \u003C?php the_title_attribute(); ?>\">\u003C?php the_title(); ?>\u003C\u002Fa>\u003C\u002Fh2>\n        \u003Csmall>Posted by \u003C?php the_author_link() ?> at \u003C?php the_time('g:i A') ?>\u003C\u002Fsmall>\n        \u003Cdiv class=\"entry\">\n            \u003C?php the_excerpt(); ?>\n        \u003C\u002Fdiv>\n    \u003C\u002Fdiv>\n\u003C?php endwhile; ?>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Then modify as necessary.\u003C\u002Fp>\n","This plugin will display your archive page in a nice way, just like on inoveryourhead.net",10,7598,80,"2011-05-17T18:12:00.000Z","2.9.2",[87,88,89,90,91],"archive","archives","inoveryourhead","julien-smith","posts","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fin-over-your-archives\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fin-over-your-archives.1.4.3.zip",{"slug":95,"name":96,"version":97,"author":5,"author_profile":6,"description":98,"short_description":99,"active_installs":81,"downloaded":100,"rating":34,"num_ratings":34,"last_updated":101,"tested_up_to":102,"requires_at_least":103,"requires_php":26,"tags":104,"homepage":73,"download_link":108,"security_score":9,"vuln_count":34,"unpatched_count":34,"last_vuln_date":35,"fetched_at":36},"zen","Zen","1.2","\u003Cp>A distraction-free environment for blogging; inspired by Habari, OmmWriter, WriteRoom, and the countless wasted hours I’ve spent staring at blank screens.\u003C\u002Fp>\n\u003Cp>If you’re a fan of \u003Ca href=\"http:\u002F\u002Fwww.hogbaysoftware.com\u002Fproducts\u002Fwriteroom\" rel=\"nofollow ugc\">WriteRoom\u003C\u002Fa>, \u003Ca href=\"http:\u002F\u002Fwww.ommwriter.com\u002F\" rel=\"nofollow ugc\">OmmWriter\u003C\u002Fa>, or similar tools that help you focus on your words instead of the tools you’re using, this plugin will soon make your wildest dreams come true (and give you a simple clean environment to write to your heart’s content)!\u003C\u002Fp>\n\u003Cp>While Zen does not replace the existing Edit Post\u002FPage screen, it provides a layer on top that allows you to focus on your writing. You get an input box for the title a regular ol’ textbox to add your post (feel free to use HTML).\u003C\u002Fp>\n\u003Cp>NOTE: Zen requires PHP 5+. Not on PHP 5 yet? Talk to your hosting provider and get them to upgrade! You can thank me later.\u003C\u002Fp>\n\u003Cp>If you’re a designer (or even just a regular Jane or Joe) and have any ideas for themes, please \u003Ca href=\"mailto:batmoo@gmail.com\" rel=\"nofollow ugc\">get in touch\u003C\u002Fa>! I’d love to add it to Zen!\u003C\u002Fp>\n\u003Cp>If you have any ideas for Zen or features you’d like to see included, please \u003Ca href=\"mailto:batmoo@gmail.com\" rel=\"nofollow ugc\">get in touch\u003C\u002Fa>!\u003C\u002Fp>\n\u003Cp>Zen was inspired by \u003Ca href=\"http:\u002F\u002Fifranky.com\u002F2010\u002F01\u002Fwordpress-vs-bloat\u002F\" rel=\"nofollow ugc\">this post on Habari\u003C\u002Fa> by \u003Ca href=\"http:\u002F\u002Fifranky.com\u002F\" rel=\"nofollow ugc\">ifranky\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Special thanks to \u003Ca href=\"http:\u002F\u002Fandrewspittle.net\" rel=\"nofollow ugc\">Andrew Spittle\u003C\u002Fa> for helping me out the with theme designs.\u003C\u002Fp>\n","A distraction-free environment for blogging; inspired by Habari, OmmWriter, WriteRoom, and countless wasted hours of staring at blank screens.",4292,"2010-12-06T23:53:00.000Z","3.1.4","2.9.1",[105,106,91,107,95],"distraction","edit-posts","writing","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fzen.1.2.zip"]