szmigieldesign

szmigieldesign.pl seems to work fine, photography.szmigieldesign.pl stalled and there’s no way to push it further (timeouts or next request in 24 hours). I’ve removed 6G Firewall from .htaccess but it didn’t help.

Also, optimization stalled at:

https://www.dropbox.com/s/qli6ni1vfgrqsy7/Screenshot-2017-11-11%20Image%20Optimization%20%E2%80%B9%20szmigieldesign%20photography%20%E2%80%94%20WordPress.png?dl=0

I believe that 6G Firewall may be causing problems with LiteSpeed Cache image optimization. The whole .htaccess firewall rules can be found here – https://perishablepress.com/6g/ – if you wish to analyse them.

I’m also using WordFence on both szmigieldesign.pl and photography.szmigieldesign.pl but szmigieldesign.pl lacks 6G Firewall rules and there are no problems with communication between my site and Image Optimization Server.

Sorry for the late reply. Latest public build fixed all issues that I had. Everything works fine again.

That might do the trick. I’d plug it into WP Cron to do checks once per day or so in order to alert users that something is wrong.

It seems that cache module is licensed for my hosting provider and it works.
However, somehow it requires manual activation that I wasn’t aware of and I wouldn’t knew it if it wasn’t for weird and long server response times.

Wouldn’t it be wise if LiteSpeed Cache plugin had the ability to check Response Headers and generate a warning if something’s wrong just to inform users that the cache might not be set up properly?

Do I have to push optimization request every 100 images? Isn’t the process automated for whole media library?

Hm, but this is strange – both main site and photography portfolio are on the same server. Perhaps it’s because of 6G Firewall rules in .htaccess. It may be missing in main. Or WordFence.

Awesome, thanks!

Because they are loaded externally. Every other CSS loads from my domain and making it go async results in flash of unstyled content and sometimes even breaks the layout (BeTheme, Slider Revolution).

I work a lot with some commercially available WordPress themes (like Avada, BeTheme, Swift Themes) and typically the only resource loaded from different domain is Google Fonts. Making it async would improve the loading speed without the need of doing too much tweaking (either make it go async or not).

Awesome, thanks!

I will get back to you after I migrate the site from localhost to stable production environment. I’ll be able to provide FTP or dashboard access to our staging server afterwards. I have to migrate the site tomorrow and I’ll get back to you with support ticket.

I’ve tried doing test migration again and this time only about 1/2 of plugins didn’t activate. However, some must have been broken in the process as Revolution Slider was impossible to activate (I had to rewrite all plugin files). Critical plugins, like WPML didn’t activate at all too.

I’ll have to move sites from localhost to production manually tomorrow. I’ve tried this method and it works fine (with help of WP Migrate DB and / or Search-Replace-DB).

EDIT:
Muffin Builder data migrated OK.

• This reply was modified 7 years ago by szmigieldesign.

I’ve just tried a test migration from localhost to my dev server. Almost all plugins break (won’t initialize) due to broken plugin headers. Also, content formatted with BeTheme’s Muffin Builder breaks partially.

It’s not only a matter of permalink. If plugins or themes store data with % signs, those strings will also be affected.