Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • April 20, 2016 at 11:41 am #618200
    codecreative

    hi when using twenty fifteen theme or any other theme my site is okay

    when I use enfold I get this error

    Warning: session_start(): Cannot find save handler ‘memcache’ – session startup failed in /var/sites/s/skindesignlondon.com/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/masonry_entries.php on line 32

    Warning: session_start(): Cannot find save handler ‘memcache’ – session startup failed in /var/sites/s/skindesignlondon.com/public_html/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/portfolio.php on line 27

    It’s happened with two versions of enfold including 3.5.1 and the latest one 3.5.3

    My server normally runs fine with enfold please help

    April 20, 2016 at 5:01 pm #618489
    Jordan

    Hey codecreative!

    Thanks for getting in touch with us!

    Could you please provide a link and login details to your site, so that we can have a closer look. You can place the information in the Private Content section of your reply.

    Regards,
    Jordan

    January 13, 2017 at 6:02 pm #733263
    Cliffy

    Hi, I have just encountered this same error.

    I’ve updated my theme and WP to the very latest 3.8.4 and 4.7.1 but I also ran WP-Sweep across the board. I’m going to go back to a backup but thought I would comment in case anyone knew what the issue was. (Oh, I also changed PHP from 5.3 to 7 but switching back doesnt fix it).

    Oh the joys … :)

    Update: I went back to a backup – went through the process again, got the same error but I didn’t run sweep, it wasnt there. There was some referral to sweep plugin though “The plugin wp-sweep/wp-sweep.php has been deactivated due to an error: Plugin file does not exist.” so what backup my hosting company restored, I don’t know. Back up and running again with the site and latest versions lol

    • This reply was modified 7 years, 3 months ago by Cliffy.
    January 15, 2017 at 7:13 am #733696
    Rikard

    Hi @Heathcliffe,

    Thanks for the feedback, so I’m guessing you solved the problem?

    Best regards,
    Rikard

    January 28, 2017 at 6:55 pm #739732
    Cliffy

    @rikard @codecreative

    I got to the route of the issue. It all stems from the /var/sites/s/ which is reference to Vidahost Hosting. The setting is implemented on Auto Install of WordPress. I could see clearly this was set in the Media Folder settings. After an initial auto install, Vidahost say it is ok to delete this setting. I don’t understand the technical reasons for doing this, but there is a clue for anyone else with errors relating to /var/sites/ .

    Hope it Helps.

    January 29, 2017 at 6:40 pm #739997
    Basilis

    Hey!

    We are sorry for that, but some times hosting providers make their installations to be fast and not always care
    on how to make sure everything is working properly.

    We are happy you got it solved!
    Please feel free to let us know if we can do anything else for you,

    Best regards,
    Basilis

  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.