"Error creating access file in the /pages directory (insufficient privileges)"

[evildmp]

I'm pretty sure this is not a permissions issue. (I have checked permissions - they seem fine.)

It occurs when I try to move a page to a new parent.

I think it is because WB is trying to do things in the /pages directory, but I don't use a /pages directory.

If I copy the directory hierarchy that I'm trying to change into /pages, and change "Pages Directory:" in Advanced Settings (to /pages), it will successfully move the page.

So it looks to me as though some part of WB is ignoring the fact that my "Pages Directory" setting is left blank, and is expecting to find the things it needs to move in /pages rather than in /.

It is generating the insufficient privileges error (I think) because it is trying to move a directory to a path that doesn't exist.

Thanks for any help.

[BerndJM]

Hi,

WB Version?

Regards Bernd

[marathoner]

Where are you trying to move to? What are the permissions?

Also, what exactly are you trying to move? You didn't explain what you are doing...but it almost sounds like you are taking an 'non-WB' web site and trying to move this to a 'WB' web site? Is that correct? If so, that won't work as all page information is stored in database.

Any 'moving' of pages needs to be done in the WB backend and not via FTP. Any page 'copying' should be done using an addon like 'page clone'.

[ruebenwurzel]

Hello,

changing /pages directory in Wb  options should only be made before the first page is created. Trying to do this afterwords could brake the page. If you do it, when pages are created you also must rename the /pages folder to the new name.

Using a pages directory from another WB installation, no matter wich name it has and wich name you give in wb options did never work as the related database entries are missing.

So as marathoner wrote, please give us more information what exactly you do.

Matthias

[evildmp]

I'm pretty sure this is not a permissions issue. (I have checked permissions - they seem fine.)

It occurs when I try to move a page to a new parent.

I think it is because WB is trying to do things in the /pages directory, but I don't use a /pages directory.

If I copy the directory hierarchy that I'm trying to change into /pages, and change "Pages Directory:" in Advanced Settings (to /pages), it will successfully move the page.

So it looks to me as though some part of WB is ignoring the fact that my "Pages Directory" setting is left blank, and is expecting to find the things it needs to move in /pages rather than in /.

It is generating the insufficient privileges error (I think) because it is trying to move a directory to a path that doesn't exist.

Thanks for your replies, here's some more information:

I'm using version 2.6.5 - I've been running this site on WB for years. Last night I tried to move a page, and that wouldn't work (it wasn't a problem before).

By "move a page", I mean assign it to a new parent.

Since, in Advanced Settings, "Pages Directory" is not set to "/pages", I don't know why I should get an error message referring to it.

It made me think that WB was trying to create or modify the directory structure within it.

To test that idea, I temporarily copied (at the shell command line) a section of the directory structure from / to /pages, and I changed the Advanced Settings for "Pages Directory" to "/pages".

After doing that, I was able to reset a page's parent for that section of the site without errors. This was just for the purposes of testing.

So it seems to me that when WB needs to write to the directory structure for pages, it's doing it in the wrong place.

I haven't had a a chance to examine the MySQL tables, but I will do that later to see if I can see any clues as to why.

[ruebenwurzel]

Hello,

the use of the pages option in WB versions prior then WB 2.7 was very buggy. Mains issue was that the pages dir was hardcoded as /pages in a lot of wb files. So in all versions of WB prior to WB 2.7 we strongly recommanded not to use this option in wb settings and let the pages dir to default /pages. Otherwise you run in problems for shure.

Second possible issue is that setting pages dir to "/", wich means root, only works (in all wb versions including WB 2.7) only if the server config from your hoster allows to create with scripts files and folders in the root dir. This is on most servers not possible.

You may say this worked before. Yes, could be. Creating pages in pages dir, then setting pages dir in options to root and move with ftp the content of pages dir to root makes the page working even on those servers where no write access for scripts is on root. But as soon as you try then to add pages or move pages it doesn't work and you got errors.

Matthias

[evildmp]

I'm pretty sure this is not a permissions issue. (I have checked permissions - they seem fine.)

I am embarrassed to report that I have discovered the cause of the problem: user (i.e. me) incompetence.

I'm very sorry to have wasted everyone's time.

Yes, the file permissions were correct - in every directory except the WB root directory. For some reason, I managed to check, set, recheck and reset permissions, and each time I failed to notice that I hadn't included the root directory.

Sorry once again.

[deeve007]

I'm pretty sure this is not a permissions issue. (I have checked permissions - they seem fine.)

I am embarrassed to report that I have discovered the cause of the problem: user (i.e. me) incompetence.

I'm very sorry to have wasted everyone's time.

Yes, the file permissions were correct - in every directory except the WB root directory. For some reason, I managed to check, set, recheck and reset permissions, and each time I failed to notice that I hadn't included the root directory.

Sorry once again.

Mate, champion!! Was having the same issue, checked permissions on all required folders... but yes, forget the "public_html" folder!

Cheers!!