Jump to content


Photo
- - - - -

w3c validation problem: <style type="text/css" id="pagelines-custom"> not accepted

w3c validation

Best Answer Simon_P , 14 June 2013 - 06:06 PM

The facebook javascript adds a frame into the head, so it'll never validate, disable the facebook stuff.

Go to the full post


  • Please log in to reply
7 replies to this topic

#1 sgendry

sgendry

    Advanced Member

  • Members
  • 79 posts
  • Country: Country Flag

Posted 10 June 2013 - 06:32 AM

My site

Please Login or Register to see this Hidden Content

and its custom pagelines css works fine, but 

Please Login or Register to see this Hidden Content

doesn't like it.

What am I missing? Why are they not accepting the custom css?

 

Line 115, Column 45Element style not allowed as child of element body in this context. (Suppressing further errors from this subtree.)<style type="text/css" id="pagelines-custom">

Contexts in which element 

Please Login or Register to see this Hidden Content

 may be used: If the 

Please Login or Register to see this Hidden Content

 attribute is absent: where 

Please Login or Register to see this Hidden Content

 is expected. If the 

Please Login or Register to see this Hidden Content

 attribute is absent: in a 

Please Login or Register to see this Hidden Content

 element that is a child of a 

Please Login or Register to see this Hidden Content

 element. If the 

Please Login or Register to see this Hidden Content

 attribute is present: where 

Please Login or Register to see this Hidden Content

 is expected, but before any other 

Please Login or Register to see this Hidden Content

 other than 

Please Login or Register to see this Hidden Content

, and not as the child of an element whose content model is 

Please Login or Register to see this Hidden Content

. Content model for element 

Please Login or Register to see this Hidden Content

:

Please Login or Register to see this Hidden Content

.

 

 

 

Above is the main error but there are 2 more pagelines-related errors that I don't understand and therefore can't fix:

 

  1. error.png Line 122, Column 156An body start tag seen but an element of the same type was already open.
  2. Please Login or Register to see this Hidden Content

    Please Login or Register to see this Hidden Content

  3. error.png Line 122, Column 156Cannot recover after last error. Any further errors will be ignored.

    Please Login or Register to see this Hidden Content



#2 Danny

Danny

    Is Awesome!

  • Moderators
  • 15242 posts
  • LocationManchester, UK
  • Country: Country Flag

Posted 10 June 2013 - 10:12 AM

Hi,

 

You have a number of scripts/CSS links in your body class?

 

Not sure why this is happening but this isn't a PageLines issue, it is related to either a plugin you're using or custom code you have added.

 

I recommend disabling all non-PageLines plugins and see if this resolves your issue, if it doesn't remove all your custom code and see if that resolves the issue.

 

These issues are not related to PageLines but either plugins or your custom code.



#3 sgendry

sgendry

    Advanced Member

  • Members
  • 79 posts
  • Country: Country Flag

Posted 14 June 2013 - 05:49 AM

Am perplexed then.

The error persist even when I deactivate ALL my plugins and delete ALL my pagelines custom code:

 

It appears to be coming from:

<body class="home page page-id-4867 page-template page-template-page-epsilon-php logged-in admin-bar custom content-shadow static pagelines-template-theme epsilon full_width ">

 

Any idea what part of pagelines generates that code?

 

 

  1.  Line 65, Column 156An body start tag seen but an element of the same type was already open.

    Please Login or Register to see this Hidden Content

    Please Login or Register to see this Hidden Content

  2. error.png Line 65, Column 156Cannot recover after last error. Any further errors will be ignored.

    Please Login or Register to see this Hidden Content



#4 Danny

Danny

    Is Awesome!

  • Moderators
  • 15242 posts
  • LocationManchester, UK
  • Country: Country Flag

Posted 14 June 2013 - 07:41 AM

Where have you and how have you added custom code to your site?

Have you added any custom sections? 

Have you made any edits to the sections files ?

Have you made any edits to the core files?

 

Can you disable all active plugins and disable all your custom code. Then enable PageLines debug mode (PageLines > Site Options > Advanced)

 

Also I must mention that the number of scripts you have in your <head> is without doubt the most I have ever seen.



#5 sgendry

sgendry

    Advanced Member

  • Members
  • 79 posts
  • Country: Country Flag

Posted 14 June 2013 - 05:35 PM

No to all your questions

 

8 scripts are too many?

You must be referring to the code that the google mod_pagespeed is creating.

It's actually speeding up the site quite nicely.

 

Will disable everything again tonight and enable the debug mode, and kindly explain what I am looking for / should expect to find. I have never done this particular procedure before.



#6 Simon_P

Simon_P

    Messer

  • Administrators



  • 8388607 posts
  • LocationDevon
  • Framework Version:2.1.1
  • Country: Country Flag

Posted 14 June 2013 - 06:06 PM   Best Answer

The facebook javascript adds a frame into the head, so it'll never validate, disable the facebook stuff.


  • sgendry likes this

#7 Danny

Danny

    Is Awesome!

  • Moderators
  • 15242 posts
  • LocationManchester, UK
  • Country: Country Flag

Posted 14 June 2013 - 11:29 PM

No to all your questions

 

8 scripts are too many?

You must be referring to the code that the google mod_pagespeed is creating.

It's actually speeding up the site quite nicely.

 

Will disable everything again tonight and enable the debug mode, and kindly explain what I am looking for / should expect to find. I have never done this particular procedure before.

 

I counted 47 scripts when I viewed your site.



#8 sgendry

sgendry

    Advanced Member

  • Members
  • 79 posts
  • Country: Country Flag

Posted 14 June 2013 - 11:54 PM

Your feedback is most valuable.

One more thing to investigate...







Also tagged with one or more of these keywords: w3c, validation