v2.0.3 | Fixed migration issue

Thanks for the PR luceos ! Just got home so I tagged v2.0.3 with your changes merged! This would fix the migration issue users have 🙂

CyberGene What will happen if I just remove this extension and not use it anymore. Is any adverse change in Google results expected?

Good question! I don't think it will really affect your ranking, but Google or another search engine might index your site differently. Also, the extension does not only help indexing (providing the necesery tags and tell the engine what page type is a discussion, a user page or a tag page), it also adds the necesery description for that page when people share a page on social media. For example, if you share a forum post on Facebook or Twitter and don't have the extension installed, they'll see the general forum image, title and description (so the embed is just about the forum).

With this extension installed, it will personalize the page embed on the platform with the actual discussion title, a short description and even a custom image if one exists for the page. So it really depends if that's really important to you.

On the left site is an example how a discussion will be shown on social media without extension, on the right side with info.

CyberGene So, apparently my forum is broken now. I’d appreciate it if you can fix this as quickly as possible. I see the same error has already been reported and as you can see there’s a pretty straightforward explanation in StackOverflow. Instead of waiting for a reply from the other guy who reported it, you could have fixed it already… Guys, please be more proactive in future, especially after major reworks of extensions.

Don't get me wrong, it was just such an update that it was a scary one for me as well since I know many forums rely on it (also, I had to update three extensions at the same time to make sure they kept compatible with eachother). I tested many situations, but this MySQL error wasn't appearing on production forums I tested it on before releasing. When the user reported that MySQL error message, it was in the screenshots which I didn't notice, I was focussed on the provided code-block with the Base table or view not found error message 👀

Hope you'll still like the extension though 🙂

    I disabled, purged and removed this extension yesterday after I was having the migration issues I reported. I have just re-installed the extension and it's reported as 2.0.3 already but I still see the old interface and don't see the new meta UI. Tried update/migrate but it says no updates available and the migrate doesn't do anything. Somehow the failed migration from yesterday is causing the extension to just keep using the old interface and the new functions won't appear.

    How can I forcefully reinstall this extension. I can start from scratch, I don't care.

    P.S. Ahh, never mind, the new meta editor is per-discussion, just opened it. OK, so everything works now, thank you for this new version of the extension 🙂

      Hey meihuak , have you tried running composer require v17development/flarum-seo ^2 ?

      CyberGene P.S. Ahh, never mind, the new meta editor is per-discussion, just opened it. OK, so everything works now, thank you for this new version of the extension 🙂

      Awesome, glad you found out! If you have any feedback, make sure to let us know 😃

        17 days later

        JasperVriends

        v2.0.3

        An error occurred while trying to load this page.

        in the server log, there is only one error "[2024-11-05 03:18:12] flarum.ERROR: Error: Call to a member function getDisplayNameAttribute() on null in /***vendor/v17development/flarum-seo/src/Page/DiscussionBestAnswerPage.php:153"

          Thanks for that feedback clarkwinkelmann ! I noticed that there was a PR regarding this issue as well, so I have asked him if it's possible to check and implement your suggestions v17development/flarum-seo100 . I'll wait a short while to see if he is able to update the code, if not then I'll implement the fix! 🙂

            Any demo available?

            6 days later

            I've found that very large discussions (around 71k posts) fail to load (timeout) and trying to access them causes database slowdown. The problem goes away when I disable the SEO extension. This wasn't an issue in version 1.x.


            Update: The problems disappear when I turn off the Crawl all posts option. However, I've always had this option enabled, including in 1.x, where it worked fine.

              JasperVriends It would be great if there was an additional feature to edit the homepage title

                Spez the homepage title is the name of your forum, you can always edit that and use the linguist extension to edit where you want your actual forum name to be?

                • Spez replied to this.

                  JasperVriends

                  May I ask when will you repair this issue? 🙂
                  there are about 1700 discussions were broken in google index.

                  wylzn Indeed, I can change the home title by modifying the website name. However, the title of a discussion always includes the website name at the end. For example, if I set the website name as 'flarum.org - source code free forum', and the title of a discussion is 'FriendsOfFlarum upload, the intelligent file attachment extension', the discussion title would be:
                  <title>FriendsOfFlarum upload, the intelligent file attachment extension - flarum.org - source free forum</title>. It's very long. Currently, I am solving this by using an extension that removes the website name from the discussion title. Now, the discussion title is simply:
                  <title>FriendsOfFlarum upload, the intelligent file attachment extension</title>. But I think the best title format would still be:
                  <title>FriendsOfFlarum upload, the intelligent file attachment extension - flarum.org</title>.
                  I have used WordPress and XenForo, and I think customizing the home page title is a basic feature in most SEO plugins.

                  11 days later
                  19 days later

                  Released v2.0.4 - Fixing bugs


                  @meihuak This update resolves your issue! 🙂