After updating to version 4.0.2, an error occurs in the admin page.

  • Resolved t.inoue

    (@tinoue)


    1 month ago

    Hello.
    After updating to 4.0.2 on multiple WordPress sites I manage, an error occurs when I enter the WordPress admin screen.
    I have confirmed that it works when I disable the plugin or downgrade to 3.4.4.

    The error that appears after logging in is as follows:

    Warning: Attempt to read property “post_content” on null in /wp-content/plugins/post-expirator/src/Modules/Workflows/Models/WorkflowModel.php on line 254
    Warning: Attempt to read property “post_content” on null in /wp-content/plugins/post-expirator/src/Modules/Workflows/Models/WorkflowModel.php on line 254
    Warning: Attempt to read property “ID” on null in /wp-content/plugins/post-expirator/src/Modules/Workflows/Models/WorkflowModel.php on line 109
    Fatal error: Uncaught TypeError: PublishPress\Future\Modules\Workflows\Models\WorkflowModel::getId(): Return value must be of type int, null returned in /wp-content/plugins/post-expirator/src/Modules/Workflows/Models/WorkflowModel.php:109 Stack trace: 0 /wp-content/plugins/post-expirator/src/Modules/Workflows/Domain/Engine/WorkflowEngine.php(146): PublishPress\Future\Modules\Workflows\Models\WorkflowModel->getId() 1 /wp-content/plugins/post-expirator/src/Modules/Workflows/Module.php(140): PublishPress\Future\Modules\Workflows\Domain\Engine\WorkflowEngine->start() 2 /wp-content/plugins/post-expirator/src/Modules/Workflows/Module.php(95): PublishPress\Future\Modules\Workflows\Module->initializeEngine()

    … 18 {main} thrown in /wp-content/plugins/post-expirator/src/Modules/Workflows/Models/WorkflowModel.php on line 109

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Steve Burge

    (@stevejburge)

    Hi @tinoue. Thanks for using PublishPress. Please update to version 4.0.3 to see if this solves the issue.

    Thread Starter t.inoue

    (@tinoue)

    I updated one of the problematic WordPress sites to 4.0.3.
    I was able to confirm that there are no more errors when logging in.
    Thank you.

    Plugin Author Steve Burge

    (@stevejburge)

    Thanks @tinoue. We appreciate you reporting the issue and confirming the fix.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.