Hey Guys. I don’t know and where to look for. I purchase a new license for X and install everything ok. I have imported the Agency - Setup Demo Content.
I have not add content yet, and Html Checker show many errors and warning?
How can I fix those errors?
Such as 11, 19 and 20
Hello Robert,
Thanks for writing in!
The errors were a result from unset variables or blank values outputted in the front end. You will need to make sure that you have set the settings in Theme Options correctly.
Please also note that the checker is experimental and it is not absolutely approved by the browser standards.
Hope this helps.
Thanks for your reply. I have been driving crazy!
It’s very frustrating to see those warnings and errors in a fresh installation without any content added at all.
So, how does a user would know if he/she is building something reliable?
xTheme should have some Checker build in so at least we can see what is going on.
What about Red Error that we don’t have access at all because was generated by WP Core?
How bad will those errors impact in SEO?
Best,
Robert
Hello Robert,
Parse error and Bad value can be eliminated by editing the page to correct it. If you can give us access to your site, we would be happy to fix it for you.
Regards.
Guys. As much I go deep in xTheme I see things that are not right!
Meanwhile, please explain how I can repair those Parse error and Bad value on my own. Also, The website is raw, and I am using only “classic” tools such as Classic Text instead Text (I have a big issue about that but not now).
website: https://www.repairhomeservice.com/sandbox/
Please open my website, view, copy and past my page code into the validator https://validator.w3.org/nu/#textarea, and help me understand where the error #15 and #16 comes from.
I see xTheme add this [style] right after a [div] and I don’t undestand for what reason!
Backend Access in notes
Hi Robert,
The error #15 and #16 are referring to the Global Block (which is your custom footer)
Please kindly consider that you are using Wordpress CMS and a Multipurpose theme like X. there is virtually no way that you can achieve 100% validation as there are many factors in place.
For example in error #10 Illegal character in query: | is not allowed. but that is how the Google load multiple fonts to reduce the request, it includes the vertical bar [ | ].
There are thousands of cases like this including the google micro-formats and snippets which will virtually make it impossible to have a 100% valid W3C code.
If you want to have a 100% valid code you need to have a small self-coded custom website. without any CMS and multipurpose themes.
Thank you for your understanding.
Got it. But what about the Footer issue? Is that something I can fix it?
Also, you said Parse error and Bad value can be eliminated by editing the page to correct it. Can you explain how can I edit those page!
Thanks,
Robert.
Hi Robert,
Sorry but, I don’t see you mentioned a footer issue on this thread, please create a new thread regarding that footer issue.
No, you can’t change those value:
CSS: word-break: break-word is not a word-break value.
You can see here, that break-word is a valid value for word-break property. And this seems to be a styling for Wordpress Block content.
Bad value https://api.w.org/ for attribute rel on element link: The string https://api.w.org/ is not a registered keyword.
https://api.w.org/ it may not a registered keyword in the validator, but that is a Wordpress URI. You can’t change that.
CSS: font-size: Parse Error.
The value that this error is referring here is a CSS calc() Function, its not an error.
Bad value //fonts.googleapis.com/css?family=Lato:400,400i,700,700i|Raleway:700,900&subset=latin,latin-ext for attribute href on element link: Illegal character in query: | is not allowed.
It’s a Google URI, you can not remove that vertical bar | in there or it will become invalid.
We are kindly asking to create a new thread regarding your footer issue, as this one is getting longer and hard to follow.
Thanks,
Hey Guys. Thank you very much for all your attention.
Things is clear now. I will create another thread for the foot issue.
Best,
Robert
You’re welcome, Robert.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.