session_start() errors

  • Resolved hallcp

    (@hallcp)


    7 years, 10 months ago

    Custom-Sidebars is causing “session_start” errors for me. This has been going on at least back to 4.7.1, the 4.7.2 upgrade made no difference. But it used to work for us at some point in the past.

    I have downloaded a fresh copy of custom-sidebars, 2.1.1.9. We are running PHP 5.3.6. I get the same error regardless of the theme (twentyeleven, etc.)

    And when I view source:

    <br />
    <b>Warning</b>: session_start() [function.session-start.html]: open(/nas/scratch/sww_php_sessions/sess_f8fc9ba3645a728e2e6f5af4bccc1307, O_RDWR) failed: No such file or directory (2) in <b>/r/hoover/vol/vol8/blogs/public_html/wp.dev/wp-content/plugins/custom-sidebars/inc/external/wpmu-lib/inc/class-thelib.php</b> on line <b>145</b><br />
    <br />

    Not sure if that first “<br />” is the problem, or just part of the error message. I’m fairly baffled at this point. Anybody have any ideas?

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

  • Hi @hallcp,

    Our developers are currently working on some improvements on that part however I would like to perform some additional test in order to be sure we got this right.

    Can you give us some more info on where exactly are you seeing these because I’m unable to replicate the issue using the PHP 5.3.29?

    Cheers,
    Predrag

    Thread Starter hallcp

    (@hallcp)

    Thanks Predrag. I am attaching a screen shot of the page and the View Source.

    Error displayed
    View Source

    The readme.txt of our plugin says:

    Tested up to: 4.7
    Stable tag: 2.1.1.9

    We have used this successfully in the past, so it’s possible there are existing sidebars in the database. Could that be an issue? Where would I look to delete them?

    Sorry I can’t be more help. I’m stumped.

    Hi @hallcp,

    Thanks for the information, I will forward this to our developer so he can check it out before the release and hopefully the new version will take care of this for you.

    Database sidebars shouldn’t be an issue because on my test site I change them quite frequently and remove and add new ones without seeing such issue.
    They should be all stored in cs_sidebars inside wp_options table.

    Cheers,
    Predrag

    Thread Starter hallcp

    (@hallcp)

    FIXED! This turned out to be a missing directory. We have PHP configured to store session data in a particular directory… and somebody deleted it.

    So sorry to have falsely accused poor Custom_Sidebars. It was completely innocent. It just happened to be the first snippet of code to try and begin a session.

    You’d think I’d have gotten errors from all over the place, but maybe WordPress turns off the warnings at some point.

    In any case, Custom_Sidebars was not the culprit here.

    Thanks so much for posting Predrag. It makes me feel very good about CS support.

    Charles.

    Thank you for the update @hallcp! Glad you got it working.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘session_start() errors’ is closed to new replies.