Hristo Pandjarov

What user agent are you using for that app?

Threads are left open for ongoing issues. This is a feature request that I am afraid we will not be adding to our plugin. If you want to receive a purge feedback you can navigate to the SG Optimizer – Caching page and press the button there. There is a temporary message confirming that the cache has been cleared. If you use the top menu, then the page reload is sufficient to consider the cache cleared.

Yes, enabling combination does that. Exceptions are handled by default rules, interface, filter or both. This current case will be covered by a filter. I am sorry if that’s not your preferred way to handle this.

At this point we will not be excluding such scripts by default since that brings more risk of introducing bugs to users than using the filter when actually using it. Furthermore, each check increases the time necessary to process the request.

I am sorry that you feel this way. Our team puts a lot of effort in addressing all reported issues and fixing them. While we mark issues as solved, feature requests are a different story. We can’t just put into production every recommendation without evaluating it and considering it within the big picture of our plugin development. It’s normal for such cases to be closed, marked as solved even if not applied and released immediatelly.

The popup is designed to be shown only once. It seems some other plugin is interfering with the admin notices causing them to loop over and over again. That’s the first time this is reported to us, please open a ticket in the forum and we will make sure to fix it ??

Please, disable the 2FA authentication if you are using it until we release an update.

@jdembowski ^^

My bad selecting the wrong topic for report. This is a hosting review, not a plugin review. CPU seconds overuse can be caused by hundreds of different things. Same goes on the comment on the hosting support.

The plugin handles automatic cache purge just fine and it powers about a million WooCommerce installations. This is indeed an issue with your sites and the way they are developed. Please stop Memcached if you are using it right away, some plugin extensions for Woo don’t play well with object caching and cause problems similar to what you are describing.

The plugin automatically purges the cache where pages are updated, comments are posted, etc. That’s literally the first feature it had. I would check error logs why something is blocking it form cache purging. If you want, you can open a thread in the forum with more specifics and we will dig right into it and tell you more.

add_action(
    'init',
    [$this->getBlocker(), 'registerOutputBuffer'],
    11
);

add_action(
    'shutdown',
    [$this->getBlocker(), 'closeOutputBuffer'],
    11
);

public function registerOutputBuffer() {
    if ($this->isEnabled()) {
        \ob_start([$this, 'ob_start']);
    }
}

public function ob_start($response) {
    // do whatever the plugin does

    return $modified_html;
}

public function closeOutputBuffer() {
    if ( ob_get_length() ) {
        ob_end_flush();
    }
}

Do not rely on the shutdown action to close the buffer. Instead of modifing the output and wait for WordPress to close it, use one of the recommended buffering functions.

The contents of this internal buffer may be copied into a string variable using ob_get_contents(). To output what is stored in the internal buffer, use ob_end_flush(). Alternatively, ob_end_clean() will silently discard the buffer contents.

The reason why shutdown action closes the buffering is to prevent forgotten opened buffers, Do not rely on it, it’s there to prevent a white screen…

Hey @mguenter

First we would like to point that we are very happy when other plugin developers are working on making their products compatible with ours. Thank you for the efforts you have put on this so far.

However, what you’re suggesting is not the best way to achieve what you’re after. We’re applying all our optimizations via this parser and adding the option to modify it will endanger the overall functionality of the plugin. That’s why I am afraid we won’t be able to provide the requested filter.

We are using default priority of 10 to open and close/flush the buffer, so you can open a new one with priority of 11 and modify the HTML content after it is being returned from our plugin.

This way some incompatibilities can be avoided and each plugin will handle its own changes only.

This is a problem with your theme and not the plugin or WooCommerce.

Thanks for reporting this, we’ve managed to locate the problem and will apply a fix in the upcoming maintenance update.