Error
-
Hi, I’m using the plugin with api but receive the following error when trying to generate the critical css:
Job status is ERROR (j-1auesb)
– Job ID: gen-8745968
– Status: STATUS_JOB_BAD
– Result: null
– Validation: NONE
-
and is this the case for all jobs, or do you (also) have P or D jobs?
Hey Frank,
I initially get a list of N jobs. These later change to P jobs and then to E jobs.
The strange thing is that when i login to the CriticalCSS website, i can see the list of my jobs and most have a “tick” showing the critical css (Ccss) has been extracted successfully. These have “api” listed next to them showing they were generated by the plugin.
There are some urls which state the Ccss looks different, and if i regenerate the Ccss, the error goes away.
So there seems to be some issues getting the Ccss back to the plugin, and also occasionally the plugin not creating the Ccss correctly (which is does first time when generated directly on the CriticalCSS website.
OK, can you enable debug logging (under “advanced settings”) and let it run for some time (4-24h) and mail me the debug log (
wp-content/cache/ao_ccss/queue.log) at futtta-at-gmail-dot-com so we can have a look?Do i have to leave my page cache disabled while i run the debug?
not necessarily π
I just reneabled the plugin and noticed my previous jobs list and api key are gone.
Could you tell me, do i have to leave this plugin active all the time (in terms of paying for the monthly subscription fees) for it to work?
My initial intention was to automatically generate the Ccss for all site pages, and then for new posts add the Ccss manually by using the website directly.
I would like to use the plugin to occassionally check my pages again to ensure the Ccss is updated and update automatically if required.
But currently i don’t really have a use for an ongoing monthly subscription. The other powerup for Ccss allowed you to make changes and keep those changes which was great as i could pay for when i needed to use the service.
With this plugin it seems like you have to pay continually and there’s no way to pause it without disabling the plugin?
this one indeed requires an active account at criticalcss.com. you could alternatively keep on using the previous, non-automated version?
I did see that suggested on the website. The reason i went with this plugin was for the automation. Something that’s useful for me now and in future.
The other plugin would require manual updates to the Ccss, which is something i’ve had to do occasionally. But this can be a pain when having to keep track of this.
I guess what i need is a way to pause the subscription and only turn on the automation when required (e.g., first time adding Ccss to site, theme updates, after major update).
On a different note, on the website it mentioned about not using any plugin that optimizes your css and JS.
My theme offers the ability to minify and combine css/js and the developers said it’s compatible with AO.
But i’m wondering if it’s a good idea to have this enabled now after reading the warning on criticalcss.com?
My theme offers the ability to minify and combine css/js and the developers said itβs compatible with AO.
should be OK really.
Hey Frank,
Just wanted to check with you if you plan to continue supporting the plugin for manual critical css insertion and that it’s not going to be superseded by the automatic plugin? Thanks
the manual plugin will keep on working, yes, there are no plans to sunset it at the moment π
Do you need an active criticalcss membership to use the manual plugin?
yes, I’m afraid you do π
Damn, this critical css is expensive!
Sorry Frank, just want to make sure i understood correctly.
If i have an active membership and enter my critical css in AO using the manual plugin, do you mean that the critical css will no longer function if my subscription expires?
The topic ‘Error’ is closed to new replies.