ssiruguri

No, we don’t have a caching plugin. Other changes I make to the text layer settings get applied immediately – for example, the dimensions or positioning.

I will use that form. Thanks.

Also, if you are running Nginx, you have to allow nginx to accept larger POST sizes. The default appears to be less than 27MB, at any rate.

See https://stackoverflow.com/questions/2056124/nginx-client-max-body-size-has-no-effect

The solution is to add client_max_body_size 30m; or something similar to a server directive in your conf files.

In my case, I had to remember to restart PHP-fpm as well – as below, for example, if you have Ubuntu 16:

sudo service php7.0-fpm restart

I have PHP 7 – with PHP 5, your fpm service is probably php5-fpm

Yes, it was – in my wp-config.php file, I needed to remove the legacy HMBKP_* variables.

We did update both plugins – EM and Full Calendar, but are not seeing our calendar page display at all.

Adding a new page with the full calendar shortcode did not generate the calendar either.

Any diagnoses we can provide that will help?

We have dev downloads enabled and downloaded 5.6.3.1… we were seeing problems with recurring events and old events (>1 month) not showing up. Now the calendar page is not rendered at all!

The events are still in the db.

Any thoughts?

For what its worth, this worked for me – I’m using WP 4.0.1 and Backwpup 3.1.2

Okay, the fix is pretty simple – those lines need a more graceful check, something like:

if ( isset($options['debug_mode']) && $options['debug_mode'] == 1 ) {

I’d confirm George’s guess that you have to update a post for the number of revisions to be updated. L119 (WP3.7.1) onwards in the function wp_save_post_revisions in wp-includes/revisions.php says

$revisions_to_keep = wp_revisions_to_keep( $post );

if ( $revisions_to_keep < 0 )
return $return;

That’s where the config variable is checked. Plugin filters are applied after the variable is checked, so plugins will override that value.

It appears that since WP 3.6, you can set the value of WP_POST_REVISIONS in wp-config.php to be the number of revisions you want to keep per post. I don’t know enough WP to confirm this but I think it applies to “posts” as well as “pages,” in the user sense, because both are “posts” in the platform code sense.

So for the most basic uses, you might not need this plugin any more.

I ran into this problem just now, and the .maintenance file is in the home folder of the WP install. My Jetpack update in fact did not complete, and this file never got deleted, so I manually moved it out of the folder. My site now works correctly, and also has the latest Jetpack.