- πΊπΈUnited States nicholas.alipaz
This still seems to be an issue in 3.0.x branch.
Observing the UI for creating a schema using the "WebPage" submodule for any given content entity, I am looking for the "name" and "url" properties to exist at the top level (same level as "description", which theoretically should be existing through the inheritance of the "Thing" schema). Instead, these properties do not appear to exist, and only exist within subschema for "Author" and "Publisher".
According to the schema org page for WebPage, these properties should exist at the top level.
Given what I perceive to be a fundamental requirement for many web page schemas, I have to ask if I am missing something, or if this is this a bug in the schema inheritance process, or if the schema content I am being provided by my internal SEO team is wrong or can be accomplished in a different manner within the current functionality?
For reference, the structured data array I received to implement contains the "name" and "url" properties at the same level as the existing top level "description" property:
Given that "description" is already present at the top level, which I would have assumed is inherited from "Thing" (without confirming by parsing the massive schemaorg-all-http.jsonld file), I am initially gravitating towards this being a bug, but would gladly like to hear otherwise.
Active
3.0
User interface
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
This still seems to be an issue in 3.0.x branch.