badget

Biggest Sale! Special Offer!

Get 30% discount on all of our single themes with this coupon code: #30%SALE

Hurry up! *Limited time offer*

Major Problem styling all lost

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #49155
    Michael
    Participant

    I upgraded to the Pro version, and made a few cosmetic changes, which worked fine. Then today for some reason all my styling has gone from the site. I reverted to my free version of Portfolio. Styling works great, then I deleted the pro version, uploaded it from the zip file, previewed it, and my site loses it’s styling again.

    I copied the CSS into a validator, and it’s found several errors. Could you please help me fix this problem urgently.

    #49159
    Michael
    Participant

    87 Unknown pseudo-element or pseudo-class ::selection [selection]
    375 input[type=”text”], input[type=”email”], input[type=”search”], input[type=”password”], input[type=”tel”], input[type=”url”], input[type=”date”], input[type=”number”], input[type=”reset”], input[type=”button”], input[type=”submit”], textarea Property appearance doesn’t exist : none
    1347 .entry-title, .entry-title a Value Error : color 333 is not a color value : 333
    2465 .featured-slider #prev:before, .featured-slider #next:before attempt to find a semi-colon before the property name. add it
    2465 .featured-slider #prev:before, .featured-slider #next:before Property progid doesn’t exist : DXImageTransform
    2465 .featured-slider #prev:before, .featured-slider #next:before Parse Error DXImageTransform.Microsoft.BasicImage(rotation=1);
    2466 .featured-slider #prev:before, .featured-slider #next:before Parse Error }

    Don’t know if that helps or not?

    #49161

    Hi Michael,

    It seems that you may have customized the theme main style.css file directly rather than using custom css options. You can add your Custom CSS (styles) in Appearance -> Customize -> Additional CSS and paste your custom css code.

    So that if you activate the pro version your customized code will not lost. We always recommended not to customize the code or if you customize the code then while updating to new version or upgrading to pro version all your customized code will be lost. So better create a child theme if code customization is required.

    Also the theme CSS validation code error that you have provide above is not actual an error since the validator system is validating with the same old system and need to update to a latest version of CSS.

    Thank you!

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.