ucallrt

No, that is not the case. I’m now running the pro version and am getting the same exact error.

Yes, confirming that moving to version 2.5.2 fixes the problem.

I think that the quick edit issue should be opened in another thread. I’m going to mark this one as resolved.

Confirmed that regressing back to 2.4.7 solves the problem.

Here are some screenshots:

The images in question that I was trying to add were 11.1 and 12.3 MB in size.

I’m having this issue. All of the above suggestions have not worked. There is no ‘core_updater’ (or ‘core_update.lock for that matter) in my wp_options table and hitting the check again doesn’t work either. I’ve waited 24 hours and it hasn’t cleared.

Problem was the same before and after 4.5.

Adding more interest to things, seems to happen on Safari, but not on Chrome.

Saw the same thing on my site. Unfortunately, the plugin author does not read the WP forum, so I don’t know if he’ll do anything about it.

I’m getting query errors related to these processes. They’re not all like the following, but they seem to relate to w3_cdn.

[19-Apr-2011 17:58:17] WordPress database error MySQL server has gone away for query UPDATE wp_options SET option_value = ‘a:16:{i:1303233951;a:1:{s:25:\”w3_cdn_cron_queue_process\”;a:1:{s:32:\”40cd750bba9870f18aada2478b24840a\”;a:3:{s:8:\”schedule\”;s:25:\”w3_cdn_cron_queue_process\”;s:4:\”args\”;a:0:{}s:8:\”interval\”;i:900;}}}i:1303234575;a:2:{s:13:\”dsq_sync_post\”;a:1:{s:32:\”15a95e250b7a0be47b78f6aba74d8ab1\”;a:2:{s:8:\”schedule\”;b:0;s:4:\”args\”;a:1:{i:0;s:5:\”19238\”;}}}s:14:\”dsq_sync_forum\”;a:1:{s:32:\”40cd750bba9870f18aada2478b24840a\”;a:2:{s:8:\”schedule\”;b:0;s:4:\”args\”;a:0:{}}}}i:1303234744;a:1:{s:18:\”w3_cdn_cron_upload\”;a:1:{s:32:\”40cd750bba9870f18aada2478b24840a\”;a:3:{s:8:\”schedule\”;s:18:\”w3_cdn_cron_upload\”;s:4:\”args\”;a:0:{}s:8:\”interval\”;i:900;}}}i:1303236196;a:1:{s:22:\”w3_objectcache_cleanup\”;a:1:{s:32:\”40cd750bba9870f18aada2478b24840a\”;a:3:{s:8:\”schedule\”;s:22:\”w3_objectcache_cleanup\”;s:4:\”args\”;a:0:{}s:8:\”interval\”;i:3600;}}}i:1303236586;a:1:{s:18:\”w3_pgcache_cleanup\”;a:1:{s:32:\”40cd750bba9870f18aada2478b24840a\”;a:3:{s:8:\”schedule\”;s:18:\”w3_pgcache_cleanup\”;s:4:\”args\”;a:0:{}s:8:\”interval\”;i:7200;}}}i:1303236651;a:2:{s:18:\”w3_dbcache_cleanup\”;a:1:{s:32:\”40cd750bba9870f18aada2478b24840a\”;a:3:{s:8:\”schedule\”;s:18:\”w3_dbcache_cleanup\”;s:4:\”args\”;a:0:{}s:8:\”interval\”;i:3600;}}s:25:\”w3_cdn_cron_queue_process\”;a:1:{s:32:\”40cd750bba9870f18aada2478b24840a\”;a:3:{s:8:\”schedule\”;s:25:\”w3_cdn_cron_queue_process\”;s:4:\”args\”;a:0:{}s:8:\”interval\”;i:900;}}}i:1303237091;

etc, etc….

@Amuary This problem seemed to have corrected itself after you released the first fix, but today with v2.0-beta5, it’s broken again. Any ideas?

Ohmigosh. Thanks so much for that fix!

That did it. Thanks!

Oh. My bad. Thought I saw a press release that 2.7 was out.

That did it. Thanks.