This plugin is inserting outdated URL’s into the page, such as this one:
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 283.5 19.6" preserveAspectRatio="none">
w3 website now uses HTTPS and the developers of Elementor need to update their coding to use HTTPS and not HTTP. This is also creating errors in page speed tests.
You can submit a Bug Report on Github at https://github.com/elementor/elementor/issues/new/choose which gives you the opportunity to follow the discussion about the bug. You can learn more about how to submit requests at https://github.com/elementor/elementor/blob/master/.github/CONTRIBUTING.md
It is not a bug, it is a required update to ensure coding is current. So, no offence, but is there an issue with developers taking this information from here and putting it to their list of things to do for updates that it somehow needs to be posted at Github?
Bug reports and/or development changes of any sort are only taken on Github, yes.
I did it anyway.
Boy, GitHub is a nightmare to navigate to find any of my past posts. Certainly not user friendly. It really needs a good dashboard.
It’s definitely not for the faint-of-heart, LOL. This might help though. https://help.github.com/en/articles/about-your-personal-dashboard
I wonder how and where you get the idea that this gets inserted by Elementor?
Can you share the url where you see this and share how exactly you identify this as coming from Elementor please?
You might be right, but I never encountered this so I wonder where this is coming from?
After all W3.org is an overall platform that develops protocols and guidelines that ensure long-term growth for the Web, so not Elementor?
I think the url is wrong because of W3 itself
and there it still says:
http://www.w3.org/2000/svg is an XML namespace, first defined in the Scalable Vector Graphics (SVG) 1.0 Specification and subsequently added to by SVG 1.1, SVG 1.2 and SVG 2. The SVG namespace is mutable; names may be added over time by the W3C SVG Working Group by publication in W3C Technical Reports.
The latest version of the SVG specification can be found http://www.w3.org/TR/SVG.
For more information about SVG, please refer to the W3C SVG overview. For more information about XML, please refer to The Extensible Markup Language (XML) 1.0 specification. For more information about XML namespaces, please refer to the Namespaces in XML specification.
Last modified: $Date: 2016/03/18 23:37:07 $
So that old url is on W3 and not Elementor right? W3 itself as the owner is responsible to change that message.
I have 50+ site running on Elementor and non of them gives me errors in speed tests eather about this, so I really wonder where you see this?
The url is actually a name declaring the specific “namespace” belonging to SVG, it’s about document/markup & interpretation of the svg tag and it’s inner contents (children) and has nothing to do with http or https.
In fact, changing the namespace to be https would not be backwards compatible and cause a lot more problems, much like adding a letter to your name and then trying to find you in an older phone directory, the end result would not be promising.
I found a crash course on namespaces here: https://developer.mozilla.org/en-US/docs/Web/SVG/Namespaces_Crash_Course
Even though the “name” is an actual url as humans see it, the browser doesn’t look at it like that (URI schema) and you won’t be judged by the SEO gods accordingly.
In other words, just ignore it, this is a very normal and common declaration defined back in the year 2000.
The example I gave is located in the source code of the page, when I deactivate Elementor, it disappears, so Elementor was inserting it.
As to who is responsible for the URL, Elementor or W3? – essentially both. W3 is responsible to ensure their side is changed and Elementor’s side is changing their coding that inserts it.
Thanks for the input. The concern was SEO / page speed.
@mwarbinek it has nothing to do with Elementor, WordPress, SEO or page speed.
You’re confusing a “name” (namespace declaration) with the function of a url, even more so trying to apply logic that doesn’t fit for the purpose of an xmlns value. Your brain is seeing a url between those quotes but it really isn’t, and what matters is really the attribute key before the = sign telling us how it’s value is to be interpreted.
Not. The. Same. Thing. Let. It. Go.
@mwarbinek I re-read your response and it seems you understand this by now so sorry for beating a dead horse but your reply to @logologics is what threw me off because it suggests responsibility for the “correct” protocol when it’s a moot issue.
However, I did some tests and found when using svg in WordPress, specifically within Elementor, I couldn’t reproduce your experience.
1) In Elementor, adding an “image” element and then choosing an uploaded svg file from my WordPress media library it renders both on the back and the front end as an img tag with the svg url path in the img’s src attribute and no where does the xmlns attribute come into play.
2) I then tried the “html” element, pasting in between basic svg tags my path but intentionally leaving out any other attributes except for width=”100%” and height=”100%” and verified both back and front end it renders without the xmlns attribute.
3) I then tried with a “text” element, pasting my svg code into the text editor and making sure NOT to click back to the visual tab of the editor as that executes a WordPress filter and removes all of the code per WordPress specification of valid tinymce elements, and it too renders just fine both back and front without the xmlns attribute.
4) I then tried pasting the svg code into a heading element because I know it also renders html but without the tinymce filters (like that of the text element) and it too renders both back and front end without adding the xmlns attribute.
5) My last test was without Elementor and just using the WordPress page editor, same as the text element in test vector #2, I pasted raw svg code into the text editor (legacy editor)/code editor (gutenberg editor) again being careful not to switch back to visual version of the editor and it also renders without the xmlns attribute on the front end.
!! I should note that I did not try the object method of embedding an svg. !!
This leaves me wondering how you are including svg through Elementor? Is it possible another plugin or a theme is adding this?
p.s. I tested w/ PHP 7.2, WordPress 5.1.1, TwentyNineteen theme and only Elementor 2.5.13 activated. (all current as of this post)
Maybe with some more input we can get to the bottom of these “extra” attributes being added.
- The topic ‘Plugin Update Needed to Correct URL requests (Elementor)’ is closed to new replies.