MikeJones wouldn't this be a feature that should be part of Upload itself? It seems like the "Complete image preview template" indeed doesn't any ability to have alt/label values right now, but this could be added. Using a custom template to insert the image as markdown or bbcode would also be an option, and would give access to the alt and title attributes.

      8 days later

      Hi!

      Can I suggest that you set the meta tag for Twitter to summary_large_image instead of just summary? That way I can have a big image on the Twitter feed when linking a post.

      I made the change in the code myself, line 202 on file Listeners/PageListener.php and it works perfectly!

      ->setMetaTag('twitter:card', 'summary_large_image');

      Or maybe make it an option? It looks much better on Twitter with the large image.

      Thanks 🙂

        4 days later

        Release 1.4 - Support Flarum beta 14

        This update should make this extension compatible with Flarum Beta 14. If you find any errors, please create an issue.

        Notice: This update is only for Flarum beta 14 or higher. You cannot install this update on Flarum beta 13 or lower.

        How to update?

        To update, run:

        composer update v17development/flarum-seo

        To install, run:

        composer require v17development/flarum-seo

        Is there anyway yet to turn off the answer thing until someone actually replies to a post?

        Basically every post I have with no other replies has this error in google search console:

        Either "acceptedAnswer" or "suggestedAnswer" should be specified

          9 days later

          Trying to install in a fresh flarum installation, got this error, any ideas?

          Problem 1
          - Root composer.json requires fof/upload 0.10.0 -> satisfiable by fof/upload[0.10.0].
          - fof/upload 0.10.0 requires flarum/core >=0.1.0-beta.12 <0.1.0-beta.14 -> found flarum/core[v0.1.0-beta.12, v0.1.0-beta.13] but the package is fixed to v0.1.0-beta.14 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.

            xarly1 EDIT: removed my previous answer because I thought this was a reply to the beta 14 release thread.

            It seems like your website is in a broken state. Assuming you installed fof/upload prior to SEO, it seems like it force a downgrade back to beta 13. But the lockfile isn't up to date and Composer has issues with that.

            If it's a completely fresh install I'd recommend starting again from scratch. Otherwise you could try removing the lock file and running composer install. You will need to remove the upload extension if you want to stay on beta 14.

              Yeah gonna reinstall all and see, thanks!

              edit: it worked now, thanks 🙂

              MikeJones Basically every post I have with no other replies has this error in google search console:

              Either "acceptedAnswer" or "suggestedAnswer" should be specified

              Yes, Google do always warn me for this, I wish I had more time to answer all the questions.

                This plugin has given every post (before installing the plugin) the same meta description as the first ever post. After installing the plugin, all posts created are correct.

                How do I get posts (before installing extension) to have different meta descriptions and not all the first ever post?

                a month later

                So I noticed something weird when updating to .14 version. My website has in my region very good google search results. But before updating If I searched for the post it was there as a separate thing like it should be:

                POST TITLE - FORUM TITLE (and link to the post)
DESCRIPTION

                But now when I updateted, it just links to my forum and that's it in "description" if I could call it like that, it just says that post with similar title is on my forum...

                FORUM TITLE (and link to the forum)
POST TITLE - TAGS

                17 days later

                just to say that the extension unfortunately doesn't work with beta 15