Hi there,
Let’s say we use cloudflare enterprise and we update a post.
Will below option purge cache for only that specific post or will purge all Cloudflare Cache?

Automatic purge on update
1. On post/term content update
2. On post/term deletion
3. On slug/permalink change
4. On attachment update

Menu cache cashing problem with language switcher in WPML and polylang. Can you please take a look at it?

It only cache the home page and shows that to be the language version of all no matter page and settings in the multilingual plugin and where there is a connected translation.

When “menu optimizer” is active (disabled now, can re-enable briefly if you need to see this happening), the domain in the URL’s in my menu point to the servebolt-domain (e.g. https://blogfu-15715.reinhold-ams.servebolt.cloud/contact/) instead of the official domain (as configured in Settings -> General (which should result in e.g. https://blog.futtta.be/teletijdsmachine/), which causes CORS errors when AJAX requests are executed (contact form, koko analytics)?

Hello, I have noticed two errors in Query Monitor relating to your plugin. It seems to be trying to access files that are restricted on our server:

file_exists(): open_basedir restriction in effect. File(/www/xxx/environment.ini) is not within the allowed path(s):

and

file_exists(): open_basedir restriction in effect. File(/www/xxx/environment.json) is not within the allowed path(s):

Option to drop indexes:
Index in the wp_options table on the autoload column
Index in the wp_postmeta table on the meta_value column

Right now we can only create. Add a wp-cli or an ssh or sql script in the FAQ to drop them until a function within the plugin GUI is available.

Suggestions for more index tables. There is also possibility to add for different columns some suggested below.

Would also prefer to be able to select which one to create as users and usersmeta is not needed for sites with 2 users. Some other columns could be very helpful to boost performance for Woo while some is not needed if not a WooCommerce. Terms, relationships and taxonomy might not be useful if you don’t use etc.

But some core are missing, wp_posts, wp_posts with guid column, some plugins and themes are still querying with LIKE and have to scan the whole table to find.

This should be fairly quick to add maybe possible to add in a patch before the big update.

Maybe possible to hit or schedule optimize/analyse the different tables as well would be useful to regenerate all data?

wp_users
wp_terms
wp_posts
wp_posts => latest_posts
wp_posts => sitemaps
wp_posts => guid
wp_usermeta
wp_term_relationships
wp_term_taxonomy

Once detecting Redis perhaps run following to clean transients which should be loaded via redis.
delete from wp_options where autoload = 'yes' and option_name like '_transient%';

Could you add function to generate an index on wp_posts on the guid column. Some themes and plugins grab posts directly using SQL against wp_posts and just use the guid. Typically, this is when they’re grabbing images. They shouldn’t do it that way, but some do like oxygen builder.

• This topic was modified 3 years, 2 months ago by Rookie.
• This topic was modified 3 years, 2 months ago by Rookie.
• This topic was modified 3 years, 2 months ago by Rookie.

Remove the wp frontend admin bar as option. Additionally, not making it jquery dependent. As of right now, we defer the jquery lib and getting console error due to servebolt settings cache-purge-trigger.js

Easiest would be just add option to not display in frontend or top menu. Another option is also to not load the trigger js if cache settings is not enabled?

And last would be to stop using jquery overall vanilla js please.

How can we verify menu cache and load translations from cache is working as it should? Where is the cache stored?

I checked the transients but doesn’t seem to see any menu cache or text domain related transients.

Any chance the menu cache could speed up /wp-admin/nav-menus.php as well? This tends to be extremely slow once you work and scroll on a large single menu with several of sub menu items.

Hello, your plugin has some really interesting features especially adding the appropriate indexes to the post_meta table.

Our post_meta table is massive (11 million rows) so I am intrigued as to what to expect if I use your plugin to index such a massive table.

I have tried other plugins that claim to do this on our staging site and they just killed our DB. Probably because they time out and don’t finish etc.

Can you provide any guidance for users wanting to use this feature with massive sites like ours? I see the plugin supports WP CLI, would this be how the plugin runs such an expensive process on the DB?

Many thanks.

If I’m only using the Plugin to optimize the database is it necessary to keep the Plugin after the database conversion is complete?

When I try to delete a plugin, I get a message that the plugin could not be deleted due to a fatal error. This appears in the error log

Fatal error: require_once(): Failed opening required 'SERVEBOLT_PATHclasses/nginx-fpc/sb-nginx-fpc-auth-handling.php' (include_path='.:/usr/share/php') in /var/www/xxx/subdomains/www/wp-content/plugins/servebolt-optimizer/functions.php on line 959

Warning: require_once(SERVEBOLT_PATHclasses/nginx-fpc/sb-nginx-fpc-auth-handling.php): failed to open stream: No such file or directory in /var/www/xxx/subdomains/www/wp-content/plugins/servebolt-optimizer/functions.php on line 959

Warning: Use of undefined constant SERVEBOLT_PATH - assumed 'SERVEBOLT_PATH' (this will throw an Error in a future version of PHP) in /var/www/xxx/subdomains/www/wp-content/plugins/servebolt-optimizer/functions.php on line 959

I just tried this plugin …

1. Consider preventing autofilling with autocomplete="new-password"

<input name="servebolt_cf_api_token" type="password" id="api_token" data-original-value="" value="" class="regular-text validate-field validation-group-api_token validation-group-api_credentials invalid">

2. Page caching isn’t working. I have tried API key method.

cache-control: max-age=0,no-cache,s-maxage=0
cf-cache-status: EXPIRED
cf-edge-cache: no-cache, platform=wordpress

3. Error log
2021/01/20 05:59:38 [error] 93563#93563: *22045 FastCGI sent in stderr: "PHP message: PHP Warning: Use of undefined constant SERVEBOLT_PATH - assumed 'SERVEBOLT_PATH' (this will throw an Error in a future version of PHP) in /home/runcloud/webapps/cf_purge/wp-content/plugins/servebolt-optimizer/functions.php on line 959PHP message: PHP Warning: require_once(SERVEBOLT_PATHclasses/nginx-fpc/sb-nginx-fpc-auth-handling.php): failed to open stream: No such file or directory in /home/runcloud/webapps/cf_purge/wp-content/plugins/servebolt-optimizer/functions.php on line 959PHP message: PHP Fatal error: require_once(): Failed opening required 'SERVEBOLT_PATHclasses/nginx-fpc/sb-nginx-fpc-auth-handling.php' (include_path='.:') in /home/runcloud/webapps/cf_purge/wp-content/plugins/servebolt-optimizer/functions.php on line 959" while reading response header from upstream, client: 162.158.23.99, server: www.example.com, request: "POST /wp-admin/admin-ajax.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/cf_purge.sock:", host: "www.example.com", referrer: "https://www.example.com/wp-admin/plugins.php?plugin_status=all&paged=1&s"

4. When I delete Deletion failed: There has been a critical error on this website.Learn more about debugging in WordPress.

Is there anything I should try again?

Thanks

Our debug log is getting filled with these messages as of the last update (2.1.5):

[24-Nov-2020 17:46:27 UTC] Servebolt Optimizer attempted to set header “Cache-Control: max-age=0,no-cache,s-maxage=0”, but headers already sent.
[24-Nov-2020 17:46:27 UTC] Servebolt Optimizer attempted to set header “Pragma: no-cache”, but headers already sent.
[24-Nov-2020 17:46:27 UTC] Servebolt Optimizer attempted to set header “X-Servebolt-Plugin: active”, but headers already sent.
[24-Nov-2020 17:46:27 UTC] Servebolt Optimizer attempted to set header “cf-edge-cache: no-cache, platform=wordpress”, but headers already sent.
[24-Nov-2020 17:46:27 UTC] Servebolt Optimizer attempted to set header “No-cache-trigger: 1”, but headers already sent.

Everything on our site is up to date.

hello, i use fastcgi cache in my site. This plugin is compatible with Nginx Helper plugin? thank you

Hi, with PHP 7.0 all things work fine.
Not so with PHP 7.3 it totally breaks the plugin backend.

In the logs I find the message:

PHP Fatal error: Uncaught Error: [] operator not supported for strings in …/wp-content/plugins/servebolt-optimizer/admin/admin-interface.php:193

Please change:
$links[] = sprintf('<a href="%s">%s</a>', admin_url( 'options-general.php?page=servebolt-wp' ), sb__('Settings'));

to:
array_push($links, sprintf('<a href="%s">%s</a>', admin_url( 'options-general.php?page=servebolt-wp' ), sb__('Settings')));

That should fix the issue.
Thanks

Hi guys,

Does Full Page Caching refer to a Cloudflare cache everything rule? If so, isn’t a Business plan required for cache-busting (with cookies)? And does your “purge all” clear the cache for the entire zone, or purge each URL individually?

Cheers!

• This topic was modified 4 years, 9 months ago by menathor.
• This topic was modified 4 years, 9 months ago by menathor.

FYI: I receive the following warnings in debug.log.

[17-Feb-2020 13:17:12 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at ###/public/wp-includes/general-template.php:2956) in ###/public/wp-content/plugins/servebolt-optimizer/class/servebolt-nginx-fpc.class.php on line 117

Same errors for line 118, 119, 121, 122, 124, 125 in same document.

(deleted) No worries. I figured out how.

• This topic was modified 5 years, 4 months ago by apartmentsforrentx.

Hi guys,

Just wanted to check if the plugin is still being actively developed?

Is there any point in running this if I’m using Scalability Pro? https://www.wpintense.com/product/scalability-pro/

And does this improve searches / pagination speed in wp-admin too?

Thanks!

• This topic was modified 5 years, 4 months ago by menathor.

Hello.

Your plug in adds another index on wp_postmeta table on meta_value column making all the columns of the table to have an index. Is this a good practise? Isn’t having a full index on all columns make things slow down on UPDATE DELETE INSERT queries?

Thank you.

Can you list what features work ONLY on Servebolt servers?

Thanks!