Tim Smith

It is the deactivation message referenced in the OP. Rather than only appearing on an actual deactivation, it also appears on a successful update.

Thanks.

It’s a bit annoying to have an update leave it lying around though. Any chance of tweaking the plugin so it only does it on an actual deactivation instead of an update?

That missing method was introduced in PHPCompatibility release 9.2.0 (which is where all of the Sniffs are from), but the parent Sniff class (and the rest of the vendor code outside of the Sniffs) is from release 8.2.0

See https://github.com/PHPCompatibility/PHPCompatibility/releases

Reopening after holiday.

The normal wp-login.php page is not being cached (it’s excluded by the default setting Never cache the following pages: wp-.*\.php).

The request a new password page (on my-account/lost-password) says
“Page Caching using disk: enhanced (DONOTCACHEPAGE constant is defined)”
but also has
“Cache key: https://www.sofi-designs.co.uk/my-account/lost-password/_index_ssl.html”,

and the wp-login.php with the reset password action is being says:
“Page Caching using disk: enhanced (Requested URI contains query)” but very little else now the link has expired.

Note that the setting “Cache URIs with query string variables” is off.

If you need any more information please ask.

We had the same issue. “Event list plugin upgrade in progress… Please be patience(sic) until this process is finished.”

Disabling and re-enabling the plugin a few times eventually sorted it out.

upgrade.log.584 has
[2018-05-16 10:12:07] Updated option "el_last_upgr_version" to value "0.8.2"

upgrade.log (and all the others with earlier timestamps) has
[2018-05-16 10:22:58] Update of option "el_last_upgr_version" is not required: correct value "0.8.2" already set

Something is wrong with the check for completion as we also got repeated error_log lines starting:

[16-May-2018 10:12:07 UTC] EL_UPGRADE: Maximum script execution time: 120 seconds
[16-May-2018 10:12:07 UTC] EL_UPGRADE: Option "el_upgr_in_progress" added with value "1526465527"
[16-May-2018 10:12:07 UTC] EL_UPGRADE: Start upgrade check
[16-May-2018 10:12:07 UTC] EL_UPGRADE: Updated option "el_last_upgr_version" to value "0.8.2"
[16-May-2018 10:12:07 UTC] EL_UPGRADE: Deleted option "el_upgr_in_progress"
[16-May-2018 10:12:08 UTC] EL_UPGRADE: Maximum script execution time: 120 seconds
[16-May-2018 10:12:08 UTC] EL_UPGRADE: Option "el_upgr_in_progress" added with value "1526465528"
[16-May-2018 10:12:08 UTC] EL_UPGRADE: Start upgrade check
[16-May-2018 10:12:08 UTC] EL_UPGRADE: Update of option "el_last_upgr_version" is not required: correct value "0.8.2" already set
[16-May-2018 10:12:08 UTC] EL_UPGRADE: Deleted option "el_upgr_in_progress"
[16-May-2018 10:12:08 UTC] EL_UPGRADE: Maximum script execution time: 120 seconds
[16-May-2018 10:12:08 UTC] EL_UPGRADE: Option "el_upgr_in_progress" added with value "1526465528"
[16-May-2018 10:12:08 UTC] EL_UPGRADE: Start upgrade check
[16-May-2018 10:12:08 UTC] EL_UPGRADE: Update of option "el_last_upgr_version" is not required: correct value "0.8.2" already set
[16-May-2018 10:12:08 UTC] EL_UPGRADE: Deleted option "el_upgr_in_progress"
[16-May-2018 10:12:09 UTC] EL_UPGRADE: Maximum script execution time: 120 seconds
[16-May-2018 10:12:09 UTC] EL_UPGRADE: Option "el_upgr_in_progress" added with value "1526465529"
[16-May-2018 10:12:09 UTC] EL_UPGRADE: Start upgrade check
[16-May-2018 10:12:09 UTC] EL_UPGRADE: Update of option "el_last_upgr_version" is not required: correct value "0.8.2" already set
[16-May-2018 10:12:09 UTC] EL_UPGRADE: Deleted option "el_upgr_in_progress"
[16-May-2018 10:12:10 UTC] EL_UPGRADE: Maximum script execution time: 120 seconds
[16-May-2018 10:12:10 UTC] EL_UPGRADE: Option "el_upgr_in_progress" added with value "1526465530"
[16-May-2018 10:12:10 UTC] EL_UPGRADE: Start upgrade check
[16-May-2018 10:12:10 UTC] EL_UPGRADE: Update of option "el_last_upgr_version" is not required: correct value "0.8.2" already set
[16-May-2018 10:12:10 UTC] EL_UPGRADE: Deleted option "el_upgr_in_progress"
[16-May-2018 10:12:10 UTC] EL_UPGRADE: Maximum script execution time: 120 seconds
[16-May-2018 10:12:10 UTC] EL_UPGRADE: Option "el_upgr_in_progress" added with value "1526465530"
[16-May-2018 10:12:10 UTC] EL_UPGRADE: Start upgrade check
[16-May-2018 10:12:10 UTC] EL_UPGRADE: Update of option "el_last_upgr_version" is not required: correct value "0.8.2" already set
[16-May-2018 10:12:10 UTC] EL_UPGRADE: Deleted option "el_upgr_in_progress"

The repeated section continues a lot.

I wasn’t clear – I was actually referring to checking for PHP 7.0 compatibility where all reports are false positives, there is/was nothing to fix.

If you’re refering to W3TC use of deprecated functions in PHP 7.1 and removed functions in PHP 7.2, then that’s good news.

Is the community maintained fork of W3TC taking over from the Frederick Townes W3TC and is it going to be avaialable through the WordPress plugin repository?

Hi @lamdayap – as it says in the title PHP version 5.3.28

I was aware of some earlier issues which is why I upgraded to 5.6, but hadn’t seen this specific issue mentioned (is there a trac for Automatic plugins?). Upgrading also may not be an option for everyone.

• This reply was modified 7 years, 3 months ago by Tim Smith.

Just to clarify only the front end of the site was effected, the admin still loaded normally.

The plugin will try to use cURL to connect.

You could try turning on import debug and/or inserting some temporary code that reports the actual cURL error.

Also:

• doesn’t remember some settings (e.g. can’t disable autoplay)
• doesn’t respect some shortcode attributes (e.g. click=none)

The fault is actually that contrary to the plugin description it now needs PHP 5.4 to work.

The code is using the new short form array syntaxt that is only supported in PHP >= 5.4

Same problem

Thanks for the informative help. It’s all working fine today.

This happens if you do not have medium sized images (0x0) or if they are themselves very large.

At present all you can do is have medium sized images at the default size (300×300). You should be able to set this in the options unless your theme is stopping you, but you will need to use a regenrate images plugin to create the size you need.

If you need an image at your current medium dimensions then you’ll have to modify your theme or plugin to create one using add_image_size and change usage of ‘medium’ to whatever name you chose.

Sorry forgot the code tags

/* Remove Yoasts publish box which is output even when post is not public
* Hook this to current_screen, the first time $typenow is set up and before the publish box action
* Custom Type is not available on admin_init so his filter is no help
* Ridiculous hard graft to remove it as can't get at the WPSEO_metabox instance either, so scan the wp filter store to track it down
*/
public static function creative_infusion_remove_yoast_seo(){
    global $typenow, $wp_filter;
    if ($typenow=='yourcustomposttype' && isset($wp_filter['post_submitbox_misc_actions']['10'])) {
        $filters=$wp_filter['post_submitbox_misc_actions']['10'];
        foreach ($filters as $idx=>$data) {
            $function=$data['function'][0];
            if ( is_object($function) && is_a($function, 'WPSEO_Metabox') ) {
                remove_action( 'post_submitbox_misc_actions', array( $function, 'publish_box' ) );
            }
        }
    }
}
add_action('current_screen', 'creative_infusion_remove_yoast_seo');