warning when installing on wp 5.4.2

  • priesterath

    (@priesterath)


    5 years, 10 months ago

    Hello,
    i just installed this plugin because of the rest api error. WordPress gave me this warning:

    Das Plugin erzeugte 2255 Zeichen mit unerwarteter Ausgabe während der Aktivierung. Wenn du „headers already sent“-Hinweise, Probleme mit Syndication-Feeds oder andere Probleme bemerkst, versuche, dieses Plugin zu deaktivieren oder zu entfernen.

    The mentioned problem occurs, if I use the template customizer. Besides this all seems to be OK. Any hints? The Rest Api error ist gone, so I think I need this plugin 😉

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Contributor Daniel Bachhuber

    (@danielbachhuber)

    5 years, 10 months ago

    Hi @priesterath

    What was the REST API error you saw that inspired you to install this plugin? The REST API doesn’t use PHP sessions, so I’m not sure that was the correct fix.

    As far as the “headers already sent” error goes, this means that one of your plugins or your theme is causing headers to be sent before WP Native PHP Sessions can run its ini_set() configuration calls. You might want to try the troubleshooting steps to resolve it.

    Thread Starter priesterath

    (@priesterath)

    5 years, 10 months ago

    Hello Daniel,
    These two errors in “Website Zustand”, they are gone if activate native php sessions.

    Die REST-API ist eine Möglichkeit, wie WordPress und andere Anwendungen mit dem Server kommunizieren. Ein Beispiel ist der Bildschirm des Block-Editors, der darauf aufbaut, deine Beiträge und Seiten anzuzeigen und zu speichern.

    Die REST-API-Anfrage ist aufgrund eines Fehlers fehlgeschlagen.
    Fehler: cURL error 28: Operation timed out after 10001 milliseconds with 0 bytes received (http_request_failed)

    Loopback-Anfragen werden verwendet, um geplante Ereignisse auszuführen, und werden auch von den integrierten Editoren für Themes und Plugins verwendet, um die Stabilität des Codes zu überprüfen.

    Die Loopback-Anfrage an deine Website ist fehlgeschlagen, das bedeutet, dass Funktionen, die sich auf sie verlassen, derzeit nicht wie erwartet funktionieren.
    Fehler: cURL error 28: Operation timed out after 10001 milliseconds with 0 bytes received (http_request_failed)

    I do not get the header already sent error, this was the part, which mkes me nervous.

    Das Plugin erzeugte 2255 Zeichen mit unerwarteter Ausgabe während der Aktivierung

    If you do not understand german, in english it should be something like

    The plugin generated 2255 characters with unexpected output during activation

    Plugin Contributor Daniel Bachhuber

    (@danielbachhuber)

    5 years, 10 months ago

    Ok. I’m not sure what the issue is, unfortunately. I’d recommend disabling your plugins one by one to see what might be causing the issue.

    Thread Starter priesterath

    (@priesterath)

    5 years, 10 months ago

    I know which one causes the health issue, or do you mean disabling all plugins one by one activate native session plugin and then re-enable all other plugins? To see if the error on activating native php session plugin disappears?

    Plugin Contributor Daniel Bachhuber

    (@danielbachhuber)

    5 years, 10 months ago

    do you mean disabling all plugins one by one activate native session plugin and then re-enable all other plugins? To see if the error on activating native php session plugin disappears?

    Yes, something like this.

    Sorry I can’t be more help at this point. If you identify a specific issue with WP Native PHP Sessions, I’d be happy to look at it. Other than that, this is somewhat outside of what we provide support for.

    Thread Starter priesterath

    (@priesterath)

    5 years, 10 months ago

    Ok, but …;-)
    I tested the installation on 3 different WP Installations, all throw errors, when activation your plugin. I think the problem is your plugin not an interfering one.

    Perhaps this warning may help to solve the problem. (I shortened the path)

    Warning: ini_set(): A session is active. You cannot change the session module’s ini settings at this time in /wp-content/plugins/wp-native-php-sessions/pantheon-sessions.php on line 127

    Warning: ini_set(): Headers already sent. You cannot change the session module’s ini settings at this time in /wp-content/plugins/wp-native-php-sessions/pantheon-sessions.php on line 136

    Warning: session_name(): Cannot change session name when session is active in /wp-content/plugins/wp-native-php-sessions/pantheon-sessions.php on line 140

    Warning: ini_set(): Headers already sent. You cannot change the session module’s ini settings at this time in /wp-content/plugins/wp-native-php-sessions/pantheon-sessions.php on line 148

    Warning: ini_set(): Headers already sent. You cannot change the session module’s ini settings at this time in /wp-content/plugins/wp-native-php-sessions/pantheon-sessions.php on line 149

    Warning: ini_set(): A session is active. You cannot change the session module’s ini settings at this time in /wp-content/plugins/wp-native-php-sessions/pantheon-sessions.php on line 150

    Warning: ini_set(): A session is active. You cannot change the session module’s ini settings at this time in /wp-content/plugins/wp-native-php-sessions/pantheon-sessions.php on line 153

    Warning: ini_set(): Headers already sent. You cannot change the session module’s ini settings at this time in /wp-content/plugins/wp-native-php-sessions/pantheon-sessions.php on line 155

    Warning: ini_set(): A session is active. You cannot change the session module’s ini settings at this time in /wp-content/plugins/wp-native-php-sessions/pantheon-sessions.php on line 157

    Warning: Cannot modify header information – headers already sent by (output started at /wp-content/plugins/wp-native-php-sessions/pantheon-sessions.php:127) in /wp-admin/includes/misc.php on line 1282

    Warning: Cannot modify header information – headers already sent by (output started at /wp-content/plugins/wp-native-php-sessions/pantheon-sessions.php:127) in /wp-admin/admin-header.php on line 9

    Plugin Contributor Daniel Bachhuber

    (@danielbachhuber)

    5 years, 10 months ago

    Hi @priesterath,

    I tested the installation on 3 different WP Installations, all throw errors, when activation your plugin. I think the problem is your plugin not an interfering one.

    Perhaps this warning may help to solve the problem. (I shortened the path)

    The problem is that something else in your codebase (another plugin, your theme, maybe something else), is starting a PHP session before WP Native PHP Sessions is loaded. If you want to use WP Native PHP Sessions, then you’ll need to track down how that’s happening.

    Thread Starter priesterath

    (@priesterath)

    5 years, 10 months ago

    Ok, I will a have an eye on it and let you know if I find out.

    Btw the problem only occurs when the plugin gets activated. If I log in later all seems to be fine. Is it possible to see if WP Native PHP session is up and running and turn on a debug log?

    Plugin Contributor Daniel Bachhuber

    (@danielbachhuber)

    5 years, 10 months ago

    Oh. If it only happens when the plugin gets activated, then I wouldn’t worry about it too much.

    Is it possible to see if WP Native PHP session is up and running and turn on a debug log?

    Not sure what you mean by a debug log. Can you explain further?

    Thread Starter priesterath

    (@priesterath)

    5 years, 10 months ago

    A log where I can see, what WP Native PHP session is doing. If it throws errors or working fine. Something like this.

    Plugin Contributor Daniel Bachhuber

    (@danielbachhuber)

    5 years, 9 months ago

    Ok. WP Native PHP Sessions doesn’t have a log like that. The PHP errors are generally accurate for that; without errors, the plugin is probably correctly configured.

Viewing 11 replies - 1 through 11 (of 11 total)

The topic ‘warning when installing on wp 5.4.2’ is closed to new replies.