bassangler Posted April 15, 2022 Posted April 15, 2022 I noticed the Organization schema works IF the TLD is the forums. However, that's not the case for us. Instead, IC a directory off the the TLD (i.e. https://TLD/forums). In this instance, the schema ends up like this: @type Organization @id https://www.TLD/forums/#organization mainEntityOfPage https://www.TLD/forums/ name Name of Forums url https://www.TLD/forums/ Where it should be: @type Organization @id https://www.TLD/#organization mainEntityOfPage https://www.TLD/ name Name of Website url https://www.TLD/ Is there a method to fix this? SeNioR- 1
Jim M Posted April 16, 2022 Posted April 16, 2022 This would be correct as your community is installed in your "forums" directory. Thus, the software uses that URL. To change this, it would not be advised and require a customization.
bassangler Posted April 18, 2022 Author Posted April 18, 2022 Well, no, it's not correct. The schema is wrong. You're saying it cannot be fixed? Seems like a bug then, because you should be able to edit it for instances like this. SeNioR- 1
Marc Posted April 18, 2022 Posted April 18, 2022 I'm a little confused as to what you believe to be incorrect there. Its generating what you have your software installed under. Your root URL is not our software
bassangler Posted April 18, 2022 Author Posted April 18, 2022 I get the software assumes it's installed at the root directory, hence the way the Schema is coded. But it's not installed in the root directory, so the Schema information is incorrect. The software has no provision for that use case (installed in something OTHER than the root). That is the problem. SeNioR- 1
Management Matt Posted April 18, 2022 Management Posted April 18, 2022 I understand what you mean. You're saying your site is my-site.com, and you have created a directory 'forums' and put the forums in there, so the JSON should report the site as 'my-site.com' but it's reporting 'my-site.com/forums'. I'll open an issue. SeNioR- 1
bassangler Posted April 18, 2022 Author Posted April 18, 2022 (edited) Yes, plus mainEntityOfPage, Name, and URL values (see my OP for example). Thank you! Edited April 18, 2022 by bassangler
Management Matt Posted June 9, 2022 Management Posted June 9, 2022 This should make it into the June release. SeNioR- 1
Marc Posted July 11, 2022 Posted July 11, 2022 This issue has been resolved in 4.7.0 which has recently been released. Please upgrade to that version to resolve this, and of course, let us know if you are still seeing any issues.
bassangler Posted December 3, 2022 Author Posted December 3, 2022 Yes, that fixed it. But I see the "website" type also needs the same treatment. Can that be included in the next release?
bassangler Posted December 15, 2022 Author Posted December 15, 2022 On 12/3/2022 at 9:49 AM, bassangler said: Yes, that fixed it. But I see the "website" type also needs the same treatment. Can that be included in the next release? Should I start a new thread? Wondering why this is being ignored.
Jim M Posted December 15, 2022 Posted December 15, 2022 13 hours ago, bassangler said: Should I start a new thread? Wondering why this is being ignored. Your topic has been moved to Feature & Suggestions. As this is a change in how it currently functions. While our team does not reply to every topic, we do read each and every request. bassangler 1
Management Matt Posted December 17, 2022 Management Posted December 17, 2022 I will take a look Monday. SeNioR- 1
Recommended Posts