Flarum SEO

clarkwinkelmann

Umutcan please share your MySQL/MariaDB version, it's probably relevant to this issue. And your whole php flarum info while at it.

I haven't used the extension myself but this will probably help Jasper

Denys

JasperVriends in my 3 websites don't any updates. How to fix it? I'm using php 8.1 and 8.2 🤷

JasperVriends

Denys Have you tried to explicitly use v2 in the tags, like composer require v17development/flarum-seo ^2 ?

Denys

JasperVriends no. I'm runed Flarum update and Flarum SEO update (composer update v17development/flarum-seo)

Denys

JasperVriends thank you! It's helped me for updated to last version 👍

JasperVriends

Subarist Do you only get this error in the admin panel? Can you verify that the file SeoPage/SeoBlogOverviewMeta.php exists in the v17development/flarum-blog vendor folder?

Denys Can you try composer why-not v17development/flarum-seo 2.0 and see if it returns any reason why it cannot install?

Subarist

Hi, Sirs,

The following issue only appears when using the admin login:

v17development-flarum-seo failed to initialize, check the browser console for further information.

Logs:

[2024-10-15 16:19:19] flarum.ERROR: ReflectionException: Class "V17Development\FlarumBlog\SeoPage\SeoBlogOverviewMeta" does not exist in /www/wwwroot/flarum/vendor/illuminate/container/Container.php:877
Stack trace:
#0 /www/wwwroot/flarum/vendor/illuminate/container/Container.php(877): ReflectionClass->__construct()
#1 /www/wwwroot/flarum/vendor/illuminate/container/Container.php(758): Illuminate\Container\Container->build()
#2 /www/wwwroot/flarum/vendor/illuminate/container/Container.php(694): Illuminate\Container\Container->resolve()
#3 /www/wwwroot/flarum/vendor/v17development/flarum-seo/src/Extend/SEO.php(51): Illuminate\Container\Container->make()
#4 /www/wwwroot/flarum/vendor/illuminate/container/Container.php(1265): V17Development\FlarumSeo\Extend\SEO->V17Development\FlarumSeo\Extend\{closure}()
#5 /www/wwwroot/flarum/vendor/illuminate/container/Container.php(1211): Illuminate\Container\Container->fireCallbackArray()
#6 /www/wwwroot/flarum/vendor/illuminate/container/Container.php(778): Illuminate\Container\Container->fireResolvingCallbacks()
#7 /www/wwwroot/flarum/vendor/illuminate/container/Container.php(694): Illuminate\Container\Container->resolve()
#8 /www/wwwroot/flarum/vendor/illuminate/container/Container.php(1027): Illuminate\Container\Container->make()
#9 /www/wwwroot/flarum/vendor/illuminate/container/Container.php(947): Illuminate\Container\Container->resolveClass()

Could you please advise me on how to troubleshoot this issue? Or is there any additional information I need to provide?


`Flarum core: 1.8.7
PHP version: 8.3.12
MySQL version: 8.0.37
Loaded extensions: Core, date, libxml, openssl, pcre, zlib, filter, hash, json, pcntl, random, readline, Reflection, SPL, session, standard, sockets, bz2, calendar, ctype, curl, dom, mbstring, fileinfo, ftp, gd, gettext, gmp, iconv, intl, exif, mysqlnd, PDO, Phar, posix, shmop, SimpleXML, sqlite3, sysvmsg, sysvsem, sysvshm, tokenizer, xml, xmlwriter, xsl, mysqli, pdo_mysql, pdo_sqlite, xmlreader, igbinary, msgpack, redis, swoole
+-------------------------------------------+---------+--------+
| Flarum Extensions                         |         |        |
+-------------------------------------------+---------+--------+
| ID                                        | Version | Commit |
+-------------------------------------------+---------+--------+
| flarum-markdown                           | v1.8.1  |        |
| flarum-flags                              | v1.8.1  |        |
| flarum-suspend                            | v1.8.2  |        |
| v17development-seo                        | v2.0.2  |        |
| askvortsov-rich-text                      | v2.1.7  |        |
| flarum-sticky                             | v1.8.1  |        |
| flarum-tags                               | v1.8.2  |        |
| flarum-lock                               | v1.8.1  |        |
| fof-formatting                            | 1.0.3   |        |
| afrux-forum-widgets-core                  | v0.1.7  |        |
| fof-oauth                                 | 1.6.12  |        |
| flarum-nicknames                          | v1.8.1  |        |
| fof-pages                                 | 1.0.8   |        |
| flarum-approval                           | v1.8.2  |        |
| fof-user-directory                        | 1.3.3   |        |
| clarkwinkelmann-advanced-search-highlight | 1.0.2   |        |
| v17development-blog                       | v0.8.0  |        |
| sycho-advanced-extension-categories       | v0.1.3  |        |
| wanecho-mediaembed                        | 1.0.1   |        |
| the-turk-stickiest                        | 3.0.1   |        |
| the-turk-flamoji                          | 1.0.4   |        |
| sycho-profile-cover                       | v1.3.5  |        |
| sycho-lite-youtube                        | v0.1.1  |        |
| rob006-last-post-avatar                   | 1.2.4   |        |
| pipecraft-id-slug                         | v1.1.0  |        |
| nearata-tags-color-generator              | v2.3.0  |        |
| muhammedsaidckr-gemini                    | v1.0.4  |        |
| malago-fancybox                           | 0.3.0   |        |
| justoverclock-og-meta-tag                 | 0.1.0   |        |
| justoverclock-hashtag                     | 1.0.1   |        |
| justoverclock-dontgoaway                  | 0.2.5   |        |
| justoverclock-custom-html-widget          | 0.1.4   |        |
| justoverclock-country-flags               | 1.0.0   |        |
| justoverclock-contactme                   | 0.2.3   |        |
| ianm-oauth-line                           | 0.1.4   |        |
| ianm-html-head                            | 1.2.3   |        |
| ianm-boring-avatars                       | 1.0.0   |        |
| hamcq-pangujs                             | 1.0.3   |        |
| glowingblue-redis-setup                   | 1.2.2   |        |
| gbcl-userip                               | 1.1.0   |        |
| fof-username-request                      | 1.2.4   |        |
| fof-user-bio                              | 1.4.0   |        |
| fof-upload                                | 1.5.5   |        |
| fof-socialprofile                         | 1.1.6   |        |
| fof-sitemap                               | 2.2.1   |        |
| fof-share-social                          | 1.2.0   |        |
| fof-profile-image-crop                    | 1.1.6   |        |
| fof-pretty-mail                           | 1.1.2   |        |
| fof-nightmode                             | 1.5.3   |        |
| fof-merge-discussions                     | 1.4.1   |        |
| fof-links                                 | 1.3.0   |        |
| fof-filter                                | 1.2.0   |        |
| fof-default-user-preferences              | 1.2.1   |        |
| fof-best-answer                           | 1.5.5   |        |
| fof-anti-spam                             | 1.1.2   |        |
| fof-analytics                             | 1.1.0   |        |
| flarumtr-mobile-search                    | v1.2    |        |
| flarum-subscriptions                      | v1.8.1  |        |
| flarum-statistics                         | v1.8.1  |        |
| flarum-pusher                             | v1.8.1  |        |
| flarum-mentions                           | v1.8.4  |        |
| flarum-likes                              | v1.8.1  |        |
| flarum-lang-english                       | v1.8.0  |        |
| flarum-lang-chinese-traditional           | v1.23.0 |        |
| flarum-lang-chinese-simplified            | v1.4.2  |        |
| flarum-extension-manager                  | v1.0.4  |        |
| flarum-bbcode                             | v1.8.0  |        |
| davwheat-ads                              | 1.2.0   |        |
| datlechin-silent-edit                     | v0.1.0  |        |
| datlechin-scroll-buttons                  | v1.1.0  |        |
| datlechin-posted-on                       | v0.2.1  |        |
| datlechin-link-preview                    | v1.5.0  |        |
| clarkwinkelmann-scout                     | 0.3.5   |        |
| clarkwinkelmann-first-post-approval       | 1.0.1   |        |
| clarkwinkelmann-author-change             | 1.0.3   |        |
| cccyun-clogin-oauth                       | v1.0.2  |        |
| blomstra-turnstile                        | 0.1.6   |        |
| blomstra-spam-prevention                  | 1.7.0   |        |
| blomstra-fontawesome                      | 0.1.5   |        |
| askvortsov-markdown-tables                | v1.2.1  |        |
| askvortsov-article-series                 | v0.2.0  |        |
| afrux-online-users-widget                 | v0.1.6  |        |
| afrux-forum-stats-widget                  | v0.1.1  |        |
| afrux-asirem                              | v0.1.8  |        |
| acpl-mobile-tab                           | 1.4.4   |        |
+-------------------------------------------+---------+--------+
Base URL: https://flarum.subarist.net
Installation path: /www/wwwroot/flarum
Queue driver: redis
Session driver: redis (Code override. Configured to file)
Scheduler status: Active
Mail driver: smtp
Debug mode: ON

Don't forget to turn off debug mode! It should never be turned on in a production system.`

RelicSystem

Subarist I encountered the same issue when in installed the blog extension, seems to be something between those two extensions not working as expected without the blog extension all was functional once again.

Subarist

JasperVriends
Hi,Sir
The file does exist, but I found it in the "temp-vendor" directory:
/www/wwwroot/flarum/temp-vendor/v17development/flarum-blog/src/SeoPage/SeoBlogOverviewMeta.php

There are no errors in the admin panel; it occurs when logging into the homepage for the first time with the admin account.

JasperVriends

Subarist Interesting! So inside the vendor forum, you don't see that file? If so, can you try to uninstall the extension and then re-install? Or is the temp-vendor your backup?

Subarist

JasperVriends
There is no "src/SeoPage" under the "vendor" .
In fact, I don't know when and how the "temp-vendor" was generated. I have never seen this directory.
However, I tried to remove "temp-vendor" and it seems that the system is not affected.

But when I tried to uninstall & re-install the SEO extension once again, everything went back to normal.
The error message disappeared and no longer appears. 😆

CyberGene

I get this on migrate


Migrating extension: v17development-seo

In Connection.php line 712:
                                                         
  SQLSTATE[42000]: Syntax error or access violation: 11  
  70 BLOB/TEXT column 'object_type' used in key specifi  
  cation without a key length (SQL: alter table `seo_me  
  ta` add unique `seo_meta_object_id_object_type_unique  
  `(`object_id`, `object_type`))                         
                                                         

In Exception.php line 18:
                                                         
  SQLSTATE[42000]: Syntax error or access violation: 11  
  70 BLOB/TEXT column 'object_type' used in key specifi  
  cation without a key length                            
                                                         

In PDOStatement.php line 117:
                                                         
  SQLSTATE[42000]: Syntax error or access violation: 11  
  70 BLOB/TEXT column 'object_type' used in key specifi  
  cation without a key length

MySQL version: 8.0.36-28

Fortunately my forum still works but the migration is broken and stops at this extension. This needs an urgent fix.

navindra

CyberGene PC isn't working for me. Not sure if it's working for others.

Something went wrong while trying to load the full version of this site. Try hard-refreshing this page to fix the error.

CyberGene

https://stackoverflow.com/questions/1827063/mysql-error-key-specification-without-a-key-length#1827099

CyberGene

navindra thanks for the heads up. I removed the extension, does it work now? (To me it always worked, maybe I got served a cached version)

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.

navindra

CyberGene Yes, it's working now. 🙂

RelicSystem

CyberGene Guys, please be more proactive in future, especially after major reworks of extensions.

Seems a bit harsh. The extension is not only open source, it also happens to be free, with likely countless thankless hours put into it. The onus of testing should be on you before you deploy it live - they cannot and should not be expected to test every weird setup across the countless distributions.

JasperVriends

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 🙂

CyberGene

RelicSystem every weird setup

My MySQL is the latest LTS version. That’s far from a weird setup. It’s the most orthodox setup there can be. And no, open source doesn’t mean that major rework testing should be on the users.

BTW, the error seems to be valid for all MySQL versions. I would assume a migration was not tested with MySQL.

Besides, even if we assume that the burden of testing this new development lies on us, users, well, that error was reported here, just a few posts above, by another user, two days ago. A simple search showed it’s a MySQL specific that is version independent.

luceos

CyberGene And no, open source doesn’t mean that testing major rework should be on the users.

Every hosting environment can be different. Different php versions, different database versions, different browsers, different internet connections, different locales, different combinations of extensions, different flarum core versions, different content created, etc.

You cannot expect maintainers to be able to put in so many hours to test every edge case. And every maintainer who releases a new major build will have tested their changes locally, or they wouldn't tag that release.

Understand that by demanding this level of engagement from a maintainer, is likely to cause frustration or stress on their end. A potential outcome could be for the maintainer to lose interest entirely. I don't expect you to want this, and neither do they.

So please, be respectful and if you want to be supportive, here are a few things you can do to help:

help isolate the issue by categorizing reports, asking users for the php flarum info, testing against a clean install etc
reply in a positive way and be thankful for the fact that Jasper did come back to give you a massive overhaul of his extension
offer to buy Jasper a coffee (or tea) to boost their morale and act as an incentive to resolve the issue you encountered.

CyberGene

luceos reading about the issue, it seems to be a limitation with MySQL hence with all versions (you cannot specify a TEXT or a BLOB field to be a primary key in MySQL unless you also provide a length of what should be used as a primary key and indexed). A simple Google search on the original issue that was posted by another user two days ago would have sufficed to see that it's a general MySQL incompatibility and not a matter of specific environment.

luceos Understand that by demanding this level of engagement from a maintainer, is likely to cause frustration or stress on their end.

I understand that but then imagine the frustration of a ton of users unable to use my forum. Somebody suggested to not update my live forum. Great, is there an easy way to stage-test my live forum? One can't seriously expect me to make a new DB copy, a new Flarum directory copy with proper config edits to reflect the new location, the new DB, then disabling emails, Pusher, PWA, and all stuff that can potentially send emails and notifications to production users while testing a staged copy. All that in order to test any new update of an extension.

luceos offer to buy Jasper a coffee (or tea) to boost their morale and act as an incentive to resolve the issue you encountered.

You know that I've contributed to Flarum, to you, and other devs. But I don't agree that I should pay in order for things to get fixed. I usually pay for a good work or if I have a proposal.

I appreciate what Jasper has made and I thank you. But I really hope that he can find some time to iron out issues in a timely matter after a major rehaul. Frankly speaking, I didn't update this extension explicitly. I’m not SEO obsessed. I just perform regular Flarum upgrade/migrate/cache-clear on my forum and for 3 years I've never had any major issues with that approach. It's only this morning that I encountered the migration error that I realized there's been such a major overhaul with this extension and the migration doesn't work with MySQL.

luceos

Proposed a potential fix: v17development/flarum-seo97

« Previous Page