• Resolved mfkne

    (@mfkne)


    Please make version 3.1.3 (or sooner) back available, as new version 3.1.4. crashed my backend. The days before i got several infos that plugin had problems.

    • This topic was modified 11 months, 2 weeks ago by mfkne.
Viewing 15 replies - 16 through 30 (of 30 total)
  • Our Website crashed as well. I got a very similar error report. I had to deactivate the plugin. I hope this will be fixed soon. We really like the plugin, it is really helpful

    One website using this plugin crashed on the backend.

    WP 6.4.2

    Deactivating plugin, deleting it or uploading version 3.1.3 had no success.

    The site is still down on backend.

    Please give some solution to this problem. Thanks

    • This reply was modified 11 months, 2 weeks ago by questionmark.
    Plugin Author andergmartins

    (@andergmartins)

    Hi guys, thanks for all the feedback, and sorry for the inconvenience.

    We have already a beta package addressing it:

    https://github.com/publishpress/PublishPress-Future/releases/tag/3.1.5-beta.1

    Please, let us know if you still have the issue.

    I tried the beta version. For my sites, it’s ok now. No more error.

    Thank you

    Same problem with the Plugin Future after upgrade.

    Here is my error reports, it’s always about line 41 / 42 / 43 of SettingsPostTypesModel.php

    Also found a typo-error there: it says ‘temrs’ instead of ‘terms’, but changing this did not fix the overall problem of crashing wordpress!

    
    Warning: array_map(): Expected parameter 2 to be an array, string given in /var/www/web173/html/wordpresstest/wp-content/plugins/post-expirator/src/Modules/Settings/Models/SettingsPostTypesModel.php on line 41
    
    Warning: array_filter() expects parameter 1 to be array, null given in /var/www/web173/html/wordpresstest/wp-content/plugins/post-expirator/src/Modules/Settings/Models/SettingsPostTypesModel.php on line 42
    
    Warning: array_map(): Expected parameter 2 to be an array, null given in /var/www/web173/html/wordpresstest/wp-content/plugins/post-expirator/src/Modules/Settings/Models/SettingsPostTypesModel.php on line 43
    
    Warning: Cannot modify header information - headers already sent by (output started at /var/www/web173/html/wordpresstest/wp-content/plugins/post-expirator/src/Modules/Settings/Models/SettingsPostTypesModel.php:41) in /var/www/web173/html/wordpresstest/wp-content/plugins/beautiful-and-responsive-cookie-consent/class/class-nsc_bar_cookie_handler.php on line 252
    
    Warning: Cannot modify header information - headers already sent by (output started at /var/www/web173/html/wordpresstest/wp-content/plugins/post-expirator/src/Modules/Settings/Models/SettingsPostTypesModel.php:41) in /var/www/web173/html/wordpresstest/wp-content/plugins/beautiful-and-responsive-cookie-consent/class/class-nsc_bar_cookie_handler.php on line 252
    
    Warning: Cannot modify header information - headers already sent by (output started at /var/www/web173/html/wordpresstest/wp-content/plugins/post-expirator/src/Modules/Settings/Models/SettingsPostTypesModel.php:41) in /var/www/web173/html/wordpresstest/wp-content/plugins/beautiful-and-responsive-cookie-consent/class/class-nsc_bar_cookie_handler.php on line 252
    
    Warning: Cannot modify header information - headers already sent by (output started at /var/www/web173/html/wordpresstest/wp-content/plugins/post-expirator/src/Modules/Settings/Models/SettingsPostTypesModel.php:41) in /var/www/web173/html/wordpresstest/wp-content/plugins/beautiful-and-responsive-cookie-consent/class/class-nsc_bar_cookie_handler.php on line 252
    
    Warning: Cannot modify header information - headers already sent by (output started at /var/www/web173/html/wordpresstest/wp-content/plugins/post-expirator/src/Modules/Settings/Models/SettingsPostTypesModel.php:41) in /var/www/web173/html/wordpresstest/wp-content/plugins/beautiful-and-responsive-cookie-consent/class/class-nsc_bar_cookie_handler.php on line 252
    Skip to content

    Our site also crashed after update to 3.1.4. I removed the plugin for now, hoping the error will be fixed soon. We got the same TypeError….:

    [14-Dec-2023 02:52:35 UTC] PHP Fatal error: Uncaught TypeError: array_map(): Argument #2 ($array) must be of type array, string given in /home/lvbhb/public_html/wp-content/plugins/post-expirator/src/Modules/Settings/Models/SettingsPostTypesModel.php:41
    Stack trace: 0 /home/lvbhb/public_html/wp-content/plugins/post-expirator/src/Modules/Settings/Models/SettingsPostTypesModel.php(41): array_map() 1 /home/lvbhb/public_html/wp-content/plugins/post-expirator/src/Modules/Expirator/Models/PostTypesModel.php(29): PublishPress\Future\Modules\Settings\Models\SettingsPostTypesModel->getPostTypesSettings() 2 /home/lvbhb/public_html/wp-content/plugins/post-expirator/src/Modules/Expirator/Controllers/BulkActionController.php(68): PublishPress\Future\Modules\Expirator\Models\PostTypesModel->getActivatedPostTypes() 3 /home/lvbhb/public_html/wp-content/plugins/post-expirator/src/Modules/Expirator/Controllers/BulkActionController.php(55): PublishPress\Future\Modules\Expirator\Controllers\BulkActionController->addHooks() 4 /home/lvbhb/public_html/wp-content/plugins/post-expirator/src/Modules/Expirator/Module.php(128): PublishPress\Future\Modules\Expirator\Controllers\BulkActionController->initialize() 5 /home/lvbhb/public_html/wp-content/plugins/post-expirator/src/Core/Plugin.php(115): PublishPress\Future\Modules\Expirator\Module->initialize() 6 /home/lvbhb/public_html/wp-content/plugins/post-expirator/src/Core/Plugin.php(108): PublishPress\Future\Core\Plugin->initializeModules() 7 /home/lvbhb/public_html/wp-content/plugins/post-expirator/post-expirator.php(126): PublishPress\Future\Core\Plugin->initialize() 8 /home/lvbhb/public_html/wp-includes/class-wp-hook.php(308): PublishPress\Future{closure}() 9 /home/lvbhb/public_html/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters() 10 /home/lvbhb/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() 11 /home/lvbhb/public_html/wp-settings.php(632): do_action() 12 /home/lvbhb/public_html/wp-config.php(102): require_once(‘/home/lvbhb/pub…’) 13 /home/lvbhb/public_html/wp-load.php(50): require_once(‘/home/lvbhb/pub…’) 14 /home/lvbhb/public_html/wp-blog-header.php(13): require_once(‘/home/lvbhb/pub…’) 15 /home/lvbhb/public_html/index.php(17): require(‘/home/lvbhb/pub…’) 16 {main}

    thrown in /home/lvbhb/public_html/wp-content/plugins/post-expirator/src/Modules/Settings/Models/SettingsPostTypesModel.php on line 41

    Plugin Support Riza Maulana Ardiyanto

    (@rizaardiyanto)

    @lureki Thanks for letting us know about the typo.

    @spithost @lureki Could you please try the beta version that @andergmartins provide above? Let us know how it goes.

    Typo error in line 43 of SettingsPostTypesModel.php:

            $tersmName = array_map(function($termId)

    Another typo error in line 56 in SettingsPostTypesModel.php:

          'termsName' => $tersmName,

    As the page is live online I’m not keen to try the Beta.
    Will wait until others recommend it or you update the install version…
    Sorry, don’t want to be unable to login to WP again…

    thank you very much!
    version 3.1.5 solved the problem(s) for me

    Plugin Support Riza Maulana Ardiyanto

    (@rizaardiyanto)

    Guys,

    This issue should be resolved in the recent release, version 3.1.5. If you still encounter any problems, please open a new thread, and we will assist you further.

    Thank you.

    Release 3.1.5 works! Thanks!

    Hi.

    just tested it on 2 development websites and everything seems to work :).

    Thanks for the quick patch.

    Have a great evening!

    Pierre.

    @rizaardiyanto In just half a year, this is the 4th update causing major issues. This plugin was a lot more stable in the days it was still called “Post Expirator” and it did just that, reliably.

    Plugin Support Riza Maulana Ardiyanto

    (@rizaardiyanto)

    @willemb2

    We apologize for any inconvenience caused. While we aim to improve the plugin by refactoring old code for better maintenance, we understand the importance of stability. We’ll strive to be more cautious in future releases to avoid disruptions.

    Your feedback is valuable, and we appreciate your understanding. If you have further concerns or questions, please feel free to let us know.

Viewing 15 replies - 16 through 30 (of 30 total)
  • The topic ‘Version 3.1.4 crashed my site’ is closed to new replies.