There are numerous ways of how to modify the WordPress tag cloud widget, but there’s an easy way to modify it. I searched about how to modify such, and landed on different blogs sharing different methods to modify the widget. I also landed on this page which tells everyone to modify the WordPress core. But I don’t think it’s the best solution to customize your WordPress Tag cloud.
If you’re an Elegant Themes user and you’re a complete PHP noob and you want to add “All Categories” as an additional option in your featured category inside your ePanel, because by default, there are no “All Categories” option in the featured category options of Elegant Themes’ ePanel, then your search is over.
Out of curiosity, I tested the auto-embed feature of WordPress if it still works in YouTube videos, and it still did. Check out the YouTube video below. I didn’t use an IFRAME at all and it still displays just fine.
Because I’m so vain with my WordPress admin, I decided to customize my Fluency plugin. Thanks again to Dean for making this customization easy as ABC and for updating Fluency to be compatible to WordPress 3.2. This post will not teach you how to customize your own Fluency admin, because it’s so easy to do so. Even a 3rd grader can customize it in minutes. What I want to do now is showcase my awesome WP-admin, powered by Fluency. Check out the image below:
I shared about Fluency before and its incompatibility with WordPress 3.2. Now, Dean, the geek behind 47 robots updated its awesome WP-admin plugin, and it’s now upgraded to Fluency Admin 3.2. So for those who are using Fluency Admin, and deactivated it because it’s not compatible with the latest WP version, now is the time to rejoice, because our precious Fluency admin plugin is now compatible with WP 3.2!
Wow, I just noticed that my blog is now full of WordPress fatal errors and how to fix it. I admit, I’m a certified WordPress junkie. Haha! This is my 78th blog post and my 12th WordPress error post. So… I’ll tag this one as WordPress and… I think just WordPress.
This error is clasified as 500 Internal Server Error. This simply means that the server is the main cause that’s why this error occurred. If you’re familiar with the Fatal error Allowed memory size of [RANDOM NUMBERS HERE] bytes exhausted (tried to allocate [ANOTHER RANDOM NUMBERS HERE] bytes) in /home/user/public_html/wp-includes/wp-db.php on line 774, then you’ll have an idea that the main cause of this error is your server’s memory allocation to the specific user.
I have a blog that wasn’t update for a very long time. Its last post was March 25, 2009. I’m still using WordPress 2.7 in that blog. After attempting to upgrade it to WordPress 3.2, I encountered the error: Cannot redeclare pclziputilpathreduction().
Now I wonder why I cannot update it. I tried figuring it by disabling my current WordPress plugins one by one, until I disabled WPAU. WPAU is the WordPress Automatic Upgrade plugin which is completely useless in the newer version of WordPress. Why? Because the WordPress core itself has an automatic upgrade feature and you don’t need to use this plugin to upgrade your blog to the latest WP version.
That’s right guys. I just tried and tested it. The latest version of the Fluency Plugin which is version 2.4 looks like a disaster in WordPress 3.2. You can activate it, but you don’t want to use it. The drop down menus doesn’t drop down, because it’s already dropped.
Technically, it doesn’t really drop down, but drop right. As you can see in the picture above. Let’s just hope that Dean Robinson will update Fluency 2.4 to 2.5 and make it compatible with WordPress 3.2. I hope he will not re-design it as I love the current design, and I bet a lot loves it too.