Only top ordered page displays, 500 error on all others

[Anlina]

I'm working on setting up my first install of WB and everything went pretty smoothly up until I started creating pages.

My first page displayed just fine, but every additional page I create gives me a 500 server error.

I did a little testing with reordering the pages, and which ever page is at the top of my list displays properly. All others give me the same error.

Basically, as far as I can tell, accessing the domain via the index page is fine, but trying to view any of the pages at /pages/pagename.php is totally broken.

Any ideas on why this is happening or how to fix it?

You can view my test site to see exactly what is going on.

http://diane.anlinasheng.com/

[ruebenwurzel]

Hello,

check the permissions of your /pages dir. It seems that scripts are not allowed to create the necessary page files in pages dir.

Also have a look to the requirements of WB (Server does not run with "safe mode on") and read our doku about filepermissions on our help page.

Matthias

[Anlina]

Thank you - I manually changed the file permissions on the pages I had already created and they are viewable now.

Now, when I create a new page the permissions are still set wrong - is that something that needs to be fixed in websitebaker, or something that needs adjusting on the server end?

Safe mode does appear to be off according to phpinfo.

[kweitzel]

That needs to be fixed serverside ... I would ask your hoster, what uid and gid (user and group id) and what default permissions the files created via PHP get. It looks like this is on purpose to diable "malicious" fileuploads / executions.

cheers

Klaus

[Anlina]

Okay, I contacted my host, but it actually was an issue with the WebsiteBaker settings (and I don't think it was a fluke - I did three complete installs and encountered the same issues each time.)

Anyway, the permissions issue was caused by a value in the "settings" table.

setting_id: 38
name: string_file_mode

The value variable was set to 0666. This was on a fresh install into an empty database, so there wasn't any setting that I played around with to create this issue after installation.

Anyway, I changed this variable to 0755 and everything seems to be fixed with respect to this problem.