- This topic has 2 replies, 2 voices, and was last updated 7 years, 10 months ago by Theme Horse Support Team.
-
AuthorPosts
-
January 9, 2017 at 10:26 am #49155MichaelParticipant
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.
January 9, 2017 at 10:59 am #49159MichaelParticipant87 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?
January 9, 2017 at 11:50 am #49161Theme Horse Support TeamKeymasterHi 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!
-
AuthorPosts
- You must be logged in to reply to this topic.