timgno wrote:
...
I made a mistake!

But the download of the green button sourceforge leads to xoops 2.5.6, not 2.5.7
...

Warning: include_once(C:\Users\Angelo Rocha\Documents\wamp\www\x257\modules\pm\admin../../../include/cp_header.php) [function.include-once]: failed to open stream: No such file or directory in C:\Users\Angelo Rocha\Documents\wamp\www\x257\modules\pm\admin\about.php on line 20

( ! ) Fatal error: Call to undefined function xoops_load() in C:\Users\Angelo Rocha\Documents\wamp\www\x257\class\xoopsformloader.php on line 20

Warning: include_once(C:\Users\Angelo Rocha\Documents\wamp\www\x257\modules\profile\admin../../../include/cp_header.php) [function.include-once]: failed to open stream: No such file or directory in C:\Users\Angelo Rocha\Documents\wamp\www\x257\modules\profile\admin\about.php on line 20

geekwright wrote:
Sounds like a permission issue

Can you change the permissions of the root directory? If yes, you could try setting the main xoops directory writable long enough to run the install, and setting it back when you are done.

What type of OS is this running on?

Most hosting companies now use suPHP servers, thus 755 will allow PHP to read, write and execute scripts just like 777 does. Because of this, most scripts work when you use 755.

geekwright wrote:
The 500 error might be the server objecting to world write. A 775 permission might make it happy. But, I can't verify that.

Let's try this. Create a mainfile.php file with the following:

if (! defined('XOOPS_INSTALL')) {
    header('Location: install/index.php');
}

Upload that to the root directory and set the file permission to 777, then retry the install.

If this works, we can add a file to extras, so we have a solution ready for problematic servers. I use Linux almost exclusively for development and production, and I don't have any environments where this is a problem. Even my Windows boxes seem happy with the changes. But there are always other ways to configure systems.

The whole reason for this change was to make it impossible to accidentally overwrite mainfile.php while upgrading a production system. If you've ever done that, it is a great way to induce panic and ruin an otherwise good day (OK, I am speaking from experience, I admit it, but I won't put a number on how many times I've done it.)

Sorry this is such a problem.


Edited to add this from support.hostgator.com:

Quote:

Most hosting companies now use suPHP servers, thus 755 will allow PHP to read, write and execute scripts just like 777 does. Because of this, most scripts work when you use 755.

suPHP solves the whole problem. Too bad they are not "most hosting companies"