Jump to content


Photo
- - - - -
Resolved

Custom Css Not Updating And Css Parse Error

css parse error bugs

This topic has been archived. This means that you cannot reply to this topic.
5 replies to this topic

#1 robjonathanwilliams

robjonathanwilliams

    Newbie

  • Members
  • 5 posts

Posted 28 October 2012 - 11:15 AM

Hi,

It's happened AGAIN, Pagelines brings out an update and it buggers something up which I now have to spend hours fixing, I'm honestly sick and tired of this.

I've just updated to 2.3.4 and am now getting the error: parse error: failed at `#respond input[type=\"text\"], .wp-comments .wp-comments-pad > #respond textarea { ` line: 1040

It happened when I simply tried to change one value in one line of css.

The problem is, the custom css will NOT update when I change it. It saves, but when I inspect the webpage it hasn't changed anything.

I'm certainly not a pro programmer or anything, but I can't understand why something that worked PERFECTLY is now giving these problems. -And I simply copied these values from Chrome Inspector where they were working fine as well.

Is there a way to downgrade back to 2.3.3?



**I URGENTLY need to get this fixed as I'm already way behind schedule.


Thanks,

Rob



Site is still under development but here's the url: ultimatemasteringformula.com

#2 Danny

Danny

    Is Awesome!

  • Moderators
  • 17533 posts

Posted 28 October 2012 - 11:35 AM

Hi,

If you receive a Parse Error, this means that you have an error in your custom CSS. LESS CSS, is not as forgiving with errors like the standard CSS. Therefore, please review your custom CSS for any errors such as a missing:

{ } ; :

Once you have resolved your incorrect CSS, save your settings and the Parse error will be resolved.

Also, in future, please add any custom code to our paste service -

Please Login or Register to see this Hidden Content



I have removed your code so the post is more readable.

#3 Simon_P

Simon_P

    Messer

  • Administrators



  • 8388607 posts

Posted 28 October 2012 - 12:10 PM

Thanks for searching before posting, just for you I'll repeat myself for the 3rd time.
All options should be filtered by wp kses before saving into the database but we whitelisted the CSS. Drawback was users could now enter HTML Javascript php in fact anything into the CSS box.. The last week or so we were plagued by users adding script tags into the CSS box and wp-admin would not load. I was getting daily emails asking for a fix so I enable the filter again.
Of course our testers didn't pick up nor did I that kses 'escapes' quotes and that chokes the compiler. So if the custom CSS is just that, CSS, then add it to the customise plugins css file where it belongs.

#4 robjonathanwilliams

robjonathanwilliams

    Newbie

  • Members
  • 5 posts

Posted 28 October 2012 - 01:10 PM

Thanks, I apologize, I did search and read the other posts but didn't really understand what that meant -or how to fix it.

I've installed the customize plugin and moved all my code to there and now it's working again.

#5 Danny

Danny

    Is Awesome!

  • Moderators
  • 17533 posts

Posted 28 October 2012 - 01:12 PM

The topic was marked as resolved.

#6 Simon_P

Simon_P

    Messer

  • Administrators



  • 8388607 posts

Posted 28 October 2012 - 05:03 PM

Change line 489 of class.render.css.php to this:

Please Login or Register to see this Hidden Content

And its fixed.