I made the following changes i config file:
'charset' => 'utf8mb4',
'collation' => 'utf8mb4_unicode_ci',
'charset' => 'utf8',
'collation' => 'utf8_unicode_ci',
and now it works ok!
Nimren This is not a fully recommended suggestion as it will break support for some Unicode such as emoji and flag codes.
tankerkiller125 I only did this to install extension, after that I went back to the default 😀
Missing a translation key：
Littlegolden FriendsOfFlarum does not provide translations other than English. You should report this to the maintainer of the language pack you are using. Unless it also happens in English ?
composer update fof/geoip
php flarum cache:clear
clarkwinkelmann yes，in english also.
Littlegolden Ah, I see the issue. No service is chosen, therefore the description is for a nonexistent service instead of being hidden. Thanks for the report!
datitisev What does this error mean?
Littlegolden it means that merging and reordering post numbers failed - it's a known issue and one hard to tackle, but we may have a solution for it soon.
datitisev are you sure it's related? 🤔 this is the GeoIP extension
matteocontrini So this is not a problem with the geoip extension? I saw that the ip in the error message so I was thought it is related to geoip. . .
matteocontrini Littlegolden Oh wow, I instantly assumed it was a merge discussions error, apologies. Uh, this sometimes happens because reasons and I need to fix it - make sure you are updated to the latest version tho, some instances of the error were solved already I think.
Version -> fof-geoip/v0.1.5
When posting, the bottom left corner will prompt an error, but the post has already been posted.
Nice work ❤️
I installed the plug-in, but he can't see anything.
tangba See anything where? Did you configure the source of the geoip data first?
datitisev I have already deleted, don't know how to use.
enable the plugin failed：
"detail": "PDOException: SQLSTATE: Syntax error or access violation: 1071 Specified key was too long; max key length is 767 bytes in /www/wwwroot/xxx/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:121\nStack trace:\n#0
I found out that this is incompatible with dexif/telegram after 2 months of testing.
This will happen if the two are enabled at same time:
Notice: Trying to get property 'identifier' of non-object in /PathToFlarum/vendor/dexif/telegram/src/Listeners/AddUserAttributes.php on line 34
Fatal error: Uncaught Laminas\HttpHandlerRunner\Exception\EmitterException: Output has been emitted previously; cannot emit response in vendor/laminas/laminas-httphandlerrunner/src/Exception/EmitterException.php:24 Stack trace: #0 vendor/laminas/laminas-httphandlerrunner/src/Emitter/SapiEmitterTrait.php(40): Laminas\HttpHandlerRunner\Exception\EmitterException::forOutputSent() #1 vendor/laminas/laminas-httphandlerrunner/src/Emitter/SapiEmitter.php(27): Laminas\HttpHandlerRunner\Emitter\SapiEmitter->assertNoPreviousOutput() #2 vendor/laminas/laminas-httphandlerrunner/src/RequestHandlerRunner.php(98): Laminas\HttpHandlerRunner\Emitter\SapiEmitter->emit(Object(Laminas\Diactoros\Response\HtmlResponse)) #3 vendor/flarum/core/src/Http/Server.php(42): Laminas\HttpHandlerRunner\RequestHandlerRunner->run() #4 /index.php(22): Flarum\Http\Server in vendor/laminas/laminas-httphandlerrunner/src/Exception/EmitterException.php on line 24
aleveltech I don't think this is caused by GeoIP. Nothing in geoip's code would make that line error. Looks like that error can happen regardless of what extensions you have installed, because it doesn't check if the DB row exists.
Referenced line of code @ https://github.com/dexif/telegram/blob/c2ee836d32bfb72b9c7779b7e08b9445495870c4/src/Listeners/AddUserAttributes.php#L34.