Hey Thomas,

Thanks for the ideas.

The decision to load the post css files late are that the CSS rules set in an element and placed in this file must override default CSS rules and we tried to use weakest selectors wherever possible to allow custom CSS rules (if necessary).

If you use filter ‘avf_post_css_create_file’ (return false) the CSS rules are placed inline in style tags right before the elements instead of the post css file.

Question is, what are “critical” CSS rules. We could consider to add those to a second post css file that is loaded first (or add them inline in header).

Best regards,
Günter

Hi,

Select Your Editor -> Use Classic Editor
Disable Block Editor For Selected Post Types:

You can only disable block editor for post tyes, means with Strg + Click select the post types you never want to use block editor.

e.g. if you select page and posts these will always open in classic editor (only “Edit” is visible),
portfolio will have “Classic Editor” and “Block Editor” links below title on “Portfolio Items” page.

Best regards,
Günter

Hi,

@sky19er

documented in place

in the file where we add the filter we add a comment with the parameters.

Best regards,
Günter

Hi,

Can you please add the following code:

.avia-related-tooltip{
	position: absolute;
	z-index: 9999999;
	padding: 0;
	width: 200px;
	border-radius: 2px;
	box-shadow: 0px 3px 13px 0px rgba(0, 0, 0, 0.1);
	border-width: 1px;
	border-style: solid;
	padding: 15px;
	margin-top: -10px;
}


.avia-related-tooltip .avia-arrow-wrap{
	top: auto;
	bottom: 0;
	position: absolute;
	left: 50%
}

.avia-related-tooltip .avia-arrow-wrap .avia-arrow{
	border-top: none;
	border-left: none;
	top: -4px;
}

at the bottom of enfold\css\shortcodes.css (will be added there in next update)

or until next update to the Quick CSS field.

FYI: Code is moved from enfold\config-templatebuilder\avia-shortcodes\blog\blog.css which is not loaded when blog is disabled.

Best regards,
Günter

Hi,

Best regards,
Günter

Hi,

Sorry for the problems.

When loading the page I get following error for

GET https://your_site_name/wp-content/uploads/avia_posts_css/post-5.css?ver=ver-1629459115
----
Status403
Forbidden
VersionHTTP/2
Übertragen894 B (752 B Größe)
Referrer Policystrict-origin-when-cross-origin

This file holds the CSS to display the background images and other styling needed for this page (this was added starting with 4.8.4).

One user could solve it by enable query parameters (which he had blocked before) needed to invalidate browser cached post-5.css file when page is updated (?ver=ver-1629459115).

Alternate way (but not recommended, only if your server configuration makes it absolutly necessary) is to disable file generation by adding this to your functions.php file:

https://github.com/KriesiMedia/enfold-library/blob/master/actions%20and%20filters/Performance/avf_post_css_create_file.php

For testing and until you find a solution with your hoster it is OK.

Best regards,
Günter

Hi,

Did you read https://make.wordpress.org/core/2021/06/07/wordpress-5-8-adds-webp-support/ chapter “Using WebP images”

Seems not all browsers support webp yet.

There is a polyfill to load: https://github.com/chase-moskal/webp-hero

Best regards,
Günter

Hi,

Best regards,
Günter

Hey S.,

Sorry for the late reply.

Thank you for these ideas and the feedback – we started discussion about it already.

We certainly will pick up some of it in near future to make it easier for users.

Have a great day.

Best regards,
Günter

Hi,

@Guenni007

Thanks – uploaded the wrong file. Fixed it.

Best regards,
Günter

Hi,

Thank you for using Enfold.

As suggested by @Guenni007 we added svg and webp to filter list.

Please replace

enfold\config-templatebuilder\avia-template-builder\php\class-html-helper.php

with the content of

https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_8_6_2/class-html-helper.php

– Do not forget to make a backup of the original file for a fallback
– Clear server and browser cache

If you need help please let us know and we can do it for you.

Best regards,
Günter

Hi,

@BigBatT

Thanks a lot – already added to core.
I asked Yigit to keep you on the list to be informed.

Have a great day.

Best regards,
Günter

Hi,

Thank you for the feedback – and glad you found the problem.

Enjoy the theme and have a great day. Feel free to come back when you need further assistance.
I will close the topic for now.

Best regards,
Günter

Hi,

Glad that it works now.

Please have a look here: https://kriesi.at/support/topic/post-css-and-caching-issue/#post-1316059

Could the query string cause the problems in your setup ?

Best regards,
Günter

Hey mterrianrode,

Thank you for using Enfold.

Actually Enfold should be able to deal with 7.0 or higher – this message is not php related.

Can you try to increase your memory limit – see https://docs.woocommerce.com/document/increasing-the-wordpress-memory-limit/

Best regards,
Günter