A few days back I pushed through an update of Knowledgebase v1.3.0. Knowledgebase is my relatively new plugin that I released last year when building WebberZone.
It’s designed to be very simple to use to set up your own Knowledgebase. The latest release incorporates a very important uninstall feature. You can now choose to delete options when you uninstall the plugin and/or delete all knowledgebase data. This is if you want to completely clean out all articles as well as sections and categories, you’d select the section option.
This does effectively mean that you’re nuking your knowledgebase and can only be restored if you chose to backup your site before. Use with caution…
Complete changes in Knowledgebase v1.3.0
Articles now support comments
Two new settings to delete all settings and Knowledgebase content when deleting the plugin.
Fixed labels where Section was still called Category
After more than two years, I decided it was high time to rework my plugin Add to All in order to bring it more compatible with the latest versions of WordPress. And, to also bring it out of an “abandoned” status.
The biggest change in this version is migrating the settings to the WordPress Settings API. It also brings a brand new tabbed interface for each of the settings. When you upgrade, please do visit the settings page and check that all your settings are properly migrated.
I’ve been working on Top 10 v2.4.0 for a long time where the main focus of this release has been to get a more compatible tracker. Today, I’m happy to say that I have pushed through the release and you can now upgrade your favourite popular posts plugin as you normally would from within your WordPress Dashboard Updates screen. This version adds two new features, fixes several bugs, has cleaner code as per WordPress Coding Standards and also deprecates some functions.
Two months back I released v2.3.2 which fixed a security issue and also required me to remove the faster performance tracker. This was needed to ensure continued hosting with WordPress.org and respecting their guidelines. v2.4.0 is the first step towards building an addon that will bring back the faster tracker. This addon will be available for free from this website in the near future.
For now, you have two options for the tracker. Try both to see which delivers a better performance to your site. The first uses an external .js file that can be cached by browsers. The second is the old query style format. From my testing, both have similar performance. But, do toggle between both options to see which performs better. For the brave at heart, you can also adapt this gist which is the old source code for the faster tracker.
Now you can “offset” your posts
Another very useful feature that I’ve added in v2.4.0 is the ability to offset the list of posts by a specific number. This is available via the shortcode or in the widget.
Using the offset you can now display posts starting from a different position e.g. display posts from 11 to 20 by setting it to offset to 10. It also helps if you would like to display multiple versions of the widget with different starting points.
As usual, if you’re looking for support, please create a new post in the Top 10 support forum. And, do blog, tweet and tell the whole world about this release.
Detailed list of changes in Top 10 v2.4.0
New tracker using a properly enqueued .js file. Two inbuilt options to use query variables or ajaxurl to process the counts
Shortcode and the widget now have an added parameter for ‘offset’. This is useful if you would like to display different widgets/shortcodes but not always start from the first post
Attachments now work with the widget and elsewhere
New tracker now works when jQuery is loaded in the footer
Don’t add tracker code when previewing in customizer
Doesn’t report an error if no author is assigned to a post
tptn_add_tracker and tptn_add_viewed_count have been deprecated. These should no longer be needed with the new tracker option.
wick script in Settings page which was used for fetching category slugs. You should now use the category name (prompted automatically). Slugs will be automatically converted into names.
On Saturday, I released a new version of Top 10, my popular posts plugin for WordPress. v2.3.0 brings several new features and fixes a lot of bug. This version will be one of major releasesfor a while as I begin to develop a pro addon which should bring several new features. Of course, I’ll continue to release bug fixes and minor new features.
I’ve released Knowledgebase v1.2.0 with a new settings page that allows you to change the permalink slugs. This now gives you the flexibility of having specific settings that work best for your WordPress blog.
Besides this, there have been several updates, code cleanups and bug fixes that make this a version you just have to try.
I released Better Search v2.1.0 yesterday. Following in the footsteps of Top 10 and Contextual Related Posts, Better Search has found its way under the WebberZone umbrella officially from this version.
Existing users of Better Search can upgrade the plugin from within their admin interface itself. The changes to this version include:
Banned terms will now filter the main search query and will no longer display the search term even in seamless mode
Highlighting now works when the search term has double or single quotes
Read the release notes in detail on the WebberZone blog. If you’re looking for support, please create a new post in the support forum. This still remains the most efficient way for you to get your questions answered.
I pushed updates to Top 10 and Contextual Related Posts last week. The main changes are better support for WPML especially the ability to display the posts in the current post language. This could potentially cause some clashes with other plugins e.g. Polylang, which I am continuing to investigate.
Another major change is to the text domain, i.e. what the plugins have used for translations. Following the announcement of the new translation system announced by WordPress.org, I’ve modified the text domains to match the plugin slugsi.e. contextual-related-posts and top-10 respectively. This will eventually result in lower plugin download files and most importantly localised and better maintained languages for Contextual Related Posts in your language.
As I mentioned before, WebberZone is the new platform (or should I say revamped) platform for my WordPress development which is currently focussed on developing GPL plugins (both free and premium).
This release of Top 10 comes with a brand new interface to view the popular posts in the Admin area. It is better integrated and you can now sort the views easily across all your posts/pages and custom post types. You can continue to view the counts in your posts / pages listings as earlier.
In addition to the new admin interface, Top 10 v2.2.3 also adds an inbuilt caching system that utilises the Transients API, has an updated styles selection interface. To view complete details, please check out the official release post on the WebberZone blog.
As usual, if you got a support query, then please create a new post at the WordPress.org support forum. It is the fastest way to get support as I monitor the forums regularly.
I’ve released v2.2.0 of my most popular plugin Contextual Related Posts today. It also marks an important moment in its development, as the plugin is almost completely rebranded and now available via WebberZone, a platform that will eventually host all my major WordPress projects.
Contextual Related Posts v2.2.0 has several new features, some enhancements to existing features and some bug fixes. Existing users can upgrade the plugin via their Updates screen in the WordPress admin area.
Two main features are the ability to turnoff related posts on a post by post basis as well as specify a set of manual related posts which are given a higher priority over the automatic related posts.
CRP Taxonomy Tools allows you to restrict the related posts generated by Contextual Related Posts to the same category and tag. At least, it used to until now.
Support for Custom Taxonomies
v1.1.0 now adds support to custom taxonomies as well. This is especially useful to custom post types where the quality of the related post may not be the most ideal set. e.g. if you’re running a movie review blog and you have two different taxonomies for actors and genres, you can now restrict the related posts on your custom post types to just these taxonomies.
Disable Contextual Matching
Another feature that I have added to the plugin is the ability to disable contextual matching. This will turn of the core feature that Contextual Related Posts is built on and so is available only as part of this addon. If you do choose to disable contextual matching, make sure that you turn on the restricting by same categories, tags or custom taxonomies. Otherwise, all your posts will return the same related posts.
You’ll also find a new option that let’s you restrict the non-contextual matching only to attachments / media and custom post types only.
If you activate this option, then posts and pages will continue to show truly related posts. Attachments and custom post types will no longer show contextual matched posts, but would remain restricted to posts from the same category, tags or custom taxonomy.
CRP Taxonomy Tools is a very useful addon that enables that extra level of relatedness that you might want to add to your site. If you’re using this plugin and might be looking to get some questions answered, then please make a new post in the Support Forum. Comments below asking for support are likely to be ignored.
If you like this addon, then do consider a 5-star review as well. It’s always encouraging when I read something nice about the work that I do 🙂