Flarum SEO

luceos

JasperVriends Then I'll need to add an or to the if statement so it's still compatiable for the old plugin-version.

If you release a new version of this extension, it's perfectly okay to drop support for extensions that are no longer maintained..

[deleted]

luceos I agree with this. The previous incarnation of best answer was broken before being brought into the FoF namespace, so there seems to be little point in supporting what is now considered legacy. Perhaps make a note in the upgrade ?

luceos

Easier would be to add fof/best-answer under suggests and the other extension under conflict.

See https://getcomposer.org/doc/04-schema.md#conflict for conflict and the full composer schema. These changes only apply to the version tagged with this information, which makes it incredibly powerful to abandon a dependency you previously used.

amanijoseph87

Hi, I have been using this extension for almost 2 years but I don't know why every time I test this with structured data i have a lot of errors in headings have this (String length of headline must be in range [0, 110]) in the logo I have this (there is a link with image but I have this error anyway) A value for the url field is required. I have this one too dateModified The dateModified field is recommended. Please provide a value if available. mainEntityOfPage The mainEntityOfPage field is recommended. Please provide a value if available.

Is there a solution for this..?

giter

Alshain Oh, my God. How do you modify the layout of your forum? I love this layout.

Hari

nice

Cathas9lives

The robots.txt unable to work properly
`public function process(Request $request, Handler $handler): Response
{
$method = $request->getMethod();
$uri = $request->getUri()->getPath() ?: '/';

    $routeInfo = $this->getDispatcher()->dispatch($method, $uri);
 
    switch ($routeInfo[0]) {
        case Dispatcher::NOT_FOUND:
            throw new RouteNotFoundException($uri);
        case Dispatcher::METHOD_NOT_ALLOWED:
            throw new MethodNotAllowedException($method);
        case Dispatcher::FOUND:
            $handler = $routeInfo[1];
            $parameters = $routeInfo[2];
 
            return $handler($request, $parameters);
    }
}`

clarkwinkelmann

Cathas9lives do you get an error message ?

wloot

Hello, Thanks for your great work. but i wanna know if it is possile that setting twitter:image meta as summary_large_image or summary by detecting the size of image, or just give us a option?

Zeokat

Yeah, as @Alshain said, there are duplicated contents with various URLs that should return 404.

Anyway is something related to Flarum itself, not to this plugin. Flarum SEO itself is a total mess. This plugin helps a little but still tons of SEO issues.

alfathso

Best-Answer not working? 🙁

Please look with mobile.
There is no answer thing in schema

I use fof-best-answer

JasperVriends

robinodds No idea why that is 🤔 I don't see any mention to '0.4-beta' in the extension or composer.json?

I'll try to reproduce it and update the extension this weekend.

alfathso This update will also fix your issue

JasperVriends

Update 1.2

This release brings you keywords support for the home page. Also, the extension now supports the current version of fof/best-answer and fof/sitemap.

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.2 is installed. And add your forum keywords! 🙂

Changelog:

Added forum keywords support
Added support for fof/best-answer, thanks to v17development/flarum-seo26
Added site og:type property and added og:url property to home page
Added missingog:title to tag page
Updated Canonical URL for profiles and added profile:username property
Replaced Zend namespace with Laminas
Removed support for flagrow/sitemap and moved to fof/sitemap
Bumped minimal Flarum version to Beta 12

The above update will fix the following issues of: TommyTran732 alfathso therealsujitk and implements some of Alshain feedback.

robinodds

Why does the SEO Ext row looks like this?

Hari

robinodds where can i get this information ? is it in admin area ?

robinodds

Hari

Admin Dashboard

rob006

JasperVriends No idea why that is 🤔 I don't see any mention to '0.4-beta' in the extension or composer.json?

This version is detected by Packagist, since there is tag with such name:
https://packagist.org/packages/v17development/flarum-seo#0.4-beta
https://github.com/v17development/flarum-seo/releases

I'm not sure why this is reported as an error, 0.4-beta looks like valid version for me.

clarkwinkelmann

I suppose Packagist accepts non-semver-compilant versions.

If we read the semver spec, 0.4-beta is not a valid version https://semver.org/

A normal version number MUST take the form X.Y.Z

But because it's a valid version in Packagist, I think the correct approach here would be for Admin Dashboard to use Composer's normalize() function https://github.com/composer/semver/blob/master/src/VersionParser.php#L102 on the version before using it as semver.

rob006

clarkwinkelmann It definitely should not fail hard when it finds one invalid version. At worst case 0.4-beta and similar versions should be ignored.

I've already implemented finding last version for my Weblate initiative (based on list of tags from Github/Gitlab, but it should work with Packagist data too), you may want to take a look: https://github.com/rob006-software/flarum-translations-builder/blob/60946656b1b63ffd3e89bd6c41c3353a34568eef/components/extensions/ExtensionsRepository.php#L270-L312

TommyTran732

I have a tiny issue with your addon, it is complaining about the sitemap addon. I do have the fof Sitemap addon installed, enabled, and the Sitemap is there, but it still thinks that I have not set it up. I have tried reinstalling both addons, but the issue does not go away. Is there a way you could help me with this?

Thank you!

datitisev

TommyTran732 Looks like the extension is looking for the flagrow-sitemap ID. When you installed flagrow/sitemap, I assume it installed the fof version as the GitHub repository was transferred, so Packagist is retrieving the FriendsOfFlarum repository now.

dumi_dev

datitisev Hi!, I am facing the same issue, the fof sitemap isnt being picked up and is showing me the same error.
Irregardless, love this plugin so much!

« Previous Page Next Page »