Everything works fine. I just had small issue with blog extension. Nothing critical. Here is AI summary:
After migrating from v17development/flarum-seo to fof/seo 3.0.0 on a Flarum 1.8 forum using v17development/
flarum-blog, I noticed one compatibility issue worth documenting.
fof/seo itself works correctly for normal discussion pages, and the package declares replace: {"v17development/
flarum-seo": "2.0.9"}.
However, v17development/flarum-blog only registers its blog SEO page drivers when this check passes:
class_exists("V17Development\\FlarumSeo\\Extend\\SEO")
After installing fof/seo, that old class no longer exists, so the blog SEO drivers are never registered.
The result was that direct /blog/{id} URLs rendered with generic forum SEO:
WebPageog:type=website- no blog canonical
- no
BlogPosting schema
- no blog
headline / author
At the same time, /d/{id} discussion URLs could still look fine because they are handled by the fof/seo discussion driver.
I fixed it locally by making the blog extension compatible with the new namespace:
V17Development\FlarumSeo\Extend\SEO → FoF\Seo\Extend\SEOV17Development\FlarumSeo\Page\PageDriverInterface → FoF\Seo\Page\PageDriverInterfaceV17Development\FlarumSeo\SeoMeta\SeoMeta → FoF\Seo\SeoMeta\SeoMetaV17Development\FlarumSeo\SeoProperties → FoF\Seo\SeoProperties- added
: void to the handle() methods required by the new PageDriverInterface
After that:
/blog/514-... renders BlogPosting, og:type=article, canonical, headline and author/d/514-... still renders DiscussionForumPosting and canonicalizes to /blog/514-...fof/sitemap correctly lists /blog/... URLs without duplicate /d/... entries
This may be useful either as a note in the fof/seo migration docs or as a compatibility fix in v17development/flarum-blog.
