James

Thanks Kevin, sorry for disappearing.

I tested it 2.2.1-rc with Classic Editor and Gutenberg. Bad news is Move to Trash still doesn’t delete a scheduled revision. Or it does and immediately creates a new revision or something.

Yes, the dev version fixes the problem. Thanks!

Sort of sounds like https://core.trac.www.ads-software.com/ticket/39132

Yes, I experienced this too.

IE 8 reports a syntax error in smooth-scroll-up/js/jquery.scrollUp.min.js on the word class:

l("<a/>",{id:p.scrollName,class:p.scrollClass,href:"#top"})

It’s bogus error, but quoting it works everywhere:

l("<a/>",{id:p.scrollName,"class":p.scrollClass,href:"#top"})

I don’t see this in the upstream jquery.scrollUp.min.js.

I haven’t tried it yet, but my plan is to uninstall APC and install ZendOptimizerPlus and APCu instead.

Kinda/sort of. I replaced the $result = apc_store( $key, $store_data, $expire ); line with the block of code above. The apc_delete call in the snippit clears the stale data, so WP will do a fresh query next request.

But upgrading and tuning APC is important.

slam_defense must be disabled since WP updates the same keys often. But in APC 3.1.3pl1 slam_defense cannot be disabled (check the source code, the ini setting is never used).

APC 3.1.7 introduces read-write locks. Because how can shared memory work with out locks?

APCu gives user data it’s own memory pool. If I understand correctly, with APC before “u”, the whole cache can be filled of PHP byte code and then every apc_store will fail.

And APCu’s apc_store still fails if another process is doing an expunge. And we’re back at the workaround.

Thanks Nicola, I updated robots.txt.

I know it seems silly. I probably should also mention our MySQL is using InnoDB tables on spinning disks on an overloaded machine due for replacement. An update still packs some punch.

I’m also running 1.10.9-standard and started experiences slow to never finishing loads. MySQL had a bunch of UPDATEs to option_name=’ai1ec_scheduler_hooks’. Which traced back to this:

all-in-one-event-calendar/constants.php:

-		define( 'AI1EC_N_CRON_FREQ',        'daily' );
+		define( 'AI1EC_N_CRON_FREQ',        '1d' );

Every page view, Ai1ec_Scheduling_Utility::reschedule compares $existing[‘freq’] (“1d” from database) and $freq (“daily” from AI1EC_N_CRON_FREQ), then replaces “daily” with “1d” and updates the db (and some more work). Repeat forever.

Paging nicola.peluchetti