FriendsOfFlarum Reactions

Gorm

It's very stable and very flexible with user reactions for now. Not ideal (some minor), but very usefull. It's well integrated with likes. It's tested widely with Flarum 1.8.5 with PHP 8.0/8.1. But be noticed, that it doesnt work with PHP 8.2/8.3 for now while Flarum in general continue to works fine.

Similiar errors with 8.2/8.3

Deprecated: Creation of dynamic property FoF\Reactions\Event\PostWasUnreacted::$actor is deprecated in /var/www/../vendor/flarum/core/src/Foundation/DispatchEventsTrait.php on line 31

Fatal error: Uncaught Laminas\HttpHandlerRunner\Exception\EmitterException: Unable to emit response; headers already sent in /var/www/../vendor/flarum/core/src/Foundation/DispatchEventsTrait.php:31 in /var/www/../vendor/laminas/laminas-httphandlerrunner/src/Exception/EmitterException.php:15 Stack trace: #0 /var/www/../vendor/laminas/laminas-httphandlerrunner/src/Emitter/SapiEmitterTrait.php(38): Laminas\HttpHandlerRunner\Exception\EmitterException::forHeadersSent('/var/www/...', 31) #1 /var/www/../vendor/laminas/laminas-httphandlerrunner/src/Emitter/SapiEmitter.php(21): Laminas\HttpHandlerRunner\Emitter\SapiEmitter->assertNoPreviousOutput() #2 /var/www/../vendor/laminas/laminas-httphandlerrunner/src/RequestHandlerRunner.php(75): Laminas\HttpHandlerRunner\Emitter\SapiEmitter->emit(Object(Flarum\Api\JsonApiResponse)) #3 /var/www/../vendor/flarum/core/src/Http/Server.php(45): Laminas\HttpHandlerRunner\RequestHandlerRunner->run() #4 /var/www/../index.php(26): Flarum\Http\Server->listen() #5 {main} thrown in /var/www/../vendor/laminas/laminas-httphandlerrunner/src/Exception/EmitterException.php on line 15

Added later:
Hm... I am switch composer to PHP 8.1 and update my install. And Laminas have an update too... So, maybe it can work with PHP 8.2?? Need to try.. I will investigate.

Composer must be switched to similiar version of php. Check with composer check-platform-reqs. Also I am runing composer self-update. And now try to update:

bash-4.2$ composer update --prefer-dist --no-plugins --no-dev -a --with-all-dependencies                                       
Loading composer repositories with package information
Updating dependencies
Lock file operations: 3 installs, 20 updates, 2 removals
  - Removing fgrosse/phpasn1 (v2.5.0)
  - Removing league/oauth2-linkedin (5.1.2)
  - Upgrading brick/math (0.9.3 => 0.11.0)
  - Upgrading fof/oauth (1.6.6 => 1.6.7)
  - Upgrading laminas/laminas-escaper (2.12.0 => 2.13.0)
  - Upgrading laminas/laminas-httphandlerrunner (2.5.0 => 2.10.0)
  - Upgrading laminas/laminas-stratigility (3.10.0 => 3.11.0)
  - Locking masterminds/html5 (2.8.1)
  - Upgrading nette/schema (v1.2.5 => v1.3.0)
  - Upgrading omines/oauth2-gitlab (3.5.0 => 3.6.0)
  - Locking paragonie/constant_time_encoding (v2.6.3)
  - Upgrading ramsey/collection (1.3.0 => 2.0.0)
  - Locking spomky-labs/pki-framework (1.1.1)
  - Upgrading symfony/css-selector (v6.0.19 => v6.4.3)
  - Upgrading symfony/deprecation-contracts (v3.0.2 => v3.4.0)
  - Upgrading symfony/dom-crawler (v6.0.19 => v6.4.3)
  - Upgrading symfony/event-dispatcher-contracts (v3.0.2 => v3.4.0)
  - Upgrading symfony/filesystem (v6.0.19 => v6.4.3)
  - Upgrading symfony/service-contracts (v2.5.2 => v3.4.1)
  - Upgrading symfony/string (v6.0.19 => v6.4.3)
  - Upgrading web-token/jwt-core (v2.2.11 => 3.2.9)
  - Upgrading web-token/jwt-key-mgmt (v2.2.11 => 3.2.9)
  - Upgrading web-token/jwt-signature (v2.2.11 => 3.2.9)
  - Upgrading web-token/jwt-signature-algorithm-ecdsa (v2.2.11 => 3.2.9)
  - Upgrading web-token/jwt-util-ecc (v2.2.11 => 3.2.9)
Writing lock file
Installing dependencies from lock file
Package operations: 3 installs, 20 updates, 2 removals
  - Downloading symfony/deprecation-contracts (v3.4.0)
  - Downloading symfony/event-dispatcher-contracts (v3.4.0)
  - Downloading symfony/string (v6.4.3)
  - Downloading symfony/service-contracts (v3.4.1)
  - Downloading symfony/filesystem (v6.4.3)
  - Downloading laminas/laminas-escaper (2.13.0)
  - Downloading laminas/laminas-stratigility (3.11.0)
  - Downloading laminas/laminas-httphandlerrunner (2.10.0)
  - Downloading ramsey/collection (2.0.0)
  - Downloading symfony/css-selector (v6.4.3)
  - Downloading nette/schema (v1.3.0)
  - Downloading web-token/jwt-util-ecc (3.2.9)
  - Downloading spomky-labs/pki-framework (1.1.1)
  - Downloading paragonie/constant_time_encoding (v2.6.3)
  - Downloading web-token/jwt-core (3.2.9)
  - Downloading web-token/jwt-signature (3.2.9)
  - Downloading web-token/jwt-signature-algorithm-ecdsa (3.2.9)
  - Downloading web-token/jwt-key-mgmt (3.2.9)
  - Downloading omines/oauth2-gitlab (3.6.0)
  - Downloading fof/oauth (1.6.7)
  - Downloading masterminds/html5 (2.8.1)
  - Downloading symfony/dom-crawler (v6.4.3)
  - Removing league/oauth2-linkedin (5.1.2)
  - Removing fgrosse/phpasn1 (v2.5.0)
  - Upgrading symfony/deprecation-contracts (v3.0.2 => v3.4.0): Extracting archive
  - Upgrading symfony/event-dispatcher-contracts (v3.0.2 => v3.4.0): Extracting archive
  - Upgrading symfony/string (v6.0.19 => v6.4.3): Extracting archive
  - Upgrading symfony/service-contracts (v2.5.2 => v3.4.1): Extracting archive
  - Upgrading symfony/filesystem (v6.0.19 => v6.4.3): Extracting archive
  - Upgrading laminas/laminas-escaper (2.12.0 => 2.13.0): Extracting archive
  - Upgrading laminas/laminas-stratigility (3.10.0 => 3.11.0): Extracting archive
  - Upgrading laminas/laminas-httphandlerrunner (2.5.0 => 2.10.0): Extracting archive
  - Upgrading ramsey/collection (1.3.0 => 2.0.0): Extracting archive
  - Upgrading brick/math (0.9.3 => 0.11.0): Extracting archive
  - Upgrading symfony/css-selector (v6.0.19 => v6.4.3): Extracting archive
  - Upgrading nette/schema (v1.2.5 => v1.3.0): Extracting archive
  - Upgrading web-token/jwt-util-ecc (v2.2.11 => 3.2.9): Extracting archive
  - Installing spomky-labs/pki-framework (1.1.1): Extracting archive
  - Installing paragonie/constant_time_encoding (v2.6.3): Extracting archive
  - Upgrading web-token/jwt-core (v2.2.11 => 3.2.9): Extracting archive
  - Upgrading web-token/jwt-signature (v2.2.11 => 3.2.9): Extracting archive
  - Upgrading web-token/jwt-signature-algorithm-ecdsa (v2.2.11 => 3.2.9): Extracting archive
  - Upgrading web-token/jwt-key-mgmt (v2.2.11 => 3.2.9): Extracting archive
  - Upgrading omines/oauth2-gitlab (3.5.0 => 3.6.0): Extracting archive
  - Upgrading fof/oauth (1.6.6 => 1.6.7): Extracting archive
  - Installing masterminds/html5 (2.8.1): Extracting archive
  - Upgrading symfony/dom-crawler (v6.0.19 => v6.4.3): Extracting archive
Package swiftmailer/swiftmailer is abandoned, you should avoid using it. Use symfony/mailer instead.
Generating optimized autoload files
Class FoF\OAuth\Providers\Custom\LinkedIn\Provider\Exception\LinkedInAccessDeniedException located in ./vendor/fof/oauth/src/Pr
oviders/Custom/LinkedIn/Provider/Exception/LinkedInAccessDeniedException .php does not comply with psr-4 autoloading standard. 
Skipping.
115 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
No security vulnerability advisories found.
bash-4.2$ php flarum migrate
bash-4.2$ php flarum cache:clear
```

But 10 minutes ago there is no any updates!! Now I will try with PHP 8.2.. And site goes down with described error 🙂 I am afraid to update all with PHP 8.2 cause of fear to lost my installation 🙂 Rolled back to PHP 8.1.

Use it with PHP 8.0 or 8.1 until fixes.

datitisev

Gorm Deprecation warnings should not be printed in production. See if https://discuss.flarum.org/d/30812-deprecated-warnings-in-the-logs-with-php-81-and-13/2 helps with turning it off.

This issue will need to be addressed eventually, but for now you can just disable the warning.

Gorm

datitisev I really appreciate your work, just warn other with php 8.2+. Docs on https://docs.flarum.org/install/ says that 8.0 in "end of life" status and 8.2/8.3 recommended. 8.1 without any remarks. I am happy with PHP 8.1 for now 🙂

Gorm

datitisev non critical, bug.. All works, but I seen an error in admin panel when adding new reaction and switch it on/off.

Uncaught (in promise)
Object { status: 404, options: {…}, xhr: XMLHttpRequest, responseText: '{"errors":[{"status":"404","code":"not_found"}]}', response: {…}, alert: {…} }

alert: Object { type: "error", content: (1) […], controls: false }

options: Object { background: true, method: "POST", url: "https://olala.area51/forum/api/reactions/undefined", … }

response: Object { errors: (1) […] }

responseText: '{"errors":[{"status":"404","code":"not_found"}]}'

status: 404

xhr: XMLHttpRequest { readyState: 4, timeout: 0, withCredentials: false, … }

<prototype>: Object { … }

But in frontend seems all work fine. Reaction added.

Bost

Gorm I'm also getting an error, but it's not that one. It's something with selecting '0' and it's null, idk. I don't feel like making a bug report though. Oh, and with mine it doesn't load the configuration for it at all.

datitisev

1.4.1

Some admin page fixes by @dsevillamartin in FriendsOfFlarum/reactions83
- Ask for confirmation when deleting reactions
- Fix modifying newly-created reaction (Gorm)
- Fix fuzzy emoji search breaking when no results are found ( Bost)

Full Changelog: FriendsOfFlarum/reactions1.4.0 → 1.4.1

datitisev

Bost I'd still like to see it fixed. When exactly does this error appear? What parts of the admin dashboard break (assuming it's the admin page)?

Bost

datitisev

Link: https://bibble.flarum.cloud/admin#/extension/fof-reactions

It's just blank when I try to access it. Console error:

TypeError: Cannot read properties of null (reading '0')
    at w (emoji.js:15:32)
    at SettingsPage.js:69:32
    at Array.map (<anonymous>)
    at a.content (SettingsPage.js:67:33)
    at n.sections (ExtensionPage.tsx:112:31)
    at n.view (ExtensionPage.tsx:68:53)
    at Function.s (render.js:30:16)
    at render.js:155:45
    at render.js:160:3
    at c (render.js:66:8)

Bost

datitisev Fix fuzzy emoji search breaking when no results are found ( Bost)

Hey, I'm still having the exact same issue.

datitisev

Bost hm, interesting. I believe I was able to reproduce your bug and fix it locally. Is the error in console still the same?

Bost

datitisev Yeah, Cannot read properties of null (reading '0')

datitisev

Bost I can no longer reproduce the issue locally after my fix. Are you running the latest version? If it's the link you posted, that seems to be running v1.3.5 and not v1.4.1

Bost

datitisev How do I upgrade it?

datitisev

Bost Oh, I just realized you're using FreeFlarum. You'll have to ask them to update it, I think.

ernestdefoe

Bost you will have to wait till the owner of FreeFlarum updates it. They usually do it every so often so all extensions are up to date. Might want to post on their support forums to see when the next round of updates will be.

Bost

ernestdefoe I asked them, they did it, and now it's working. 🎉

tom23

Hello we have a problem
Before his spell, a user still rated hundreds of contributions poorly, which for many users who are not irritated in the topic. Can I somehow remove the votes from a single user? If so how?
Thank you

datitisev

tom23 Are you asking if there is a way to remove all reactions made by a user? If so, there's not currently a way to do so.

Gorm

tom23 since 1.4.0 you can remove individual reactions from any user. I am using last available 1.4.1 with Flarum 1.8.5 and all works fine.

If you have too many reactions for manual deletions - just delete the user and his reactions will gone 😉 Ideal if user have a 0 messages. If user have many posts... his posts will stay 🙂 Standard Flarum's behavior.

BrodyStone21

Is it possible, instead of converting reactions to likes, to convert likes to reactions? Like if someone likes the post, it will become a 👍️

Also, can I make the reactions display when hovering over the like button? I think that would get more people using them.

User31

BrodyStone21 I thought it was the Votes extension that did that.
Does this Reactions extension do it as well?

Trc4

BrodyStone21 Also, can I make the reactions display when hovering over the like button? I think that would get more people using them.

this would be great 👍

« Previous Page Next Page »