Carsten Meiselbach

Hello & thanks for your feedback.

Yep, seems to be an issue with page code on my side. I’ve found the problem, it’s now solved. So everything ok with WPP ??

Best regards.

…and not to forget:
https://happycarb.de/wp-json/wordpress-popular-posts/v1/popular-posts/widget/2?is_single=0 is requested twice with same results, even the placeholder “wpp-widget-placeholder” is available once within the Markup.

Best regards.

Hello Raul,

with FVM Version 3.2.1, CSS / JS Minification is running again for all my assets.

Thanks!

Best regards.

FYI: I’ve installed FVM Version 3.1.8 and the CSS / JS Minify problem is still existing. Combine files is working.

Best regards,

Carsten

• This reply was modified 3 years, 10 months ago by Carsten Meiselbach.

“Enabled CSS Processing” and “Combined CSS Files” is enabled.
CSS files to be ignore are checked, working as excepted.
wp_enqueue_style is used for main style, which is not minified.
Cache Purge etc. already done (using WP Rocket).

Overall it might be server environment related. Which tool you using for (CSS) minifying?

Best regards.

Hello Raul,

I just checked this again and made sure that I’m not logged in. It does’t work.
You need to open the (single) css and scroll a little bit down to see the details. E.g. beginning with this parts it’s not working.

`/*
Theme Name: Default
Theme URI:
Author: gVectors team
Author URI:
Description:
Version: 7.0.0
*/
/* wpDiscuz CSS Style */

#comments{max-width: 1100px; margin: 50px auto; color: #333333; font-style: normal; }
#comments p, #respond p{ float: none!important;}
#wpdcom{max-width:750px; padding:0; margin:7px auto 15px auto;}

Best regards,
Carstem

Hallo und danke für das Feedback. Die benannte Funktion dazu werde ich mir anschauen.

Der Preconnect ist relevant für einen schnelleren Netzwerkzugriff der VGWort Tracking-Domaine. Hilft etwas beim Laden der Seite. Schaut doch mal, ob ihr nicht dazu eine Admin-Option mit einbauen k?nntet.

Beste Grü?e.

Hola Héctor,

thanks for your feedback.

Lazy loaded conflicts wasn’t my case here. I’ll disabled your setting, my WP Rocket is also disabled for this. Instead, I’m sing the Lazy Loader-Plugin from Florian Brinkmann, MarcDK, which is running fine for all my needs.

I now find a solution for me.

An inproper CSS setting for inner

• items with overflow:auto was resulting into an incorrect box sizing. Concerning the empty container .wpp-widget-placeholder with undefined height: i added a min-height for .popular-posts and this way, the shifting is now at bearly nothing and not an issue for Google’s CLS assessment anymore!

  Since it’s not a good option to directly place the top post widget (without AJAX) and using very short page caching time, my given solution runs fine.

  Overall i try to keep requests also for other things like comments low when I’m using AJAX requests for this.

  So overall I could avoid using some of the named poison options here ??

  Best regards & keep healthy,

  Carsten

Hello Héctor,

big thanks that you involved the FVM Plugin Author here.
So we’re looking forward what could be done here.

Best regards,
Carsten

Hello & thanks for your quick help. I’ve add the Plugin Asset Path to the ignore list of FVM and it worked again.

Could you tell me what inline code is exactly removed by FVM? Maybe I could add this manually to my global JS that FVM could work again without the ignored path.

Best regards,

Carsten

Sorry, I need to deactivate your Plugin again since it makes to much Side effects on my Website but I reactivated it now again.

Please give it a quick check on my named testpage.

Cheers.

• This reply was modified 4 years, 8 months ago by Carsten Meiselbach.

Hi Héctor,
thanks for your fast feedback.

Error thrown is this:
Uncaught SyntaxError: Unexpected token ‘:’

Testet with Chrome and FF newest Version.

Testpage for you: https://happycarb.de/kontakt/

Good to know that your Plugin doesn’t need JQuery. I’m curious what might be the source of the problem here.

Best regards,

Carsten

Hi Shortbookandscribes,
I already opened a ticket, so everything is currently underway.
Best regards.

Oki do, done.

Hi again,
today I’ve done another posting test, this time it work with our Subscriber Mailing.

I’m still running one Version 4.3.2-beta2, no change since the last test on.
If you changed something in between for your servers: it worked for me, but I will take an eye for the next posts.

Kind regards,

Carsten