problem with mediawiki cookies

Question

anytime a user logs into our Wiki they get the following error: \"This Wiki uses cookies to log in users. You have cookies disabled. Please enable them and try again.\" Even

Answer 1

For future reference... We just had a similar problem on Appropedia (same error, but couldn't log in at all). It turned out the temp directory was full. Cleared the temp directory, problem solved.

Answer 2

Wikimedia's advice is

Check to make sure PHP's directory for storing session data is writable. This directory can be found in the php.ini file under the session.save_path setting. Errors in this php.ini setting can also cause other problems.

... (and) make sure the Internet Guest Account (eg. IUSR_FOOBAR, nobody, or apache) has write permissions to the folder listed in the session.save_path variable of the php.ini file.

Source.

If you are using a hosting site you need to edit your php scripting configuration (php.ini). The page should have information on your web document root. If there is already a "tmp" folder created then use it. If there is not a tmp folder in your current set up create one that is NOT browseable by users and tell the php.ini file the location as directed above.

Answer 3

If you are using NGINX + PHP-FPM the previous answers will likely not be of any assistance.

From the command line, run:

php-fpm -i|grep --color cookie_path

See what your cookie_path is, then stat the folder and ensure your php-fpm user has write access to it.

To resolve this issue using Nginx and Php-Fpm, I had to change my cookie_path from it's default of / (seriously, why would this be a default?) to /tmp.

After restarting nginx and php-fpm, it works perfectly.

Answer 4

Problem I just had was due to default install of our PHP using C:\windows\temp as a base folder for PHP session and other data.

Of course, once someone empties out the temp folder because its full of junk .... the sub-folders for PHP information go with it too :\

Answer 5

It turned out the temp directory was full

In my case it was because the entire partition was full, needed more space.