WordPress.org

Support

Support » Plugins and Hacks » [Plugin: Simple Twitter Connect] Switching from suPHP to dso triggers error

[Plugin: Simple Twitter Connect] Switching from suPHP to dso triggers error

  • I use suphp only when upgrading our multisite wordpress installation to make things quick. Everything was configured and working great. A few days later (this morning), I switched the php back to dso to conserve server resources. But after doing that I received the following errors on all pages (including admin):

    Warning: session_start() [function.session-start]: open(/tmp/sess_31e7619cfe4e01b208b1099beb3455ac, O_RDWR) failed: Permission denied (13) in /home/xxxxx/public_html/wp-content/plugins/simple-twitter-connect/stc.php on line 33
    
    Warning: session_start() [function.session-start]: Cannot send session cache limiter - headers already sent (output started at /home/xxxxx/public_html/wp-content/plugins/simple-twitter-connect/stc.php:33) in /home/xxxxx/public_html/wp-content/plugins/simple-twitter-connect/stc.php on line 33

    Switching back to suphp fixed the problem, switching back to dso triggers it again. I’ve never been required by a plugin to use suphp and don’t like using it full-time because it takes up server resources.

    Any suggestions?

    thanks!

Viewing 1 replies (of 1 total)
  • Plugin Author Samuel Wood (Otto)

    @otto42

    WordPress.org Tech Dude

    It’s hard to say what the specific problem is, but the general error is that PHP can’t set headers after something has already been sent to the browser. So something on your other server is causing output before the plugin runs and tries to start the session (which sends a cookie).

Viewing 1 replies (of 1 total)
  • The topic ‘[Plugin: Simple Twitter Connect] Switching from suPHP to dso triggers error’ is closed to new replies.