user65
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Publishing or managing posts time outSome more info —
I always receive this error:
Connection lost. Saving has been disabled until you’re reconnected. We’re backing up this post in your browser, just in case.If I save a Draft, it works fine. If I move the draft to trash, it works fine. But, if it’s published or attempts to be published, it hangs up and errors out. I’ve tried increasing the autosave interval but nothing happens.
Again, all plugins have been disabled and reverted back to 2013 and still receive this issue. All operations within the dashboard and front end of the site perform very quickly, but anything relating to publishing doesn’t work properly.
Forum: Fixing WordPress
In reply to: debug error – custom_backgroundUpgrading Twenty Eleven resolved the error.
Thanks – I posted here since I was receiving the error on both themes. I will contact their support regarding their theme.
I second this request, in fact I was just going to post this exact request.
Thanks so much for the plugin, it’s responsible for at least 50% of our website right now.
Any way you can set an option to “hide or display” title?
As you can see, it can easily get confusing!
Forum: Fixing WordPress
In reply to: RSS Feed and Multiple Page PostsI don’t mean to bump my post, but is this simply not possible?
Forum: Plugins
In reply to: [Video Thumbnails] Video Thumbnails and Blip.tvWorked like a charm!
Thanks so much, Sutherland.
— Edit
Ahhh, now my page loads SOO MUCH FASTER – Thanks again!!!!
Forum: Fixing WordPress
In reply to: database maxing cpu usage after upgrade to 3.1i have role manager and kept it enabled.
i found the best way to solve my problem was to examine what plugins affected the post edit screen. So basically enable all screen options and check out which plugins affect the post. I started with that method and found the seo plugin. it has to be a plugin that being activated or used through the post edit page.
Forum: Fixing WordPress
In reply to: database maxing cpu usage after upgrade to 3.1I had google sitemaps enabled, tried disabling it without any positive effect. For me it was platinum seo.
Forum: Fixing WordPress
In reply to: database maxing cpu usage after upgrade to 3.1i removed platinum seo plugin and that seemed to do the trick.
Can I move the cache directory elsewhere within the plugin to get the folder to sync up automatically?
It is Viva Thumb-Zoom. wp-content/uploads/cache
Also, User Photo for the wp-content/uploads/userphoto directory.
Also, Nextgen gallery for the wp-content/gallery
Can you add a code to allow us to select other directories to scan in the auto sync?
Thanks Backie,
Don’t have the smushit enabled. Is there a way to set the “wp-content/uploads/cache” directory to auto sync? I have to manually sync every time a new article is published in my slider.Forum: Fixing WordPress
In reply to: MYSQL-Slow Queries WordPress 3.1I am having the EXACT same issue! Come one wordpress, fix the REAL issues.
This problem has to do with the post date, something happened and is causing the tmp table to max out when it shouldn’t have to.
not sure if the trac file helped, but I found that my editors can work with posts in the dashboard if I turn on Maintenance Mode. It’s a plugin that puts a splash on the front end.
my post with the exact same issue:
http://wordpress.org/support/topic/database-maxing-cpu-usage-after-upgrade-to-31Forum: Fixing WordPress
In reply to: database maxing cpu usage after upgrade to 3.1Here is what my host is recommending:
For example, the following queries are being executed rather frequently and even using indexes are scanning over 25,561 rows and only returning 10 back to the client.
# User@Host: pnnsql[pnnsql] @ localhost []
# Query_time: 12 Lock_time: 0 Rows_sent: 10 Rows_examined: 25561
SELECT SQL_CALC_FOUND_ROWS wp_posts.* FROM wp_posts INNER JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id) WHERE 1=1 AND ( wp_term_relationships.term_taxonomy_id IN (953) ) AND wp_posts.post_type = ‘post’ AND (wp_posts.post_status = ‘publish’) GROUP BY wp_posts.ID ORDER BY wp_posts.post_date DESC LIMIT 0, 10;mysql> explain SELECT SQL_CALC_FOUND_ROWS wp_posts.* FROM wp_posts INNER JOIN wp_term_relationships ON (wp_posts.ID = wp_term_relationships.object_id) WHERE 1=1 AND ( wp_term_relationships.term_taxonomy_id IN (953) ) AND wp_posts.post_type = ‘post’ AND (wp_posts.post_status = ‘publish’) GROUP BY wp_posts.ID ORDER BY wp_posts.post_date DESC LIMIT 0, 10 \G
*************************** 1. row ***************************
id: 1
select_type: SIMPLE
table: wp_posts
type: index
possible_keys: PRIMARY,type_status_date
key: PRIMARY
key_len: 8
ref: NULL
rows: 27077
Extra: Using where; Using temporary; Using filesort
*************************** 2. row ***************************
id: 1
select_type: SIMPLE
table: wp_term_relationships
type: eq_ref
possible_keys: PRIMARY,term_taxonomy_id
key: PRIMARY
key_len: 16
ref: dbname.wp_posts.ID,const
rows: 1
Extra: Using index
2 rows in set (0.00 sec)You may benefit from adding a separate entry for the wp_posts.post_date field. This is being referenced in the type_status_date index, but not in the leftmost order from where it can be properly utilised.
Basically any time I schedule or mess with the timestamp of a post and save, the whole site goes down sending mysql into a spin/cpu peak.
My best option to downgrade?
Forum: Fixing WordPress
In reply to: database maxing cpu usage after upgrade to 3.1I am also getting this error consistently in the mysql logs:
/usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_6e35_43.MYI’; try to repair it
Basically the host is telling me that the tmp table is filling up from the wp_post query.
anyone else having these issues?
here is my list of errors from mysqld:
110324 14:25:59 [ERROR] /usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_3713_32.MYI’; try to repair it
110324 14:25:59 [ERROR] /usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_3713_82.MYI’; try to repair it
110324 14:26:20 [ERROR] /usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_3713_67.MYI’; try to repair it
110324 14:26:20 [ERROR] /usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_3713_68.MYI’; try to repair it
110324 14:26:20 [ERROR] /usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_3713_71.MYI’; try to repair it
110324 14:26:20 [ERROR] /usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_3713_35.MYI’; try to repair it
110324 14:26:20 [ERROR] /usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_3713_13.MYI’; try to repair it
110324 14:26:20 [ERROR] /usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_3713_15.MYI’; try to repair it
110324 14:26:20 [ERROR] /usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_3713_49.MYI’; try to repair it
110324 14:26:20 [ERROR] /usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_3713_86.MYI’; try to repair it
110324 14:26:20 [ERROR] /usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_3713_39.MYI’; try to repair it
110324 14:26:20 [ERROR] /usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_3713_33.MYI’; try to repair it
110324 14:26:20 [ERROR] /usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_3713_5.MYI’; try to repair it
110324 14:26:20 [ERROR] /usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_3713_0.MYI’; try to repair it
110324 14:26:41 [ERROR] /usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_3713_36.MYI’; try to repair it
110324 14:26:41 [ERROR] /usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_3713_54.MYI’; try to repair it
110324 14:26:41 [ERROR] /usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_3713_72.MYI’; try to repair it
110324 14:26:41 [ERROR] /usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_3713_46.MYI’; try to repair it
110324 14:26:41 [ERROR] /usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_3713_24.MYI’; try to repair it
110324 14:26:41 [ERROR] /usr/libexec/mysqld: Incorrect key file for table ‘/tmp/#sql_3713_63.MYI’; try to repair itForum: Fixing WordPress
In reply to: Category Archives Broken (3.1 issue?)Deactivating all plugins did the trick.
Thank you.