fouedex

Works now (after deleting all rules), thanks !
Keep up the good work. Removing debug env.
Merci.
F.

• This reply was modified 4 years, 10 months ago by fouedex.

Oups, can’t remember if it was checked by default.
It’s on now. Should CCSS be regenerated for each page automatically ?
F.

There you go Screenshot

• This reply was modified 4 years, 10 months ago by fouedex.

Aggregate CSS was already checked.
Which screenshot do you need ?
Bonne soirée !

https://bamsoo.com
Debug active.
F.

Will do & keep you posted.
F.

Hi !
Tried everything I could imagine, but still no luck : every page (is_page) uses the same CCSS. I could create rules for these, but my understanding is that it should be done automatically, right ?
Any insights, please ??
F.

Thanks !

Done, but still no luck, no Toolset post types in drop down.

F.

• This reply was modified 4 years, 10 months ago by fouedex.

Super weird ??

$cpts = get_post_types(
            array(
                'public'   => true,
                '_builtin' => false,
            ),
            'names',
            'and'
        );

actually returns the custom types, but still, they are not available in the drop down…

• This reply was modified 4 years, 10 months ago by fouedex.

re. “Path based rules don’t match my type slug neither”: but did you enter critical CSS in the rule, or is it waiting to be processed?

Waiting to be processed “To be fetched from criticalcss.com in the next queue run…”. In the process queue is is_single instead of my path rule.

“I wish I could have 1 CCSS by page, which is the case, and one per type, which I can’t achieve.”; what to you mean with one per type? because manual rules notwithstanding, that is exactly what should happen; blogposts are not served by individual rules, but by is_single, archives by is_archive, search by is_search, …

I want one CCSS per Custom post Types (Toolset ones), but can’t see the in the drop down (investigating this), and can’t path rules match.

Thanks ??

Hi && thanks for the good help ??

I still don’t see Toolset types in the Conditional Type Rule, even in latest beta.
Maybe a creation type configuration.

Path based rules don’t match my type slug neither.
/agency/ or agency/ are still interpreted as is_single.

I wish I could have 1 CCSS by page, which is the case, and one per type, which I can’t achieve. Maybe a PHP way : is that what you meant above ?

if needed the same logic (switching from conditional to path-based) can be extended to other types with a couple of lines hooking into the API, let me know if you’d like an example of that ??

F.

Still no luck with beta : none Toolset created types listed.

AO : 2.6.2
AO CCSS power-up : 1.18.0
Both latest I believe.

As a complement, I have a CPT say “agency” which URL is //…/agency/…
As I can’t see them in the list, I created a Path based Rule (Path = /agency/).
Pages I see in the job queue are still associated with target “is_single” and I see “To be fetched from criticalcss.com in the next queue run…” for a long time (ao_ccss_queue runs normally every 10 min).

So the CCSS of a given post of type is_page is not directly editable ?