Posted On

Justoverclock

maybe could be better if the post could keep the device value...so if i made a post on windows, that post will be always windows, if i change to another device the next post shows the new used device

HasanMerkit

Hey, We have our own operating system. After User-Agent browser work is done, I will contact you for adding support 🙂

datlechin

HasanMerkit Okay 😉

HasanMerkit

datlechin hello again, do u remember that?
"User Agent" is ready earlier 🙂

Do you use a library for detecting OS and Browsers like ua-parser-js?
Can you add PiluX and PiluX Server support? 🙂

Please check this: faisalman/ua-parser-js617

Here is a User-Agent by PiluX and PiluX Server:

PiluX, version 2.1: Mozilla/5.0 (X11; PiluX; Ubuntu; Linux x86_64; rv:108.0) PiluX/2.1 Gecko/20100101 Firefox/108.0

PiluX Server, version 2.1: Mozilla/5.0 (X11; PiluX; Ubuntu; Linux x86_64; rv:108.0) PiluX/2.1 PiluXServer/2.1 Gecko/20100101 Firefox/108.0

Thanks 🙂 I will wait for your reply.

basti4k

very nice, thanks. 👍️
But i think we need a option for the user, in the user-settings:
Each user should decide for themselves whether or not to display the OS.
Can you perhaps implement an on / off switch?

datlechin

basti4k Can you perhaps implement an on / off switch?

added to todo list. 😉

datlechin

basti4k added in v0.1.3

HasanMerkit

Sometimes OS detail is automically change with wrong.

Example: I writed my 1th comment in Windows, 3th comment in Android. And details true. After few minutes, clicked to dissuscion again, shows 1th comment is Android(wrong) and 3ths is Windows(wrong)

datlechin

HasanMerkit

jsystems73

v01.4

Fixed datlechin/flarum-posted-on1

HasanMerkit

datlechin thanks for update 🙂

I found other problem in my PHP error log;
PHP Warning: Undefined array key "content" in /vendor/datlechin/flarum-posted-on/src/Listeners/SavePostedOnToPost.php on line 14

datlechin

HasanMerkit fixed on v0.1.5

Subarist

datlechin
I ran into an error when trying to edit user "[deleted]" posts.
I can't read the article normally after editing. I need to go to the database to clear the "posted_on" value of the article, and everything will return to normal.
Imgur

datlechin

Subarist Thanks for your report. Can you create an issue on Github repo? It will be easier for tracking
https://github.com/datlechin/flarum-posted-on

datlechin

V0.1.6

Fixed page break when user is deleted

Subarist

datlechin
thanks, checked, fixed

Subarist

After a recent extension closure, it suddenly became impossible to reopen. Reinstallation was ineffective and an error occurred during purging. (Flarum 1.7.2 php 8.2.4 MySQL 8.0.32)

The backup site that uses MySQL 5.7.41 is functioning normally.

> POST https://www.subarist.net/api/extensions/datlechin-posted-on

PDOException: SQLSTATE[42000]: Syntax error or access violation: 1091 Can't DROP 'posted_on'; check that column/key exists in /www/wwwroot/flarum/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:117
Stack trace:
#0 /www/wwwroot/flarum/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php(117): PDOStatement->execute()
#1 /www/wwwroot/flarum/vendor/illuminate/database/Connection.php(501): Doctrine\DBAL\Driver\PDOStatement->execute()
#2 /www/wwwroot/flarum/vendor/illuminate/database/Connection.php(705): Illuminate\Database\Connection->Illuminate\Database\{closure}()
#3 /www/wwwroot/flarum/vendor/illuminate/database/Connection.php(672): Illuminate\Database\Connection->runQueryCallback()
#4 /www/wwwroot/flarum/vendor/illuminate/database/Connection.php(490): Illuminate\Database\Connection->run()
#5 /www/wwwroot/flarum/vendor/illuminate/database/Schema/Blueprint.php(109): Illuminate\Database\Connection->statement()
#6 /www/wwwroot/flarum/vendor/illuminate/database/Schema/Builder.php(364): Illuminate\Database\Schema\Blueprint->build()
#7 /www/wwwroot/flarum/vendor/illuminate/database/Schema/Builder.php(211): Illuminate\Database\Schema\Builder->build()
#8 /www/wwwroot/flarum/vendor/datlechin/flarum-posted-on/migrations/2022_02_09_000000_add_posted_on_to_posts.php(16): Illuminate\Database\Schema\Builder->table()
#9 [internal function]: Illuminate\Filesystem\Filesystem::{closure}()
#10 /www/wwwroot/flarum/vendor/flarum/core/src/Database/Migrator.php(194): call_user_func()
#11 /www/wwwroot/flarum/vendor/flarum/core/src/Database/Migrator.php(213): Flarum\Database\Migrator->runClosureMigration()
#12 /www/wwwroot/flarum/vendor/flarum/core/src/Database/Migrator.php(174): Flarum\Database\Migrator->resolveAndRunClosureMigration()
#13 /www/wwwroot/flarum/vendor/flarum/core/src/Database/Migrator.php(156): Flarum\Database\Migrator->runDown()
#14 /www/wwwroot/flarum/vendor/flarum/core/src/Extension/Extension.php(501): Flarum\Database\Migrator->reset()
#15 /www/wwwroot/flarum/vendor/flarum/core/src/Extension/ExtensionManager.php(329): Flarum\Extension\Extension->migrate()
#16 /www/wwwroot/flarum/vendor/flarum/core/src/Extension/ExtensionManager.php(342): Flarum\Extension\ExtensionManager->migrate()
#17 /www/wwwroot/flarum/vendor/flarum/core/src/Extension/ExtensionManager.php(263): Flarum\Extension\ExtensionManager->migrateDown()
#18 /www/wwwroot/flarum/vendor/flarum/core/src/Api/Controller/UninstallExtensionController.php(42): Flarum\Extension\ExtensionManager->uninstall()
#19 /www/wwwroot/flarum/vendor/flarum/core/src/Api/Controller/AbstractDeleteController.php(24): Flarum\Api\Controller\UninstallExtensionController->delete()
#20 /www/wwwroot/flarum/vendor/flarum/core/src/Http/RouteHandlerFactory.php(41): Flarum\Api\Controller\AbstractDeleteController->handle()
#21 /www/wwwroot/flarum/vendor/flarum/core/src/Http/Middleware/ExecuteRoute.php(27): Flarum\Http\RouteHandlerFactory->Flarum\Http\{closure}()
#22 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/Next.php(49): Flarum\Http\Middleware\ExecuteRoute->process()
#23 /www/wwwroot/flarum/vendor/flarum/core/src/Api/Middleware/ThrottleApi.php(33): Laminas\Stratigility\Next->handle()
#24 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/Next.php(49): Flarum\Api\Middleware\ThrottleApi->process()
#25 /www/wwwroot/flarum/vendor/flarum/core/src/Http/Middleware/CheckCsrfToken.php(44): Laminas\Stratigility\Next->handle()
#26 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/Next.php(49): Flarum\Http\Middleware\CheckCsrfToken->process()
#27 /www/wwwroot/flarum/vendor/flarum/core/src/Http/Middleware/ResolveRoute.php(69): Laminas\Stratigility\Next->handle()
#28 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/Next.php(49): Flarum\Http\Middleware\ResolveRoute->process()
#29 /www/wwwroot/flarum/vendor/flarum/core/src/Http/Middleware/SetLocale.php(51): Laminas\Stratigility\Next->handle()
#30 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/Next.php(49): Flarum\Http\Middleware\SetLocale->process()
#31 /www/wwwroot/flarum/vendor/flarum/core/src/Http/Middleware/AuthenticateWithHeader.php(58): Laminas\Stratigility\Next->handle()
#32 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/Next.php(49): Flarum\Http\Middleware\AuthenticateWithHeader->process()
#33 /www/wwwroot/flarum/vendor/flarum/core/src/Http/Middleware/AuthenticateWithSession.php(31): Laminas\Stratigility\Next->handle()
#34 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/Next.php(49): Flarum\Http\Middleware\AuthenticateWithSession->process()
#35 /www/wwwroot/flarum/vendor/flarum/core/src/Http/Middleware/RememberFromCookie.php(52): Laminas\Stratigility\Next->handle()
#36 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/Next.php(49): Flarum\Http\Middleware\RememberFromCookie->process()
#37 /www/wwwroot/flarum/vendor/flarum/core/src/Http/Middleware/StartSession.php(61): Laminas\Stratigility\Next->handle()
#38 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/Next.php(49): Flarum\Http\Middleware\StartSession->process()
#39 /www/wwwroot/flarum/vendor/flarum/core/src/Api/Middleware/FakeHttpMethods.php(29): Laminas\Stratigility\Next->handle()
#40 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/Next.php(49): Flarum\Api\Middleware\FakeHttpMethods->process()
#41 /www/wwwroot/flarum/vendor/flarum/core/src/Http/Middleware/ParseJsonBody.php(28): Laminas\Stratigility\Next->handle()
#42 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/Next.php(49): Flarum\Http\Middleware\ParseJsonBody->process()
#43 /www/wwwroot/flarum/vendor/flarum/core/src/Http/Middleware/HandleErrors.php(57): Laminas\Stratigility\Next->handle()
#44 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/Next.php(49): Flarum\Http\Middleware\HandleErrors->process()
#45 /www/wwwroot/flarum/vendor/flarum/core/src/Http/Middleware/InjectActorReference.php(25): Laminas\Stratigility\Next->handle()
#46 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/Next.php(49): Flarum\Http\Middleware\InjectActorReference->process()
#47 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/MiddlewarePipe.php(75): Laminas\Stratigility\Next->handle()
#48 /www/wwwroot/flarum/vendor/middlewares/request-handler/src/RequestHandler.php(84): Laminas\Stratigility\MiddlewarePipe->process()
#49 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/Next.php(49): Middlewares\RequestHandler->process()
#50 /www/wwwroot/flarum/vendor/middlewares/base-path-router/src/BasePathRouter.php(99): Laminas\Stratigility\Next->handle()
#51 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/Next.php(49): Middlewares\BasePathRouter->process()
#52 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/Middleware/OriginalMessages.php(36): Laminas\Stratigility\Next->handle()
#53 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/Next.php(49): Laminas\Stratigility\Middleware\OriginalMessages->process()
#54 /www/wwwroot/flarum/vendor/middlewares/base-path/src/BasePath.php(73): Laminas\Stratigility\Next->handle()
#55 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/Next.php(49): Middlewares\BasePath->process()
#56 /www/wwwroot/flarum/vendor/flarum/core/src/Http/Middleware/ProcessIp.php(24): Laminas\Stratigility\Next->handle()
#57 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/Next.php(49): Flarum\Http\Middleware\ProcessIp->process()
#58 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/MiddlewarePipe.php(75): Laminas\Stratigility\Next->handle()
#59 /www/wwwroot/flarum/vendor/laminas/laminas-stratigility/src/MiddlewarePipe.php(64): Laminas\Stratigility\MiddlewarePipe->process()
#60 /www/wwwroot/flarum/vendor/laminas/laminas-httphandlerrunner/src/RequestHandlerRunner.php(73): Laminas\Stratigility\MiddlewarePipe->handle()
#61 /www/wwwroot/flarum/vendor/flarum/core/src/Http/Server.php(45): Laminas\HttpHandlerRunner\RequestHandlerRunner->run()
#62 /www/wwwroot/flarum/public/index.php(26): Flarum\Http\Server->listen()
#63 {main}

datlechin

HasanMerkit

@datlechin i want to contact you.

datlechin

HasanMerkit my discord id: ngoquocdat#4414

Subarist

Subarist
update..
The backup site with MySQL 5.7.41 also encountered an error.
"post on" extension can be trun on, but get error when attempting to publish an article.

`POST http://150.230.44.1:99/api/posts

PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'posted_on' in 'field list' in /www/wwwroot/www.impreza.com.tw/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php:82
Stack trace:
#0 /www/wwwroot/www.impreza.com.tw/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php(82): PDO->prepare()
#1 /www/wwwroot/www.impreza.com.tw/vendor/illuminate/database/Connection.php(495): Doctrine\DBAL\Driver\PDOConnection->prepare()
#2 /www/wwwroot/www.impreza.com.tw/vendor/illuminate/database/Connection.php(705): Illuminate\Database\Connection->Illuminate\Database\{closure}()
#3 /www/wwwroot/www.impreza.com.tw/vendor/illuminate/database/Connection.php(672): Illuminate\Database\Connection->runQueryCallback()
#4 /www/wwwroot/www.impreza.com.tw/vendor/illuminate/database/Connection.php(490): Illuminate\Database\Connection->run()
#5 /www/wwwroot/www.impreza.com.tw/vendor/illuminate/database/Connection.php(454): Illuminate\Database\Connection->statement()`

clarkwinkelmann

If the column doesn't exist anymore, you could delete the migration entry from the migrations table and Flarum will stop trying to roll it back and will run it again on the next enable (based on the error message, it's probably the 2022_02_09_000000_add_posted_on_to_posts migration).

Ideally, the extension developer should write the "down" migrations so that it gracefully skips if the column/table already doesn't exist ($schema->hasColumn($table, $column) can be used).

« Previous Page Next Page »