Error: "The export directory is not writeable"

[cb3211]

I get this error on my forum whenever anyone visits Profile > Actions

Example link: ../index.php?action=profile;area=getprofiledata;u=

(screenshot also attached)


The forum is a fresh install of 2.1 using default them and no modifications.

[Doug Heffernan]

I get this error on my forum whenever anyone visits Profile > Actions

Example link: ../index.php?action=profile;area=getprofiledata;u=

(screenshot also attached)


The forum is a fresh install of 2.1 using default them and no modifications.

Can you chmodd the Profile-Export.php file? If the error will not go away, try to chmodd all the profile files inside the /Sources directory and see if it will help.

[Arantor]

The export isn't about Profile-Export.php but the exports/ folder it tries to make, which should be writable - perhaps it should be manually created and given chmod for editing.

[Doug Heffernan]

The export isn't about Profile-Export.php but the exports/ folder it tries to make, which should be writable - perhaps it should be manually created and given chmod for editing.

Right, but yesterday while I was doing some work on a forum for a member here, coincidentally one of the things, among other stuff that I had to fix, was this very same issue. I had to chmodd all the profile files for the error to go away. Hopefully that will work for the OP as well.

[Arantor]

You get the 'the exports folder is not writable' error because Profile-Exports.php has the wrong chmod? WTF?

[Sesquipedalian]

Changing the permissions on the Profile-Export.php file definitely will not make any difference here. The problem is exactly what the error message says: the exports directory cannot be written to.

To fix it, the permissions on the directory need to be changed so that it becomes writable. Under most conditions, SMF will automatically take care of this itself. But if the permissions on both the exports directory and the forum's root directory are especially restrictive, it may be necessary to do the job manually, as @Arantor rightly said.