Errors after update to version 1.8.3

  • Mike Meinz

    (@mikemeinz)


    6 years ago

    Multiple errors displayed on my test web site after update to version 1.8.3.

    ( ! ) Notice: Undefined index: use_session_alternate_method in C:\wamp\www\eltownhall.com\wp-content\plugins\participants-database\classes\PDb_Session.class.php on line 35
    Call Stack
    # Time Memory Function Location
    1 0.2834 486864 {main}( ) …\plugins.php:0
    2 0.2843 534344 require_once( ‘C:\wamp\www\eltownhall.com\wp-admin\admin.php’ ) …\plugins.php:10
    3 0.2848 548400 require_once( ‘C:\wamp\www\eltownhall.com\wp-load.php’ ) …\admin.php:31
    4 0.2854 561720 require_once( ‘C:\wamp\www\eltownhall.com\wp-config.php’ ) …\wp-load.php:37
    5 0.2865 652304 require_once( ‘C:\wamp\www\eltownhall.com\wp-settings.php’ ) …\wp-config.php:106
    6 2.0195 39630040 do_action( ) …\wp-settings.php:327
    7 2.0195 39630336 WP_Hook->do_action( ) …\plugin.php:453
    8 2.0195 39630360 WP_Hook->apply_filters( ) …\class-wp-hook.php:310
    9 2.0620 40372688 Participants_Db::init( ) …\class-wp-hook.php:286
    10 3.5986 49536776 PDb_Session->__construct( ) …\participants-database.php:523

    ( ! ) Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at C:\wamp\www\eltownhall.com\wp-content\plugins\participants-database\classes\PDb_Session.class.php:35) in C:\wamp\www\eltownhall.com\wp-content\plugins\participants-database\vendor\wp-session-manager\wp-session-manager.php on line 46
    Call Stack
    # Time Memory Function Location
    1 0.2834 486864 {main}( ) …\plugins.php:0
    2 0.2843 534344 require_once( ‘C:\wamp\www\eltownhall.com\wp-admin\admin.php’ ) …\plugins.php:10
    3 0.2848 548400 require_once( ‘C:\wamp\www\eltownhall.com\wp-load.php’ ) …\admin.php:31
    4 0.2854 561720 require_once( ‘C:\wamp\www\eltownhall.com\wp-config.php’ ) …\wp-load.php:37
    5 0.2865 652304 require_once( ‘C:\wamp\www\eltownhall.com\wp-settings.php’ ) …\wp-config.php:106
    6 2.0195 39630040 do_action( ) …\wp-settings.php:327
    7 2.0195 39630336 WP_Hook->do_action( ) …\plugin.php:453
    8 2.0195 39630360 WP_Hook->apply_filters( ) …\class-wp-hook.php:310
    9 3.9950 52734760 wp_session_manager_start_session( ) …\class-wp-hook.php:284
    10 3.9950 52734760 session_start ( ) …\wp-session-manager.php:46

    ( ! ) Warning: Cannot modify header information – headers already sent by (output started at C:\wamp\www\eltownhall.com\wp-content\plugins\participants-database\classes\PDb_Session.class.php:35) in C:\wamp\www\eltownhall.com\wp-admin\includes\misc.php on line 1126
    Call Stack
    # Time Memory Function Location
    1 0.2834 486864 {main}( ) …\plugins.php:0
    2 0.2843 534344 require_once( ‘C:\wamp\www\eltownhall.com\wp-admin\admin.php’ ) …\plugins.php:10
    3 5.3881 66102720 do_action( ) …\admin.php:156
    4 5.3881 66103016 WP_Hook->do_action( ) …\plugin.php:453
    5 5.3881 66103040 WP_Hook->apply_filters( ) …\class-wp-hook.php:310
    6 5.5083 66710776 wp_admin_headers( ) …\class-wp-hook.php:286
    7 5.5083 66711144 header ( ) …\misc.php:1126

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter Mike Meinz

    (@mikemeinz)

    Four hours later after a restart of the Windows OS in the virtual machine, my test web server is no longer displaying those error messages. It is still running PDB version 1.8.3. The Windows OS restart completed the installation of Windows 10 Version 1809. I don’t understand how that could have had an effect on this issue.

    Because I don’t understand what would cause the kinds of error messages reported earlier, I am a bit concerned about trying version 1.8.3 on my live web server. I will probably wait until early Saturday or Sunday morning to do that.

    wp-config.php on my test web server contains:

    define('WP_DEBUG', true); 
define('WP_DEBUG_LOG', true); 
define( 'SCRIPT_DEBUG', true);
define( 'SAVEQUERIES', true);
    Plugin Author xnau webdesign

    (@xnau)

    Well the first is a notice, so not a problem in most contexts, the second and third warnings happened because the notice was posted, which constitutes output.

    This happened because the plugin options were momentarily out of sync, and would normally not be an issue.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Errors after update to version 1.8.3’ is closed to new replies.