Plugin can work with Autoptimize + Cache Enabler?

Hi there,

Technically it should work. Docket Cache is an object caching plugin. It will not interfere with page caching plugins like Cache Enabler or web assets optimization plugins like Autoptimize.

You can try it first to see if it work with your hosting environment.

Thanks.

Yes, please try to install and see if it works.

Hi, thank you for your compliment and happy new year.

the plugin not adjust himself to the excet configuration have in the WP-CONFIG
and the PHP.

By design, PHP constant can’t be overwritten and Docket Cache only can adjust any constant that is not already defined in wp-config.php. You need to manually remove previously defined constants.

My cPanel PHP LIMIT is 512 THE PLUGIN READ ONLY 256.

Docket cache shows “PHP Memory Limit” at Overview page like this,

PHP Memory Limit:

The data is manually retrieved from PHP configuration by using the command ini_get(‘memory_limit’)

WP Frontend Memory Limit:

We read it from WP_MEMORY_LIMIT, it is WordPress constant and you need manually adjust this setting.

WP Backend Memory Limit:

We read it from WP_MAX_MEMORY_LIMIT, it is WordPress constant and you need manually adjust this setting.

have a way to adjust the plugin to the current WP-CONFIG? for example:

in the wp-config i did 7 days trash, your plugin did 30 days.
things like that.

Currently, we don’t have a plan to adjust entirely what is in the wp-config.php file. Since it will cause a lot of issues if something goes wrong. We only put small code at the bottom wp-config.php before WordPress loads the wp-settings.php file. We called it runtime code.

Any constant defined before we load our code will be honoured. If your set 7 days trash, it will be 7 days trash. Our 30 days is no effect. The configuration page will show notice “constant already defined or exists in wp-config.php file. This update has no effects” if your try to set “Trash Bin”.

You need manually remove any constant that Docket Cache try to handle. This is a list of constants that we handle at Configuration RUNTIME OPTIONS.

Auto Save Interval:
AUTOSAVE_INTERVAL

Post Revisions:
WP_POST_REVISIONS

Trash Bin:
EMPTY_TRASH_DAYS

Cleanup Image Edits:
IMAGE_EDIT_OVERWRITE

Disallows WP Auto Update Core:
WP_AUTO_UPDATE_CORE

Disallows Plugin / Theme Editor:
DISALLOW_FILE_EDIT

Disallows Plugin / Theme Update and Installation:
DISALLOW_FILE_MODS

WP Debug:
WP_DEBUG
WP_DEBUG_DISPLAY
WP_DEBUG_LOG

Hope this will answer your question.

Thanks.

Hi,

I’m taking note of your suggestion. You can try other plugins if Docket Cache is not suitable for your usage.

Thanks again for your compliment. I’m marking this thread as resolved. Feel free to open a new topic if you have further questions.

Thanks.

Hi @123nadav,

I’m sorry if my words mislead you from what I’m trying to say. I want you to know that I’m not offended. Docket Cache is an open-source project, and it is Okay if people want to use it or not. I simply suggest you try other plugins that are specifically made to handle wp-config.php. You may use it along with Docket Cache.

Docket Cache runtime code it’s only a small part of this plugin. And only to manipulate WP constant as said earlier. It only activates if you click install/update runtime code on the configuration page. It’s tested on a hosting server with cPanel.

The only lack of is, it can’t change the constant if already have before. This is because the PHP constant only can be set once. The only solution is Docket Cache need to remove any constant set earlier in wp-config.php. This is we don’t have a plan at this moment. The reason is if when we try to update the wp-config.php file and the server is in heavy traffic, chances wp-config.php not fully written can be. This will cause server error 503. And users need manually restore the wp-config.php file.

This is not because we can, or can’t do. It is because this is the right solution at this time.

I hope this will answer your question. Thanks again for your compliment.

Thanks.