Tag Archives: wordpress

Plugin could not be activated because it triggered a fatal error. — WordPress

WordPress plugin installation error message

When installing or upgrading a plugin in WordPress, you may get a message like this: Plugin could not be activated because it triggered a fatal error. The specifics may look something like this Fatal error: Access level to WPsite_Firebar_List_Table::get_table_classes() must be public (as in class WP_List_Table) in /xyz/wp-content/plugins/codecanyon-9861906-firebar-notification-bars-for-wordpress/admin/model/list-table.php on line 460 The error is likely due to an outdated version of WordPress. Upgrade to the latest version and your issue will hopefully be resolved

Downloading and extracting WordPress via command line

Wordpress extract, Putty

# wget http://wordpress.org/latest.tar.gz –2015-05-04 10:44:46– http://wordpress.org/latest.tar.gz Resolving wordpress.org…, Connecting to wordpress.org||:80… connected. HTTP request sent, awaiting response… 301 Moved Permanently Location: https://wordpress.org/latest.tar.gz [following] –2015-05-04 10:44:46– https://wordpress.org/latest.tar.gz Connecting to wordpress.org||:443… connected. HTTP request sent, awaiting response… 200 OK Length: 6321767 (6.0M) [application/octet-stream] Saving to: âlatest.tar.gzâ 100%[==========================================================>] 6,321,767 6.63MB/s in 0.9s 2015-05-04 10:44:47 (6.63 MB/s) – âlatest.tar.gzâ saved [6321767/6321767] # tar xfz latest.tar.gz

Regenerate thumbnails error on WordPress [SOLVED]


Recently I switched to a new WordPress theme and subsequently encountered some image thumbnail issues. Here is the specific error I received when regenerating thumbnails: function (){if(l){var t=l.length;(function i(t){x.each(t,function(t,n){var r=x.type(n);”function”===r?e.unique&&p.has(n)||l.push(n):n&&n.length&&”string”!==r&&i(n)})})(arguments),n?o=l.length:r&&(s=t,c(r))}return this} This was particularly frustrating, because if a custom size is not available then WordPress will use the FULL size image even for thumbnails. This of course results in slow page times and wasted bandwidth The solution Thankfully, after a little checking it appeared to be a simple permissions issue.

The best custom taxonomy plugin for WordPress? [SOLVED]


I checked out a bunch of custom taxonomy plugins for WordPress. When it was all said and done my favorite plugin was: Custom Fields and Custom Post Types Management http://wordpress.org/plugins/types/The complete and reliable plugin for managing custom post types, custom taxonomy and custom fields. While it is a little hefty at ~6.8MB after uploading, it does the trick and is fully compatible with the latest WordPress version. Woot!

[Err] 2006 – MySQL server has gone away Navicat/WordPress [solved]

Screenshot showing the wait_timeout variable in Navicat Server Monitor

Recently I tried upgrading to the latest version of the WordPress Download Monitor plugin. It did not go well Thus, I tried to revert from a backup made using Navicat. Unfortunately, the restore would fail every time while trying to import my wp_posts table (a pretty important table!) I tried exporting the backup to a SQL dump and importing that. No luck. Finally, I tried resolving the actual ‘MySQL server has gone away’ issue itself and I had success. This tip is

WordPress comment pagination and 301 redirects

I recently enabled paginated comments on my WordPress blog. Later I decided to disable pagination and just go for the regular ol’ a single comments listing on each post (regardless of how many comments there are). After the chance I was a bit worried about duplicate content, but thankfully when I unchecked the ‘break comments into pages with…’ option from wp-admin -> settings -> discussion WordPress automatically took care of redirecting! Here is the example: http://www.jdhodges.com/blog/dreamweaver-document-too-large-copy-past/comment-page-2/ auto redirects to http://www.jdhodges.com/blog/dreamweaver-document-too-large-copy-past/

Permalink Updates on WordPress

For a very long time this post’s permalink URL would have been: http://www.jdhodges.com/2013/07/permalink-updating-wordpress/ But now it is: http://www.jdhodges.com/blog/permalink-updating-wordpress/ I made this adjustment primarily because an old URL like this one: http://www.jdhodges.com/2012/05/exede-wildblue-satellite-internet-review/ Even if the actual content was updated the URL made it look like it was only updated in 2012. The new permalink structure is shorter and more relevant, so far I love it! However, one should exercise caution when doing this type of update as it can wreak havoc

Page 1 of 41234