RichardR
-
Posts
131 -
Joined
-
Last visited
Content Type
Forums
Gallery
Blogs
Events
Store
Downloads
Profiles
Posts posted by RichardR
-
-
-
-
-
So, been backwards and forwards to SS and they've been super helpful. I've spotted a couple of parse errors in the CSS and when I now drop it all into a CSS validator it's all good. However, issue still occurs.
If I remove all CSS, clear cache, refresh page and then try - error gone. So this still suggests my CSS is the issue but I simply can't find it.
I could do with someone casting their eye over the CSS, any takers I can DM it over?
Thanks in advance, this is driving me mad 😞
-
19 minutes ago, paul2009 said:
Why is this error appearing in my editor?
This week, Squarespace introduced a new editor 'feature' with the intention of highlighting custom CSS errors when users are editing other content. If errors are detected with Custom CSS, a red banner appears in the editor to warn users about the issue.
Squarespace have done this to try to reduce the number of problems being caused by custom code that users randomly add to their sites without knowing the harm that it can cause.
Recently many more customers reported problems with the editing interface, for example Fluid Engine, but these errors were often self-inflicted - caused by users adding snippets of Custom CSS that interfere with Squarespace. As customers rarely return to the Custom CSS panel after they've added some "magic code", this new error banner should help to highlight the issue and allow them to fix it for themselves.
However, I have seen a number of reports of the banner appearing even when the Custom CSS panel is empty, so there may be some instances of "false flags" where it appears for no good reason.
How to fix the error
If the error has appeared on your site, my advice is to remove all custom CSS and then check if the error appears. You can do this as follows:
1. Go to Design > Custom CSS
2. Save a copy of your CSS somewhere safe. A text file is ideal for this. Do not save it in Microsoft Word as this will often cause unwanted changes to the CSS.
3. When you are sure that you have a good backup of the CSS, delete all content in the Custom CSS panel.
4. Save the changes and check to ensure the panel is now empty. When empty, you should only see the label for line 1; nothing else:
5. If you have added any custom CSS to any other areas of your website using Code Injection, repeat this process for all remaining code. You may find this in Settings > Advanced > Code Injection and in the Settings panel of individual pages.
6. When you have removed all CSS, refresh your browser to reload the site (Cmd-R on Mac; Ctrl + Shift +R or Ctrl + F5 on Windows).
7. Return to the page you were editing and check for the error message...
- If the error message has gone, your CSS was the likely cause of the error. You will need to check the CSS that you backed up to find the cause of the issue. Understandably, Squarespace Customer Care cannot help you to troubleshoot your own CSS. If you had more than a few lines of Custom CSS, it may help you to pinpoint the cause of the error if you carefully re-insert short sections of your CSS until the error reappears.
- If the error message is still shown after you have removed all Custom CSS from your site then you know that your Custom CSS is not the cause of the error message. You can now confidently go back to Squarespace Customer Care to tell them that your site shows a CSS error message but you do not have any Custom CSS on the site. They can then assist you to resolve or escalate the issue.
Let me know if you have any questions.
Did this help? Please give feedback by clicking an icon below ⬇️
Thanks so much for this walkthrough Paul, I really appreciate it. I've followed it and removed all CSS from the Custom CSS part and also the small amount of code injection. Then refreshed and checked, same error with all CSS removed. I've tried to get this across to SS but they don't seem to respond to my comment about removing it all and it still showing the error. I'll keep trying of course 🙂
-
I agree, they make no secret about custom code at all. I'm still baffled by where the issue is though 🤷♂️
-
I think the other issue for me is that I can't see anything on my site not working correctly - so it's even more confusing!
-
Reported to Squarespace and had the following response. Any thoughts really welcomed as I can’t see any visible errors in the site itself, just in the back end. Even removed Custom CSS and error continues.
To provide a bit more context, we were seeing an elevated rate of custom CSS errors interfering with editing tools. To help flag this, we released the 'CSS parsing error' banner as a new editor 'feature' this week.
In this case, the 'CSS parsing error' banner is displaying due to formatting issues in the Custom CSS panel and the util.less file.
Updates to the platform can cause a site's custom code to behave differently or break. This means custom code can interfere with your site's behavior or stop working at any time, even if it previously worked or wasn't interfering.
Because of this, we can't ensure that any custom code will be compatible with the platform. To learn more, visit our guide:
https://support.squarespace.com/hc/articles/205815928 -
Hey everyone,
Did anyone get an answer to this? I'm seeing the same on all blog posts in 3 different sections of my website.
No syntax errors in the CSS at all, so I completely removed all the CSS and the same issue occurs 'Error parsing Custom CSS, verify Custom CSS is valid' . I'm guessing this is potentially a Squarespace issue, as creedon has said.
-
Perfect solution, thank you so much 😀
-
Thanks, will send you a message
-
Hi, the site isn't live as yet, is there a way fo me doing it?
-
Brine banner advice
in Customize with code
Posted · Edited by RichardR
Hey everyone,
I've started to pull together a donate page and trying to come up with better banner ideas. I like the idea of adding an image with a title and short intro text for the desktop version - see below:
https://www.probation-institute.org/donate
However, the mobile version doesn't look quite so good. I'd really welcome any advice on how to make it better on the mobile with any custom coding perhaps. Or, any other suggestions for banners would be really appreciated.
Many thanks in advance.
Richard