Opu JasperVriends thanks for this great extenstion. Today I have tested some discussions with google schema markup validator and noticed that the meta description is always coming from the forum description, not from the main post. Is it happening to only me? https://www.google.com/search?prvw=AHHjJUPAnRLmJWNGNTTqmAk-l0P8HX8Z4w&q=previewid%3A47368f17-1006-4c8e-9481-c2c6b6e06820&useragent=Mozilla%2F5.0+%28Linux%3B+Android+7.1.1%3B+Nexus+6+Build%2FN6F27M%29+AppleWebKit%2F537.36+%28KHTML%2C+like+Gecko%29+Chrome%2F66.0.3359.106+Mobile+Safari%2F537.36&filter=0&gws_rd=cr&newwindow=1&igu=1
Opu And another thing, can we have a slug customization feature, please? Ex: example.com/d/123-slug to example.com/discussion/123/slug similar to stackoverflow's permalink.
luceos Opu this is not something this extension manages, but what Flarum itself decides on. There are no plans to allow modification of the URL structure, but it should be possible using an extension (which doesn't exist yet).
tankerkiller125 Alshain In regards to the URLs your sharing at the top of your post are you finding those in a search engine results? Or are those just links that your creating/finding inside the software itself?
JasperVriends Alshain Hi Alshain, thanks for the feedback! About the meta tags, can you create a issue on GitHub for that? Then I won't forget to add them in an update. https://github.com/v17development/flarum-seo/issues I'm wondering what's wrong with the ?nearURL- tag? How would you change the title and description of the page as the discussion is the same? The same for the /all?page=1 page
tankerkiller125 JasperVriends This is something I would have thought would have gotten caught by the conical URL, but apparently not.
therealsujitk JasperVriends The Post Best Answer extension has been marked incompatible. Could you please change it to the Friends Of Flarum Version.
tankerkiller125 therealsujitk The link needs updating in the original post, but it appears to already work with the FoF version.
JasperVriends tankerkiller125 Looking at this line it appears to check if the extension exists before executing: https://github.com/v17development/flarum-seo/blob/master/src/Managers/QADiscussion.php#L40 I do not know if the plugin slug of Best Answer has been changed. It may be fof-best-answer now instead of wiwatsrt-best-answer. Does someone know that?
JasperVriends tankerkiller125 Then I'll need to add an or to the if statement so it's still compatiable for the old plugin-version. Is someone able to add an if statement to the code so it will also work with the new plugin/slug? Then I'll merge it to master if someone opens an PR
luceos JasperVriends Then I'll need to add an or to the if statement so it's still compatiable for the old plugin-version. If you release a new version of this extension, it's perfectly okay to drop support for extensions that are no longer maintained..
[deleted] luceos I agree with this. The previous incarnation of best answer was broken before being brought into the FoF namespace, so there seems to be little point in supporting what is now considered legacy. Perhaps make a note in the upgrade ?
luceos Easier would be to add fof/best-answer under suggests and the other extension under conflict. See https://getcomposer.org/doc/04-schema.md#conflict for conflict and the full composer schema. These changes only apply to the version tagged with this information, which makes it incredibly powerful to abandon a dependency you previously used.
amanijoseph87 Hi, I have been using this extension for almost 2 years but I don't know why every time I test this with structured data i have a lot of errors in headings have this (String length of headline must be in range [0, 110]) in the logo I have this (there is a link with image but I have this error anyway) A value for the url field is required. I have this one too dateModified The dateModified field is recommended. Please provide a value if available. mainEntityOfPage The mainEntityOfPage field is recommended. Please provide a value if available. Is there a solution for this..?
