This thread is over two years old and may be outdated. Please create a new thread if you need help, or email us if you have an active Premium license.

Element Styles and Links Validation Errors

Open 16 replies premiumthemetheme-vantage
Ryan
10 years ago · Last reply by Andrew Misplon 10 years ago

Please refer to the link to see the markup errors. I can’t seem to figure out how or where to correct these issues.

Element style not allowed as child of element div in this context.

Element style is missing required attribute scoped.

Element link is missing required attribute property.

http://validator.w3.org/check?uri=http%3A%2F%2Fwww.comm-works.com%2Flimitless%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

Much appreciated.

URL: http://validator.w3.org/check?uri=http%3A%2F%2Fwww.comm-works.com%2Flimitless%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

This is our free support forum. Replies can take several days.

Need fast email support? Get SiteOrigin Premium

Replies

16
  1. Magus Staff 10 years, 10 months ago

    Hi Ryan

    The Style tags in your page at the line locations mentioned are in the wrong location on the page. Style tags when used like on your page should be in the head, before the opening body tag. The error is being shown because the style is not part of a div tag like this

    <div style="....

    The ones on your page are being written as

    <div><style....

    Could you tell us how you styled these call to action boxes. Was it done in the pagebuilder layout attributes or by using another method

    Magus

  2. Ryan 10 years, 10 months ago

    Hi Magus –

    I used pagebuilder widgets Call to Action (PB) and Button (PB) and simply selected the styles from the available list. I have not used any other method of styling.

    Yes, I did notice that they (styles tags) were not in the head, but I’m not sure how they got where they are or how to correct it. The style tags automatically go to the bottom of the page.

    Thanks.

  3. Magus Staff 10 years, 10 months ago

    Could you please verify that you are running the latest version of Vantage and the latest version of PageBuilder.

    If you are then please try removing one of the call to action buttons, saving the page and then recreating it.

    Then we can see if it continues to write the style information outside of the div tag.

    Thanks

    Magus

  4. Ryan 10 years, 10 months ago

    Vantage Version 2.4.2
    Page Builder Version 2.1

    I believe these are the latest.

    I removed 2 call to actions and 1 button, saved the page and then added them back again.

    still getting errors on these lines:

    line 376

    </div><style type="text/css" media="all">.origin-widget.origin-widget-call-to-action-simple-clean{zoom:1;padding:2em;position:relative;-webkit-border-radius:0px;-moz-border-radius:0px;border-radius:0px;background:#FCFCFC;-webkit-box-shadow:0 1px 2px rgba(0,0,0,0.1);-moz-box-shadow:0 1px 2px rgba(0,0,0,0.1);box-shadow:0 1px 2px rgba(0,0,0,0.1);border:1px solid #D0D0D0}.origin-widget.origin-widget-call-to-action-simple-clean:before{content:'';display:block}.origin-widget.origin-widget-call-to-action-simple-clean:after{content:'';display:table;clear:both}.origin-widget.origin-widget-call-to-action-simple-clean .title{line-height:1.6em;margin:0;color:#333333;font-weight:auto}.origin-widget.origin-widget-call-to-action-simple-clean .subtitle{line-height:1.25em;margin:0;color:#555555;font-weight:auto}.origin-widget.origin-widget-call-to-action-simple-clean .origin-widget-button{position:absolute;display:block;top:50%;right:2em;margin-top:-22px}@media (max-width:680px){.origin-widget.origin-widget-call-to-action-simple-clean .origin-widget-button{position:static;margin-top:2em}.origin-widget.origin-widget-call-to-action-simple-clean .origin-widget-button a{display:block}}</style><div class="so-panel widget widget_origin_call-to-action panel-last-child" id="panel-2277-1-0-1"><div class="origin-widget origin-widget-call-to-action origin-widget-call-to-action-simple-clean"><h2 class="title">Why Choose Comm-Works?</h2>

    line 378

    <style type="text/css" media="all">.origin-widget.origin-widget-button-vantage_flat-black a{display:inline-block;padding:11px 45px 10px 45px;-webkit-border-radius:4px;-moz-border-radius:4px;border-radius:4px;color:#EFF0F4;font-size:1em;font-family:inherit;font-weight:500;text-decoration:none;text-shadow:0 1px 0 #1A1B1E;text-align:center;border-bottom:2px solid #1E1F22;background:#2f3033;background:-webkit-gradient(linear,left bottom,left top,color-stop(0,#2E2F32),color-stop(1,#303134));background:-ms-linear-gradient(bottom,#2E2F32,#303134);background:-moz-linear-gradient(center bottom,#2E2F32 0%,#303134 100%);background:-o-linear-gradient(#303134,#2E2F32)}.origin-widget.origin-widget-button-vantage_flat-black a:hover{background:#333437;background:-webkit-gradient(linear,left bottom,left top,color-stop(0,#2B2C2F),color-stop(1,#333437));background:-ms-linear-gradient(bottom,#2B2C2F,#333437);background:-moz-linear-gradient(center bottom,#2B2C2F 0%,#333437 100%);background:-o-linear-gradient(#333437,#2B2C2F)}.origin-widget.origin-widget-button-vantage_flat-black a:active{background:#292A2D;background:-webkit-gradient(linear,left bottom,left top,color-stop(0,#292A2D),color-stop(1,#2f3033));background:-ms-linear-gradient(bottom,#292A2D,#2f3033);background:-moz-linear-gradient(center bottom,#292A2D 0%,#2f3033 100%);background:-o-linear-gradient(#2f3033,#292A2D);-webkit-box-shadow:none;-moz-box-shadow:none;box-shadow:none;padding-top:12px;padding-bottom:9px}.origin-widget.origin-widget-button-vantage_flat-black.align-left{text-align:left}.origin-widget.origin-widget-button-vantage_flat-black.align-right{text-align:right}.origin-widget.origin-widget-button-vantage_flat-black.align-center{text-align:center}.origin-widget.origin-widget-button-vantage_flat-black.align-justify a{display:block}</style><div class="origin-widget origin-widget-button origin-widget-button-vantage_flat-black align-none"><a href="http://www.comm-works.com/limitless/about/why-comm-works/" >

    line 520

    </div></div><div class="panel-grid-cell" id="pgc-2277-3-2" ><style type="text/css" media="all">.origin-widget.origin-widget-button-vantage_flat-violet a{display:inline-block;padding:11px 45px 10px 45px;-webkit-border-radius:4px;-moz-border-radius:4px;border-radius:4px;color:#FFEAFF;font-size:1em;font-family:inherit;font-weight:500;text-decoration:none;text-shadow:0 1px 0 #540096;text-align:center;border-bottom:2px solid #5A009B;background:#7113b1;background:-webkit-gradient(linear,left bottom,left top,color-stop(0,#7011B0),color-stop(1,#7215B2));background:-ms-linear-gradient(bottom,#7011B0,#7215B2);background:-moz-linear-gradient(center bottom,#7011B0 0%,#7215B2 100%);background:-o-linear-gradient(#7215B2,#7011B0)}.origin-widget.origin-widget-button-vantage_flat-violet a:hover{background:#771BB7;background:-webkit-gradient(linear,left bottom,left top,color-stop(0,#6B09AB),color-stop(1,#771BB7));background:-ms-linear-gradient(bottom,#6B09AB,#771BB7);background:-moz-linear-gradient(center bottom,#6B09AB 0%,#771BB7 100%);background:-o-linear-gradient(#771BB7,#6B09AB)}.origin-widget.origin-widget-button-vantage_flat-violet a:active{background:#6803A9;background:-webkit-gradient(linear,left bottom,left top,color-stop(0,#6803A9),color-stop(1,#7113b1));background:-ms-linear-gradient(bottom,#6803A9,#7113b1);background:-moz-linear-gradient(center bottom,#6803A9 0%,#7113b1 100%);background:-o-linear-gradient(#7113b1,#6803A9);-webkit-box-shadow:none;-moz-box-shadow:none;box-shadow:none;padding-top:12px;padding-bottom:9px}.origin-widget.origin-widget-button-vantage_flat-violet.align-left{text-align:left}.origin-widget.origin-widget-button-vantage_flat-violet.align-right{text-align:right}.origin-widget.origin-widget-button-vantage_flat-violet.align-center{text-align:center}.origin-widget.origin-widget-button-vantage_flat-violet.align-justify a{display:block}</style><div class="so-panel widget widget_origin_button panel-first-child panel-last-child" id="panel-2277-3-2-0"><div class="origin-widget origin-widget-button origin-widget-button-vantage_flat-violet align-center"><a href="http://www.comm-works.com/limitless/subscribe/" >

    lines 631,632,633

    <a href="#" id="scroll-to-top" title="Back To Top"><span class="vantage-icon-arrow-up"></span></a><link rel='stylesheet' id='metaslider-flex-slider-css' href='http://www.comm-works.com/limitless/wp-content/plugins/ml-slider/assets/sliders/flexslider/flexslider.css?ver=3.3.2' type='text/css' media='all' />
<link rel='stylesheet' id='metaslider-public-css' href='http://www.comm-works.com/limitless/wp-content/plugins/ml-slider/assets/metaslider/public.css?ver=3.3.2' type='text/css' media='all' />
<link rel='stylesheet' id='metaslider-pro-public-css' href='http://www.comm-works.com/limitless/wp-content/plugins/ml-slider-pro/assets/public.css?ver=2.6.2' type='text/css' media='all' />
  5. Magus Staff 10 years, 10 months ago

    Hi Ryan

    Tested this on my site and the divs generated correctly. It may be a plugin conflict.

    Please try disabling all non SiteOrigin plugins and then test the page again. If it does not generate errors then enable the plugins one at a time, testing at each step, until the error reappears. This should help us narrow down the cause.

    Let us know how you get on

    Magus

  6. Ryan 10 years, 10 months ago

    disabling all plugins still left me with 3 errors in those specific widgets (call to action and button.)
    Disabling the meta slider removes 3 errors from the meta slider but I really need to have that on and working.

    6 total errors – 3 errors caused by Meta Slider and 3 errors caused by PB widgets.

  7. Ryan 10 years, 10 months ago

    If I deactivate Page Builder and Meta Slider – then it passes. But there is no content left on the page. :)

  8. Magus Staff 10 years, 10 months ago

    Hi Ryan

    I have done a bit of digging through my site and discovered why this is happening.

    Please go to Settings->PageBuilder and under widgets please disable the option Legacy Bundled Widgets.

    Then remove the existing widgets on the page and replace them with the ones marked as SiteOrigin Call-to-Action and SiteOrigin Button.

    This should remove all the errors relating to those items.

    I will keep looking for a solution to the metaslider error.

    Hope this helps

    Magus

  9. Ryan 10 years, 10 months ago

    I do not see an option for a SiteOrigin Call-to-Action widget.

  10. Magus Staff 10 years, 10 months ago

    Hi Ryan

    In that case please download and install this plugin.

    https://wordpress.org/plugins/so-widgets-bundle/

    These are advanced versions of the original bundled widgets which are causing your validation errors.

    The metaslider errors can be fixed by disabling the home page slider and adding it into a pagebuilder row at the top of the page. This can then be styled to remove the top margin and stretch the whole width with some custom CSS.

    Hope this helps

    Magus

  11. Ryan 10 years, 10 months ago

    ok I had the widget budget, had to turn on the Call-to-Action feature.

    I followed these instructions:
    Please go to Settings->PageBuilder and under widgets please disable the option Legacy Bundled Widgets.
    Then remove the existing widgets on the page and replace them with the ones marked as SiteOrigin Call-to-Action and SiteOrigin Button.

    still get widgets errors.

    I tried this and it messed up the site:
    The metaslider errors can be fixed by disabling the home page slider and adding it into a pagebuilder row at the top of the page. This can then be styled to remove the top margin and stretch the whole width with some custom CSS.

    I tried the new row and deleted it, but won’t go away now! please help.

  12. Ryan 10 years, 10 months ago

    Ok cleared cache its okay for now, I will return to this issue tomorrow. keep my thread open. Thanks for your assistance.

  13. Ryan 10 years, 10 months ago

    Please note: after changing to the Site Origin widgets I have 7 errors,

    http://validator.w3.org/check?uri=http%3A%2F%2Fwww.comm-works.com%2Flimitless%2F&charset=%28detect+automatically%29&doctype=Inline&group=0

  14. Andrew Misplon Staff 10 years, 10 months ago

    Hey everyone

    Error 1, 2 & 3: Meta Slider plugin
    Error 4,5,6,7,8: SiteOrigin Widgets Bundle

    I believe the validator is looking for property=”stylesheet” to be added.

    Thanks for reporting. I’ve marked this as a bug report.

  15. Ryan 10 years, 10 months ago

    Hi Andrew –

    Does a bug report mean that there is no fix yet?

  16. Andrew Misplon Staff 10 years, 10 months ago

    I believe this is the first time this particular validator warning has been raised. I logged the report this afternoon, so unfortunately no fix yet.

Replies on this thread are closed.

Please create a new thread if you have a question, or purchase a SiteOrigin Premium license if you need one-on-one email support.

Have a different question or issue?

Start New Thread