Pieter Daalder

Hi there Sam!

What version of our plugin are you using? Does this occur with the latest version as well? And: where is this error produced? How can we reproduce this behaviour?

Hi Sam,

Yes it will skip any steps that are not needed.

Kind regards,

Pieter
Servebolt

Hello! Sorry about the delayed response.

We need to separate your question into two parts – first the question regarding the menu cache-feature:

You can verify that the feature is working by inspecting the source code of a page where a menu is present. But first we need to add some code to your site for the purposes of debugging:
add_filter('sb_optimizer_menu_optimizer_print_cached_comment', '__return_true');

Usually you would typically add this to your functions.php-file in your theme, or perhaps a PHP-file in the “wp-content/mu-plugins”-folder.

This code will result in a comment in the source code telling you whether the menu was retrieved from the cache or not. The comment is formed like this:
<!-- This menu is cached by Servebolt Optimizer -->.

Regarding where is the cache stored – the cache is stored in WordPress transients which in turn is stored in the “wp_options”-table. The transient key will start with the string “sb-menu-cache-“. You would need to inspect your database-tables to see the cached data.

Note that we have a v3.4 release coming up (no formal release date yet) that will improve the menu cache feature, and increase the compatibility for various themes and plugins. So if you are seeing issues with the menu cache feature then you might possibly want to wait for the v3.4-release and test again then.

Regarding the translation loading cache feature – there is currently no way to confirm that the feature is working (other than debugging the code manually). The translation cache is also stored in WP transients. The transient key is a md5 hash of the path to the MO-file. Unfortunately no prefix so these rows are hard to spot in the “wp_options”-tables.

Hi there Rookie!

There have been some changes in the plugin lately. What version are you currently running on your site?

Hi there Sam!

Thank you for contacting us. If you’re worried about database performance during these kind of changes, it’s best to try it out on a staging environment first. It’s hard to tell wether it should work in your case, since we have no insight in the platform/stack you’re currently using.
If you have the option to run this through WP-CLI, that would indeed be the best way of doing this.

Let me know if there is anything else we can help you with!

Terribly sorry about that.

The good news: the Servebolt are about to launch an update to this plugin. This issue is one of the things that get addressed. It should land shortly, but if you need to get rid of the plugin in the mean time you’d have to manually delete it through SFTP.

Thanks for your update! I’ll look into this further!

Hi there Gulshan! Thank you for your feedback! Just quickly recapping your points:

1. That’s a very good thing to consider! We’ve added it to the new features we’re currently working on. You can expect it to be included in one of the upcoming releases.
2. Normally page caching shouldn’t be an issue. Would you mind sharing the domain it’s about? If you want, you can send it through a private message instead. I can look a little more in to your specific situation in that way.
3. Regarding three and four: I need to dive in to this for you. It’s not the behaviour I’d expect. I’ll get back to you on this.

Hi Peter!

Normally this behaviour shouldn’t occur. What settings are you using on our plugin? And could you check if the problem persists when you disable all other plugins?

Sure, no problem! Thanks for the quick fix ??

Actually, instead of using mod_access_compat it would be better to use the following .htaccess code, which should work on all servers:

<Files web.config>
	# Apache 2.2
	<IfModule !mod_authz_core.c>
		Order Deny,Allow
		Deny from all
	</IfModule>

	# Apache 2.4
	<IfModule mod_authz_core.c>
		Require all denied
	</IfModule>
</Files>

Are you using any kind of caching solution? If so: does clearing your cache fix this issue?

Awesome, thanks!

Where are you trying to enter this CSS code?

If you’re not actively using Duplicator, I’d recommend removing it and also removing all files created by it. If you need it in a later stage, you can always reinstall the plugin.