blau

Thank you for clarifying!

@thebrandonallen thank you, I created a dedicated plugin for the additional filter settings.
Renaming the administrator user and blocking “admin” via fail2ban has been the single biggest security improvement in my sites.

Thank you Brandon, I put it in the plugin wp-fail2ban-redux.php file, it works well, hope it survives next upgrade.
Thank you for porting the original wp-fail2ban plugin, have a nice day.

It’s a Debian 8 nginx php mariadb setup, it’s not causing any issue.

I use it with nginx as the only webserver and it works very well. You should check your setup because you may end up logging localhost for the failed logins, as this is the source address of the requests that apache sees.

Thank you Christopher, the linked documentation is the starting point I was looking for. Have a nice day!

Interesting, solved my problem as well. Thank you.

Hi frank, I can’t remember the original AO version, my guess is a Pagelines Framework snafu, but can’t be sure because I didn’t notice it immediately when I did my step by step upgrades.

blau

hello futtta,

just for your information I ran into issues after a mass upgrade to:

autoptimize 1.8.5
wordpress 3.9.1
Pagelines Framework 2.4.5

– top navbar dropdown menus no longer there;
– feature slider css broken, shows all feature images instead of transition effect.

Solution: Simply disabling html optimization fixes the issue. The other setting
is just css optimiziation, no js.

If you like, you can see the site here (in fixed state):
https://alfabeta2.bamaulion.net/
Just tell me if you need me to reproduce the error.

I see. I will keep an eye on the cache to see if it grows again. Thank you for your time.

Edit: 1000 files in 20 minutes. Disabled js optimizing and let’s see.

Hi Frank, thank you for your reply.

Would it be feasible to have a cron job clear the cache, say, weekly? What would the command be? This one?

https://www.example.com/wp-admin/options-general.php?page=autoptimize&settings-updated=true

I disabled NextGen for the time being. In the long term I will disable eShop and replace it with another ecommerce plugin.

Good to know.

The NextGen changelog has dates added, so I know that
V2.0.23 – 09.16.2013
https://www.ads-software.com/plugins/nextgen-gallery/changelog/

and I started noticing the problem only in November.

Do we have dates fot the eshop changelog?
https://www.ads-software.com/plugins/eshop/changelog/

I just sorted the thing and am thinking. In fact, NextGen works well side to side with eShop, so the malfunction seems to fall on the eShop side. Not blaming faults at anyone, mind you.

The NextGen settings apparently have no configuration option that interferes with content transfer or authentication.

Eshop as well does not have obvious troublesome config options.

This has happened about November 2013, end of November perhaps.