Custom css publishes on staging but not live

Support
#1

Hi, I’d like to pick this thread back up please:

I have made a direct copy of the site on a staging platform (same hosting so presume same php memory set up with GoDaddy). The staging site does not have this same issue, which suggests it is not a plugin conflict or memory issue.

I have tried to increase php memory anyway just in case, have added the code into wp-config file. Tried adding to htaccess as well but this caused an internal server error?

Im reluctant to update everything on the version compatibility list as it is all these constant updates that seem to cause us problems - plus the same versions work fine on the staging site and dont have these issues.

Is there anything else it could be?

Thanks

#2

Hi there,

Did you updated X or Cornerstone before you start getting the issue? If so, kindly double check if you both have X and Cornerstone updated to the latest version because you will get an incompatibility issue if you only updated one of them.

Also, it would be better putting the custom CSS in the Global CSS as what was suggested in your previous thread as the Global CSS will get higher precedence and it has a better syntax highlighting.

Kindly also make sure that there is no CSS error in the codes that you have. You can check that here: http://csslint.net/

In case you are still getting an issue, please provide us with the admin and FTP details of the staging site so that we can check it.

Thank you.

#3

Hi,

Both X and cornerstone were up to date when we started getting the issue.

As mentioned in the other thread I tried to put the css in the Global CSS but that page wont load. I’ve just tried to do this again but CSS isnt even showing under X > Theme Options now??

Cant see any major issues with the CSS.

Also as the css editor works perfectly on the staging site which is a replica of the live site, it seems something bigger is an issue.

#4

I tested your live site where you said it doesn’t work but the Global CSS works (see secure note). This shows there’s no issue with the Global CSS.

I also tested WordPreses’ built in Customizer CSS (Additional CSS) and found that when I remove all your CSS, it works. This shows that there’s something wrong with your custom CSS. I pasted it back but WordPress won’t accept it (won’t save) again. I checked your CSS in CSS lint and there are no errors but there’s lots of warnings. Maybe that’s why it won’t save.

Based on my test, this is not a theme issue. Please fix your CSS.

Thanks.

#5

Thanks, but as you have removed all the css my site now looks a mess! The client will not be happy.

How is it this css is working - and allows you to make changes - on the staging site, but not on the live site. What is the difference between them?

#6

Also, where do I find the Global CSS?

#7

Hi,

I have managed to get the css back in to the additional css customise area - it seems the issue was with the comments I had throughout the css (/* COMMENT */). Hope that helps for someone else.

The only problem I have now is I just cant find the Global CSS where you have set that gray text colour which I need to remove??

Thanks

#8

Found it! Thanks for your help.

#9

Glad you’ve sorted it out :slight_smile:

#10

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.