Hi @linxie, the site you provided is not reachable, could you please check.
Thread Starter
linxie
(@linxie)
Hi Stanley,
It might be the firewall… what’s your IP?
Thread Starter
linxie
(@linxie)
This might help – Report Number: DORCSIJW
You can use https://wp.api.litespeedtech.com/ips for the list of IPs used.
Quickly passing your CSS file https://exclusiveweb.co.za/min/8c000.css through a CSS linter reveals you have an error on line 6752.
@media only screen and (max-width:768px) {
.fl-builder-content .fl-module-content-slider .fl-slide-0 {
background-color: #fc44444 !important
}
}
The error is with the background-color code #fc44444, which is not valid. HEX should be six, and not seven characters in length.
If you fix that error and purge CCSS then process CCSS again, it should work.
Thread Starter
linxie
(@linxie)
I’ve found the issue with the padding being added – it was an issue with beaver builder and the fixed header, so I’ve just disabled the fixed header so long.
After going through all the CSS, I’ve removed any issues it had with the use of !important and fixed that Hex value, but I’m still getting the same error when trying to manually run the cron to generate the CCSS.
We’ve added that list of IPs to our whitelist now, so you should have no issues accessing the site.
The error message Failed to post via WordPress: Too many frequent errors happens when the CCSS fails to often, you are rate limited for a period of time to prevent your site from requesting CCSS again and again when it keeps failing.
I can see that your site homepage CCSS is generated, which shows it’s working now after fixing the CSS error. You just had to wait a short period of time for your site to be allowed to send more CCSS requests to the API.
————
Checking your page https://exclusiveweb.co.za/web-hosting/, I can see /*CssSyntaxError: /min/aa7bf.css:1:138747: Unknown word*/, again running https://exclusiveweb.co.za/min/aa7bf.css through a CSS linter picks up a lot of errors.
I will list a few below:
line: 4800
.fl-node-5d1d91338fd14 .pp-pricing-table .pp-pricing-table-col.pp-pricing-table-highlight .pp-pricing-table-column .pp-pricing-featured-title {
background-color: #ccc;
color: #
}
line: 4838
.fl-node-5d1d91338fd14 .pp-pricing-table .pp-pricing-table-column .pp-pricing-table-duration {
font-size: 12px;
color: #
}
line: 4845
.fl-node-5d1d91338fd14 .pp-pricing-table .pp-pricing-table-column .pp-pricing-table-features {
font-family: "Raleway", sans-serif;
font-weight: 400;
font-size: 14px;
color: #;
text-transform: none;
text-align: center;
min-height: 0px
}
There’s many more if you search that file for color: #; you will find around 182 errors.
Thread Starter
linxie
(@linxie)
It appears the plugin I’m using for the pricing table is causing this so I will need to remove it and just hand code the pricing table.
Thanks for your help sorting this out.
A lot of the time with plugin generated CSS issues they arise from configurable options, where there are empty inputs.
Check to see if it’s not as simple as filling them empty input boxes with a valid colour value to resolve the errors.
If this is an issue with the table plugin https://www.ultimatebeaver.com/modules/table, you should report it to the author, and they can then push a fix to resolve this for you and all the rest of their customers.
Thread Starter
linxie
(@linxie)
Thanks, it’s the both pricing packages and the tables further down.
I’ve found a quick fix (giving those colours values didn’t work):
I saved the comparison tables as a module, removed them from the affected pages, ran the ccss, then added them back after the ccss generated. The errors aren’t resolved, but because there were less errors, the ccss generated without issue.
I will need to get in touch with Power Pack and Ultimate Beaver about these errors.
Thanks again for all your help, it is most appreciated, and I can finally rest easy now that I have ccss for all my pages.