Brendan
Forum Replies Created
-
Forum: Plugins
In reply to: [Maintenance Switch] Remove 503 error code or add option to not use itThanks for the response! I’ll check out the update.
I re-read my post and I apologize for the harsh tone. I understand what you’re saying about SEO- that would definitely be important for sites that are already established (such as showing this page during a WP update, the 503 is appropriate). For sites that are not yet launched, however, I think the 503 is a mixed bag – there would be no SEO value lost by not returning a 503, but you are unable to verify certain external services such as SparkPost because their TOS requires a “working” website.
Yes ds123, I just looked through inc/admin/common.php and it appears that these changes have been integrated into the plugin.
Cheers!
Ok, so the problem is actually if you don’t define the capabilities array in register_taxonomy. This should be more clear in your plugin details because most people don’t define taxonomies with the capabilities array.
Even more confusing is that as an admin you can manage/edit/delete the taxonomy terms, but with your plugin, it says you can’t edit them.
To make sure you don’t run into this error, at a minimum add this to your register_taxonomy call:
capabilities => array('edit_terms')Forum: Fixing WordPress
In reply to: No update required after update to 3.3Ipstenu, the problem is you can’t flush the W3TC cache because you can’t get into the admin panel at all.
You literally have to stop W3TC from running to get your admin panel back. (or manually upgrade db like i did)
Forum: Fixing WordPress
In reply to: No update required after update to 3.3Hi,
This happened to me just now. The script hung because the database upgrade took a while and didn’t complete it’s post database upgrade functions.
Go into your database (using PHPMyAdmin or other database tool) and go to your wp_options table (or $prefix_options) and find the row with option_name of “db_version”. The option_value of this row should be 19740 (wp 3.3). Change this value to the corresponding value in the following list:
3.3.1 = 19470
3.2.1 = 18226
3.2 = 18226
3.1.4 = 17516
3.1.3 = 17516
3.1.2 = 17516
3.1.1 = 17516
3.1 = 17056
3.0.5 = 15477
3.0.4 = 15477
3.0.3 = 15477
3.0.2 = 15477
3.0.1 = 15477
3.0 = 15260More available here: http://codex.ww.wp.xz.cn/FAQ_Installation under the “Force Database Upgrade” section.
Then run /wp-admin/upgrade.php and it should ask you to upgrade.
This worked for me, hopefully this helps you too.