I'm setting this up with a new Flarum beta 11 installation. Just so everyone knows, there are oops errors when trying to save certain things within the health check. But, I think it is due to this already known saving issue which was discovered when saving custom CSS: flarum/core1946

I'm going to assume that any extension which saves things like the Custom CSS saves things will have this problem until this bug is fixed.

I could be wrong but I'm basing this on the fact that my php error log gives me the same error whether I try to save my Custom CSS or save this extension's settings.

    FBI I did your two changes in the PageListener.php of the extension and cleared the cache, but still Facebook debugger shows:

    Inferred Property: The 'og:image' property should be explicitly provided, even if a value can be inferred from other tags.

    Missing Properties: The following required properties are missing: og:image, fb:app_id

    @JasperVriends, could you please give us an option in the extension to add the fb:app_id also so we can remove this second error too?

    I also can't see the image in other social networks. I am not using images from imgur like you but directly uploading and embedding them via the Uploads extension. So will this patch of yours work for those images too?

    tankerkiller125 I was able to save the settings and get through the review / checkup after updating to beta 11.1. But, if I remember correctly it was a little buggy. As in, at one point it didn't seem like the review confirmation saved, but then I refreshed and it was saved. So the beta 11.1 update helped for me, but this extension could still need some tweaking.

    15 days later

    @JasperVriends No doubt the plugins works great. But I don't know if someone noticed or not related to the H1 tag.
    Isn't its good to have H1 tag instead of H2 to the Discussion Title on the single discussion page?
    And I don't to having the H1 tag to the logo is good?

    Update 1.1

    There is the update a lot of people were asking for. This update supports images in posts as page image. Works only if the first post has an image and it's big enough for the social media. When there is no post image, the default forum image will be used (set up in the SEO settings). When that's not available, the logo will be used. If you have no forum logo, the favicon will be used as a last resort.

    This update also contains some code cleanups, bug fixes and small changes. If you have any feedback, please let it know!

    Feedback? Let it KNOW! Please...

    Many people are discussing this SEO extension on different places and in different languages that I don't understand. It results into the situation that people don't let their feedback know in the GitHub repository or even in this discussion on Flarum. Please, if you have feedback, complains or change requests, let it know so we can do something with it!

    How to update?

    To update, run:

    composer update v17development/flarum-seo

    To install, run:

    composer require v17development/flarum-seo

    Then check in the admin dashboard if version 1.1 is installed.

    Changelog:

    • This update requires Flarum beta 11 or higher
    • Multiple bug fixes
    • Code cleanup & logic changes
    • Added logo to Organization Json LD
    • Merged PR v17development/flarum-seo24 of @Os555

      FBI Sorry, there were some changes made in beta 10 which I also changed in the extension to use less resources. https://flarum.org/docs/extend/update-b10.html

      It's about the following change in beta 10:

      The formatContent() method of Flarum\Post\CommentPost can now be called without an HTTP request instance, e.g. when rendering a post in an email template.

      You can revert my changes in the extension. Then you need to add $this->parent->getServerRequest() again on multiple places in the code.


      010101 tankerkiller125 Also, this update should fix the saving problems at the dashboard, are you able to test this?

        15 days later

        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

        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.

          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).

          11 days later

          JasperVriends

          I want to write a few shortcomings I have seen.

          https://discuss.flarum.org/all?page=1

          https://discuss.flarum.org/all?page=25

          https://discuss.flarum.org/all?page=50

          All of the above links have the same title and the same description. We need to separate the passes in the page parameter.

          Likewise near tag.

          https://sorhadi.net/d/48498-fakulte-ile-yuksekokul-arasindaki-fark-nedir?near=5

          https://sorhadi.net/d/48498-fakulte-ile-yuksekokul-arasindaki-fark-nedir?near=

          Https://sorhadi.net/d/48498-fakulte-ile-yuksekokul-arasindaki-fark-nedir

          https://sorhadi.net/d/48498-fakulte-ile-yuksekokul-arasindaki-fark-nedir/5

          All of them have the same title and the same description.

          I blocked the tag near robots.txt.

          User-agent: *
          Allow: /
          Disallow: /u/*
          Disallow: /d/*?near

          Sitemap: https://sorhadi.net/sitemap.xml

          Apart from these,

          <meta property = "og: url" content = "https://sorhadi.net">
          <meta property = "og: type" content = "website">

          meta tags are also missing.

          I would be glad if you can fix them too 🙂