marampb

Hi Raul

The issue was fixed. thanks for the quick fix.

I removed the wrong elements in the over the fold part, and back to a more normal setting.
i keep however having problems once the css processing is activated. i almost removed (excepted) all the folders that might have css inside, but i still keep having “ugly” page display. tried the different configurations, but still something which hang the page. looks like the bottons and some overlays get broken.
no css is reported as being processed, except some google fonts.
all cache is cleaned and my testing firefox clean cache each time i close it.

i currently deactivated the css processing. i kept the js part, and i will come back when i have some time. need to continue on other parts of this dev site, before coming back to optimisation side.

seems there are 2 methods of css processing. the previous one (present till 1.4.4 worked better on my side), the new one a little bit less. that’s life ??

if possible having a toggle in between old fashion optimisation and new one – if possible
could be nice. for sure if possible.

Anyway thanks for all your investment, and pro dev done for this plugin.

regards,
B

No Problem.
Thanks for your hard work for this plugin
B

same behaviour on both – safari Mac (Version 10.1.1 (12603.2.4))
and firefox Mac (53.0.2 64-bit)

regards,
B

Hello Raul

I confirm this regression on the version 1.4.9. All worked fine on 1.4.8.
some of the settings in – settings menu and advanced menu – for example

Disable minification on CSS files
Inline all enqueued CSS
Skip deferring the jQuery library
Skip deferring completely on the login page

are not getting saved.

regards,
B

Yes Sir!

Perfect ?? now it is working !
There are some css not correctly loading in frontend as “planned”, but this is normal.
I will exclude them on the proposed list ??

really Great! This is a 5 star plugin!
your support is best in class. I also really appreciate the “pro” clean implementation, and the missing advertising/add-ons or hard pushing by any mean for buying something.

All my best regards and success for the new devlopments!
B

Thanks a lot ??
maybe a “switch” in between using the “old” techno and “new” techno for CSS ?
could be nice.
info – i already tried the version 1.4.7.1 – with no success.

thanks
B

Hello Raul

just did a quick check to the plugin – WP Async CSS – created by Robert S?ther.
I saw a mention of this plugin in one of your recent discussions, on the version 1.4.4 asking you to implement this ??
The behaviour is exactly the same (nginx gateway error).
It looks like my website “does not appreciate” the functions included. Maybe there are somme commonalities in processing the css in between that plugin any fast velocity?…
Is there any incompatibility with Apache 2.4/php7 of that supposed feature.

thanks in advance
best regards,
B

Hi Raul
thanks a lot for your answer.
i apologise. On my first contact i forgot to thank you for this “best in class plugin”
despite the problem i have since the version 1.4.5, I remain convinced it is one of the best i ever seen! ??

These are the logs reported in the plugin. (i replaced my domain name and the port). if needed i can share this information with you offline.
—————————————
fvmcss-022bd250c026a013a-1493849831.min.css

– REQUEST FAILED () – //myFQDN:myPort/wp-includes/css/dashicons.min.css
– REQUEST FAILED () – //myFQDN:myPort/wp-includes/css/admin-bar.min.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/plugins/responsive-cookie-consent/includes/css/style.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-parent/style.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/plugins/unyson/framework/static/libs/font-awesome/css/font-awesome.min.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/plugins/unyson/framework/static/libs/qtip/css/jquery.qtip.min.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/plugins/unyson/framework/extensions/feedback/extensions/feedback-stars/static/css/styles.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-parent/css/bootstrap.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-parent/css/jquery.mmenu.all.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/uploads/the-core-style.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-child/style.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-parent/css/prettyPhoto.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-parent/css/animate.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/plugins/unyson/framework/extensions/shortcodes/shortcodes/section/static/css/background.css
– FROM CACHE: //fonts.googleapis.com/css?family=Raleway:700,300,100,100italic|Martel+Sans:200,regular|Crimson+Text:regular|Open+Sans:300,300italic&subset=latin,latin-ext,devanagari

fvmcss-0d3be1db5026a013a-1493849831.min.css
– REQUEST FAILED () – //myFQDN:myPort/wp-includes/css/dashicons.min.css
– REQUEST FAILED () – //myFQDN:myPort/wp-includes/css/admin-bar.min.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/plugins/responsive-cookie-consent/includes/css/style.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-parent/style.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/plugins/unyson/framework/static/libs/font-awesome/css/font-awesome.min.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-parent/css/bootstrap.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-parent/css/jquery.mmenu.all.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/uploads/the-core-style.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-child/style.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-parent/css/prettyPhoto.css
– REQUEST FAILED () – //myFQDN:myPort/wp-content/themes/the-core-parent/css/animate.css
– FROM CACHE: //fonts.googleapis.com/css?family=Raleway:700,300,100,100italic|Martel+Sans:200,regular|Crimson+Text:regular|Open+Sans:300,300italic&subset=latin,latin-ext,devanagari
—————————–

status of the different toggles:
ON: Use the default dynamic “//” protocol
OFF: Force HTTP urls [ needed for the CDN Enabler plugin ]
OFF: Force HTTPS urls [ needed for the CDN Enabler plugin ]

HTML Options
HTML Options
OFF Disable minification on HTML
OFF Strip HTML comments
OFF Fonts Options

CSS Options
OFF (when on site broken) CSS Options Disable CSS processing
ON Disable minification on CSS files
ON Inline all enqueued CSS

JavaScript Options
OFF Disable JavaScript processing
OFF Skip minification on JS files

————–advances

Render-blocking JS
ON Render-blocking Enable defer parsing of JS files
ON Enable defer of JS for Pagespeed Insights
ON Skip defer of JS for the jQuery library
OFF Load CSS asynchronously with loadCSS and rel=”preload”

exclusions:
/wp-includes/js/jquery/jquery.js
/wp-includes/js/admin-bar.min.js
/wp-includes/js/jquery/jquery-migrate.min.js
/wp-includes/js/jquery/ui/effect.min.js
/wp-includes/js/wp-embed.min.js
/wp-content/themes/the-core-parent/js/

preconnect headers:
//fonts.googleapis.com/
//fonts.gstatic.com

on server side:
virtual port based on port
HTTP
HTTPS 9433
root — myfolder
HSTS on
HTTP/2 on
main server – apache 2.4
main php – 7.0

the message reported on the browser is 504 Gateway Time-out nginx

note: my site is intended to work on https. i added a plugin which replace widely the http or https with // this for avoiding having mixed content problems.
i didn’t check – if you think useful i can deactivate it, and force here the https, and also to rewrite this part of the .htaccess

additional information – my dev website is hosted on a synology system (this is why the combination of different web servers) and the server is in prod. the dev website is on the virtual host in purpose, before it is migrated to a new hosting.

thanks a lot
B