Error parsing Custom CSS, verify Custom CSS is valid. - someone help

Hi I got this error message saying "Error parsing Custom CSS, verify Custom CSS is valid" on my blog page editing and also events and I suppose any pages which when I want to do editing. 

What can I do ? I did not change any custom code and will definitely not touch any part of it as I think that may break the entire site and I have no developers to help me in this as I'm managing the site myself. 

Please help!

When you see this message, go back to Design > Custom CSS and look for errors in your code.

If you aren't familiar with code or have added code that you found online, I recommend that you remove it, save it somewhere safe (not on Squarespace) and save your changes. You can then check to see if this has cleared the error.

If the error persists, please contact Squarespace Customer Care directly for assistance with the platform.

Did this help? Please give feedback by clicking an icon below  ⬇️

I have went to the Custom CSS page of my own site but there are no parts that have red error messages. I was directed by them to here to seek assistance. Just find it utterly unhelpful and extremely distressing. 

I have attached here in the private youtube video the entire run through of my CSS custom code but there are no error red messages.

What other ways are there to help? SOS!!!!

On 11/22/2022 at 12:05 PM, Lim said:

I have went to the Custom CSS page of my own site but there are no parts that have red error messages. I was directed by [Squarespace Customer Care] to here to seek assistance.

I recommend that you follow the advice in this similar thread:

Did this help? Please give feedback by clicking an icon below  ⬇️

Hi , I got the similar message and the same issues and being directed here. "Error parsing Custom CSS, verify Custom CSS is valid". I am clueless how to resolve as I manintain the site on my own too

Hi Paul 

Thank you so much for all the guidance.  I will save my CSS code but I don't think I will dare to delete everything and then slowly put back, its too stressful because my site runs on the custom code. 

I have already feedback to the Squarespace customer care. I believe its issue on their side because I have not touch anything and one day the error message just pop up. I would not risk breaking my whole site because of their backend issue.

I have the same error coming up.. I assume its' an error on Squarespace's end as it seems many people are reporting the same problem of late?

I also think its Squarespace side. But the way they resolve this problem is disappointing as I feel the support is weak and they just brush us to forum to seek out solutions on our own without looking further into what may be causing the issue on their end. 

I also have this issue. It seems obvious given the proliferation of the problem that it's a backend issue so what are squarespace doing?!

I'm having this issue too. When will this error be corrected? 

15 hours ago, peterboxall said:

It seems obvious given the proliferation of the problem that it's a backend issue so what are squarespace doing?

It may appear this way, but where I have been asked to check sites with this error, all the sites had genuine code issues that required correction or removal 🙂

For the record, I am having the same problem all of a sudden, on old events that I saved a while ago.

1 minute ago, brynna said:

For the record, I am having the same problem

Have you followed the advice that I gave in this post?

Can someone help me understand why this is showing up? i've spoken to customer service twice , deleted cache but still nothing at still appears to be here.

please any help would be much appreciated

1 hour ago, Rjafadi said:

Can someone help me understand why this is showing up?

Please see this thread:

Did this help? Please give feedback by clicking an icon below  ⬇️

10 hours ago, paul2009 said:

Please see this thread:

Did this help? Please give feedback by clicking an icon below  ⬇️

Could this be the problem?

8 hours ago, Rjafadi said:

Could this be the problem?

No. Go to Design > Custom CSS and look for errors in your code.