Auto-updates enabled

Hi there,

The auto-updates depend on the WordPress auto-updates process. It might take a while before it proceeds when cron is triggered.

Docket cache auto-updates option purposely to run action before and after the updates process is triggered. We don’t control when it will happen.

Thanks.

Thanks for your response. What is strange is that auto-updates usually indicate when they will happen, usually next day, once an update appears. Your plugin does not seem to do that.

Hi,

I’m not sure why it did not work on your site. Since it works as expected. Please try to disable and enable it back and checks if this option 'DOCKET_CACHE_AUTOUPDATE' => 'enable' exists in wp-content/docket-cache-data/options.php

Docket Cache use the “auto_update_plugin” filter to inform WordPress whether auto-updates for Docket Cache should enable or disable. If from the plugins page Docket Cache “Automatic Updates” is displayed as “Auto-updates enabled” it should work, if not, seems nothing Docket Cache can do.

Thanks.

I found my problem. Although the plugin states Auto Updates Enabled on the plugin page, when I manually update the plugin, a link appears under the Auto Updates Enabled saying Configure auto updates. Clicking on that takes me to the configuration tab of the plugin. Scrolling down to Plugin Options, I find Docket Cache Auto-Updates disabled. So although the plugin tells WordPress it is set for auto-updates, it actually isn’t until that configuration is made in the plugin options. A bit confusing to be sure.

Hi,

Before the latest update, auto-updates are enabled by default. No need to configure it on the configuration page unless want to disable it. Because of that, no option has been written into wp-content/docket-cache-data/options.php.

In the latest version, this has been changed. We disable auto-updates by default and require a user to configure it if want to enable it. Also, we put a configuration link on the plugins page.

If the auto-updates have been enabled on the configuration page, I think it should work for the next updates.

I’m taking note of the “Auto Updates Enabled” issue on the plugins page, will try to replicate and fix the issue on the next release.

Thanks.

Here’s a screen shot of the plugins page on one of my sites.

https://northumberlandstudiotour.ca/wp-content/uploads/Auto-updates-enabled-scaled.jpeg

From that screenshot, it should be updated by WordPress. If you really want to confirm it, please edit the wp-content/plugins/docket-cache/includes/src/Plugin.php file at line 249 and remove this code:

add_filter(
            'auto_update_plugin',
            function ($update, $item) {
                if ('docket-cache' === $item->slug) {
                    return $this->cf()->is_dctrue('AUTOUPDATE');
                }

                return $update;
            },
            \PHP_INT_MAX,
            2
	);

And then enable back auto-updates at plugins page. Or manually define this constant in wp-config.php

define('DOCKET_CACHE_AUTOUPDATE', true);

Thanks.

• This reply was modified 1 year, 11 months ago by Nawawi Jamili.

Hi,

I think I’ve figured out why it’s confusing. When Docket Cache is disabled, the “Automatic Updates” plugin page will display Enable/Disable auto-updates. Since Docket Cache is not enabled, it has no effect on the Docket Cache Auto-updates option on the Configuration page or the “DOCKET_CACHE_AUTOUPDATE” constant.

For the next release “DOCKET_CACHE_AUTOUPDATE” constant will only be used to force automatic updates if defined.

Thanks.

Thanks for continuing to address this issue. Auto Update for this plugin is different from all other plugins I’ve encountered. Guess which one of these is Docket Cache?

https://northumberlandstudiotour.ca/wp-content/uploads/Auto-Update-Enabled.jpeg

My only problem now is that I’ve installed the plugin on nearly 100 websites and I don’t know which ones need to be updated to auto update. I will eventually get to them all as I visit them, but it will take some time.

Please try this next release version below. And see if it solved the issue.

https://docketcache.com/devtest/docket-cache-220703-rc5.zip

Thanks,

The latest version seems to have fixed it. Thank You.