Plugin Support
qtwrk
(@qtwrk)
the filter you used is for UCSS , you are talking about CCSS ?
please clarify which one that you are trying to do with
-
This reply was modified 9 months, 3 weeks ago by
qtwrk.
Thread Starter
mcdeth
(@mcdeth)
Yes, sorry about the confusion. Ideally, I’d prefer to have one CSS file per post type in both cases, for UCSS and CCSS.
However, it seems like the settings are being ignored. Currently, I can see that multiple products are being included in the CSS queue for both post types.
https://sendapic.xyz/view/uNiNPd
@mcdeth
UCSS will contain only the CSS needed to show the page correctly. This will fix the issue, and remove extra CSS from page.
CCSS will contain the CSS needed to show the above the fold(first screen when you navigate to page). This will speed up the loading.
They cannot be combined, they are added in different locations
Thread Starter
mcdeth
(@mcdeth)
Yes, I understand that UCSS and CCSS serve different purposes and are different.
My question is independently more about the expected behavior when using 1 UCSS/CCSS per post type.
If we have UCSS set per post type, why are multiple product pages still being queued for UCSS generation? Shouldn’t only one representative product be used for generating UCSS for that post type?
Similarly, with CCSS per post type, shouldn’t only one product page be used for generating CCSS for the entire “product” post type, instead of queuing multiple products?
What I’m worried is:
- having multiple UCSS/CCSS for products
- killing my quota on account because its constantly generating for products duplicate ucss OR ccss
Is this normal behavior, or is something not being respected in the configuration?
-
This reply was modified 9 months, 3 weeks ago by
mcdeth.
Plugin Support
qtwrk
(@qtwrk)
I just looked at the code, if I am not mistaken , it is always queued , but before sending to QC nodes , it will check UCSS locally first