[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fkyaPyRoOs9QQ-rAWZ0JslrhwQaHHowWQHDAjm2jyp_w":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},"makesites","Makis","https:\u002F\u002Fprofiles.wordpress.org\u002Fmakesites\u002F",2,20,85,30,84,"2026-04-04T11:03:13.389Z",[14,36],{"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":22,"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":22,"unpatched_count":22,"last_vuln_date":34,"fetched_at":35},"author-categories","Author Categories","1.0","\u003Cp>Numerous people are using WordPress for blogging and in many cases there are more than one authors on a website. It’s uncomfortably surprising that WordPress doesn’t support out of the box a category menu for each author separately.\u003C\u002Fp>\n\u003Cp>I was looking for this feature online for my personal need but couldn’t find it on any plugin. To be exact I was using a modified version of \u003Ca href=\"http:\u002F\u002Fwww.makesites.cc\u002Fprogramming\u002Fby-makis\u002Flevel10-blog-matrix-plugin-for-wordpress-2x\u002F\" rel=\"nofollow ugc\">another similar plugin\u003C\u002Fa> but that was until version 2.3 where the database structure changed for WordPress and it simply stopped working.\u003C\u002Fp>\n\u003Cp>As I saw it, it wasn’t worth fixing old, deprecated (and highly cluttered) code, and there weren’t any other solutions out there, so I decided to create a new plugin. Thankfully the new database and API made it as easy as I had hoped for.\u003C\u002Fp>\n\u003Cp>I ended up with this plugin, that was created as a wrapper of the default category menu.\u003C\u002Fp>\n\u003Cp>It is lightweight and can easily plug-in, plug-out. Furthermore, being an extension of the default category menu, means that none of the functionality (sorting, post count etc.) is lost. In fact it can be easily extended and could support future versions of the blogging platform for years to come.\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cp>After you upload an activate the plugin through your admin panel, all you need to do is call the custom function wp_author_categories() that will create an author’s menu for you. Notice that this only works in author pages and will revert to the default category menu in any other case.\u003C\u002Fp>\n\u003Cp>If you are using the default template, you can easily find this line in “sidebar.php” (that displays the category menu):\u003Cbr \u002F>\n            \u003C ?php wp_list_categories('show_count=1&title_li=Categories’); ?>\u003C\u002Fp>\n\u003Cp>You can replace it with this condition that will use the wp_author_categories() function instead, when you are visiting the author pages\u003C\u002Fp>\n\u003Cpre>\u003Ccode>        \u003C?php \n        \u002F*\n        * First write down the arguments you want to use for you menu and store them in a variable. \n        * These are the same for the default menu (\"wp_list_categories\") and the author menu (\"wp_author_categories\")\n        * you can find more information on the options you can use here: https:\u002F\u002Fcodex.wordpress.org\u002FTemplate_Tags\u002Fwp_list_categories\n        *\u002F\n        $args = 'show_count=1&title_li=\u003Ch2>Categories\u003C\u002Fh2>';\n        if($author){\n            wp_author_categories($args); \n        } else{\n            wp_list_categories($args); \n        }\n        ?>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Alternatively, and if you already have an “author.php” file in your template folder, you can simply rename “wp_list_categories()” to “wp_author_categories()”, passing the same arguments.\u003C\u002Fp>\n\u003Cp>To uninstall, it’s as easy as doing the reverse actions. Delete all references of the wp_author_categories() function from your template files and uninstall the plugin through that WordPress’s admin panel.\u003C\u002Fp>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>This work is released under the terms of the GNU General Public License:\u003Cbr \u002F>\nhttp:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-2.0.txt\u003C\u002Fp>\n","A wrapper of the default 'wp_list_categories' to present an author's menu, when in the author pages.",10,4410,0,"2009-04-11T10:28:00.000Z","2.7.1","2.5","",[28,29,30,31],"author","categories","menu","post-count","http:\u002F\u002Fwww.makesites.cc\u002Fprojects\u002Fwp_author_categories","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fauthor-categories.1.0.zip",null,"2026-03-15T15:16:48.613Z",{"slug":37,"name":38,"version":17,"author":5,"author_profile":6,"description":39,"short_description":40,"active_installs":20,"downloaded":41,"rating":22,"num_ratings":22,"last_updated":42,"tested_up_to":43,"requires_at_least":25,"requires_php":26,"tags":44,"homepage":50,"download_link":51,"security_score":9,"vuln_count":22,"unpatched_count":22,"last_vuln_date":34,"fetched_at":35},"post-version-control","Post Version Control","\u003Cp>Posts can be grouped in many ways in WordPress but there is no direct version control system. This plugin offers a lightweight solution if you want version control for a group of posts.\u003C\u002Fp>\n\u003Cp>To make this work you define a keyword for each version control group you want to create. Then use that keyword as a prefix in the post name of each post in that group. The plugin will sort out the latest post automatically and label the rest as outdated.\u003C\u002Fp>\n\u003Cp>It also let’s you have a URL that will always point to the latest post of that version control group. That way you can give out the URL to others and be sure that your visitors will always be viewing the most recent post.\u003C\u002Fp>\n\u003Cp>This plugin will automatically:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Define if a post is part of a version control group. \u003C\u002Fli>\n\u003Cli>Search and locate the latest post by publish date.\u003C\u002Fli>\n\u003Cli>Label the older posts of the group as outdated.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This is especially practical for bloggers that often revisit older subjects and have to do the linking with the updated posts manually. Or if you are like me and publish material that has versioning applied to it (ex. software) through a blogging platform.\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cp>First thing you should do is visit the plugin’s options page (“Settings” -> “Post Version Control”).\u003C\u002Fp>\n\u003Cp>There you will find two fields:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\n\u003Cp>The keyword list field, where you enter all the keywords you want to track seperated from each other by a comma and a space “, “. Each of them defines a different version control group.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>The path for the latest posts URL. By default the path is “\u002Fcurrent”. So if we have a keyword named “ajax” the URL: http:\u002F\u002Fwww.myblogaddress.com\u002Fcurrent\u002Fajax will point to the latest post of the “ajax” group.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>To link a post to a version control group of posts all you need to do is enter the keyword of that group as a prefix to the post_name of that post. So in the group “ajax” mentioned earlier all posts in that group should start with the “ajax-” prefix. An example list of that group of posts might be:\u003C\u002Fp>\n\u003Col>\n\u003Cli>ajax-first-post\u003C\u002Fli>\n\u003Cli>ajax-updated-version\u003C\u002Fli>\n\u003Cli>ajax-latest-news\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>..and so on.\u003C\u002Fp>\n\u003Cp>The plugin will automatically look through your posts of the same group and label the older ones by inserting an \u003C!– outdated –> tag. This is replaced by the content of “outdated.html” in runtime. This is an example of how you can style your outdated tag. Just insert it along with your other styles:\u003C\u002Fp>\n\u003Cp>\u003Cstyle>\u003C\u002Fp>\n\u003Cp>p.outdated{\u003Cbr \u002F>\n  border: dashed 1px #f00;\u003Cbr \u002F>\n  background: #eee;\u003Cbr \u002F>\n  color: #f00;\u003Cbr \u002F>\n  text-align: center;\u003Cbr \u002F>\n}\u003C\u002Fp>\n\u003Cp>p.outdated a {\u003Cbr \u002F>\n  color: #f00;\u003Cbr \u002F>\n}\u003C\u002Fp>\n\u003Cp>\u003C\u002Fstyle>\u003C\u002Fp>\n\u003Cp>Uninstalling should be pretty easy too. The only left overs are the \u003C!– outdated: … –> comments in the old posts content which of course are ignored when viewing the webpage. If you don’t mind that you don’t have to do anything else apart from de-activating the plugin through your WordPress administration.\u003C\u002Fp>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>This work is released under the terms of the GNU General Public License:\u003Cbr \u002F>\nhttp:\u002F\u002Fwww.gnu.org\u002Flicenses\u002Fgpl-2.0.txt\u003C\u002Fp>\n","Automatic version control for posts with the same prefix in the post_name",2336,"2008-05-29T14:23:00.000Z","2.5.1",[45,46,47,48,49],"automatic","revision","subversion","svn","version-control","http:\u002F\u002Fwww.makesites.cc\u002Fprojects\u002Fpvc","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpost-version-control.1.0.zip"]