Hello,
Trying to add a new class into my Content CSS for my homepage and add padding to another class. I hit Save, says “Saved!” but the new CSS I added just will not stay put.
http://dev.thehelpfulmarketer.com/
What bug is this and will it be addressed in the Theme Update coming out next week?
Hello There,
Thanks for posting in! This isn’t a bug. The css is saved in the custom css option. It is not displaying and taking effect in the live page because of caching. I can tell that you are using CloudFlare. Please login to your CloudFlare account and purge your site cache after making any site changes before testing your site again. For best results, please make sure that you are using the recommend CloudFlare settings which was explained in details here: https://xthemetips.com/using-cloudflare-rocket-loader-with-x-pro-and-x5/928/
Hope this helps. Please let us know how it goes.
No, I already have my caching turned off.
I can assure you that I have added a new class into my homepage css and it’s not saving.
I didn’t even give you the new class’s name, so I’m not sure how you would be able to tell that it did indeed save.
I’m looking at the CSS right now, and the new class that I’ve added and saved 5 times is not there, nor is the padding that I added to a different class.
I’ve read other posts that mentioned bugs with using Classic elements (which I have a mix of classic and V2) and a bug involving Yoast and CSS not saving.
Could this be related to either of those?
Hey There,
To assist you better with this issue, would you mind providing us the url of your site with login credentials so we can take a closer look? This is to ensure that we can provide you with a tailored answer to your situation. Once you have provided us with your URL, we will be happy to assist you with everything.
To do this, you can create a secure note with the following info:
– Link to your site
– WordPress Admin username / password
Thank you.
Secure note sent. Tried again tonight. Changes to homepage’s Content CSS are still not saving.
P.S. - the homepage seems to be the only page whose Content CSS is not saving. All other pages’ CSS is saving just fine.
Hello There,
Thank you for the credentials. I tried and yes, it is not saving. I found this error:
There’s a timed out error. Since this issue is specific to this page, it can be memory. You may check error log to see the specifics of the error. Then try increasing memory.
You can try adding this in your wp-config.php located at the root directory of your site.
define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );
You can add it before the line
/* That’s all, stop editing! Happy blogging. */
Hope that helps.
Thank you!
I’ll give that a try shortly.
What are those other errors under “Uncaught TypeError” that I’m seeing on your screen; the ones that all start with (cs-vendor? None of those come up in my Dev Tools’ Console.
My Console does show something similar- a bunch of yellow triangle warnings that say "cs-vendor.js:7407 WARNING: Binding style attributes may introduce cross-site scripting vulnerabilities; please ensure that values being bound are properly escaped. For more information, including how to disable this warning, see http://emberjs.com/deprecations/v1.x/#toc_binding-style-attributes."
Is that anything I need to be concerned about?
Hey Abby,
The error says there’s something wrong with the Javascript execution in Cornerstone.
The warning that happens to some server environments. It is not critical so you can ignore that for now. That might be fixed in the succeeding releases.
Thanks.
Thank you both.
I increased the memory limit in my wp-config, still no difference. Also tried a different browser, just in case.
Content CSS on Homepage is still not saving.
Hi a_buzon,
This is a plugin conflict issue, I suggest doing a plugin conflict test, the safest way to do that is to install “Health Check” plugin and enable “Troubleshooting mode” if everything went okay, then you can re-enable plugins one by one to figure out the culprit. The good thing about “Heath Check” plugin is that it’s developed by WordPress team and it only affects your logged in session so that other visitors won’t be affected.
I’ve already did that, and managed to add some CSS code like this one:
.themeco_test {
display: none;
}
and I confirm it’s appearing in both the backend and the frontend.
Thanks.
Thank you @Alaa. Luckily, my suspicion was correct and it was Yoast SEO causing the conflict, so testing didn’t take long.
Where do I go from here?
Is this an issue that you guys will keep record of and hopefully remedy? Do I notify Yoast as well?
I’m pretty much done with the site design, so hopefully I shouldn’t even need to add any further Content CSS. Am I ok to keep Yoast SEO on, or if there’s 1 conflict, there’s likely to be another?
Hi @a_buzon
I’ve reported this issue to our dev team for further investigation, for now, I narrowed down this issue to the homepage custom CSS content only, it works fine on other pages content CSS, so I believe you can just add the CSS codes there to (X > Theme Options > CSS), with a CSS rule targetting the home page like this:
.home
So, let’s say you want to style h5 on homepage only, so your code in Global CSS will be like:
.home h5 { font-size: 2em; }
Thanks.
Hi there,
I just wanted to let you know that the issue where CSS doesn’t save when Yoast is active has been fixed for the next release.
Thanks for the heads up here. What’s the timing for the next release?
Hi @itstimetx,
The beta testing phase has begun already. Usually, at this stage of development, it takes 1 or maximum 2 weeks to get the new release.
Please consider this as my personal experience and speculation and not an official statement.
Thank you.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.