Tommy78

That would be great, thanks!

Hi David,
Thank you for your reply.
If this basic feature will be part of Premium version then I guess it’s time to look for another solution that offers a decent level of security without being annoyed on a daily basis to upgrade to a Premium plan – all being well, before the end of this month…

Hi Prashant,
Thank you for your reply but my questions are not answered.

You mention the new firewall system is using the 6G rules, but according to the notification in the AIOWPS-dashboard the firewall system is PHP-based. The 6G rules are .htaccess-based.
What is correct?

According to your answer, I can disable the PHP-based firewall function by turning of the 6G rules in the dashboard. However, the 6G rules are already disabled in all of my WordPress-websites since almost two years. I am already using the 7G rules, which are more robust, and have added them as custom rules in the .htaccess-file.
At the same time I can see an aiowps-bootstrap.php-file in the root-directory of my WordPress isntallation and also some references to this file in the .htaccess-file in the same directory.
So my conclusion is now that the PHP-based firewall is still actie (the aiowps-bootstrap.php-file exists), but the 6G rules aren’t (they are .htaccess-rule based and do no appear in the .htaccess-file).

So, again, please answer my questions:
1. Where can I find the settings for this PHP-based firewall functionality?
2. How can I disable this PHP-based firewall functionality?

And in addiiton:
3. What does this PHP-based firewall functionality add to this existing one?

No problem. I realized that the solution I provided in my previous post is not a proper one either, it breaks the lay-out on smaller screens.
Thanks!

You’re probably experiencing the same issue as described here.

A temporary solution is to disable the Cache rebuild option on the Advanced tab of the WPSC Settings page.

Honestly, I think the lay-out is still broken. The grey line should be below the tabs, not above.

This makes it look like it’s supposed to be:

<style type='text/css'>
#nav h2 {
border-bottom: 1px solid #ccc;
padding-bottom: 35px;
}
table {
clear: both;
}
</style>

I filed the initial problem of this thread as an issue on GitHub, hoping to get the developer’s attention.
Hope it helps…

It’s an issue on GitHub.

Yes, I am seeing the same. Layout in the dashboard is broken.

It’s a bit disappointing to see that none of the plugin authors has taken the time to reply to this topic. It’s two weeks since the issue was reported and more and more sites are affected by this.

It seems you’re having the same issue as described here. Hope this will be fixed soon.

Sorry, but I can’t comment on your question about preload of the mobile posts.

Indeed, the bug is still there.

It appears to me that whenever WPSC needs to display non-cached content (e.g. rejected user agents, excluded posts) it’s supposed to be searching for files that need to be rebuild using the Cache rebuild feature and delete these, but instead of that it’s deleting valid cache files.

I would really like to see a comment of one of the plugin authors on this.

Just noticed v1.4.6 was released. Anybody knows if this issues has been resolved in this update?

The cache rebuild function does have sense, see the question “What does the Cache Rebuild feature do?” in the FAQ. If I understand correctly, disabling may cause an increase of serverload on sites with lots of visitors.

Disabling may solve the frontpage from not caching, but I still think this is a bug which should be fixed.

wish the developer of Supercache would let us know if he’s working on this bug though

I agree, I would also like to know if the issue is being addressed. The method described by Tony Franco might be a good temporary workaround, but for the time being I’m back to 1.4.4 which caches the frontpage just fine.