Corrupted configurations.php (weird)

[SaucyWench]

The thread is going around in circles. I've used Freehostia and have no problem. In fact I had extensively modified a second server on Freehostia with no problems.

Try re-downloading 1.1.0 and reunpacking it and reuploading it, then get rid of all the modules, and then fix all the game settings. Make sure it all works. I expect it will! Then add the modules a few at a time.

[SaucyWench]

Can we get someone to turn on error reporting and see if anything comes up?

Has anyone contacted the host (who does provide support) to ask whether 51 means anything to them? It might be an error code they understand.

[ATN]

maybe freehostia servers can't handle too many modules when 1.1.1 is installed?

[Elessa]

without seeing actual error messages there is no way to tell.

[Iori]

without seeing actual error messages there is no way to tell.

My understanding is that the actually error message is a blank white screen with the number 51 on it.

[Elessa]

without seeing actual error messages there is no way to tell.

My understanding is that the actually error message is a blank white screen with the number 51 on it.

how absolutely bizarre.

[XChrisX]

That's the advanced version of a blank screen with a single 42 ...

[Elessa]

from googling this seems to me that PHP error reporting needs to be turned on in order to determine what is causing the error to be generated.

the PHP has been configued to not display any errors generated by PHP scripts. 

When you download PHP you find that two configuration files (php.ini files) are provided a default and a recommended. The recommended configuration has display of errors turned off. So as we see having a Blank Page is not the root problem. We need to dig deeper in order to determine the actual error before any fix can be determined.

Re-configuring PHP to display errors

To identify the root cause we need to get at the error being generated by PHP. How we do this depends on the level of access available to the server.

If you have access to update the server configuration then you can either alter your PHP configuration to turn on the displaying of errors to the browser or log errors to a file. To display errors in the browser set display_errors = On in php.ini. To log errors to a file set log_errors = On and provide a valid log file in error_log = filename (note 1)

If you don't have access to update the server configuration, the server you use is running apache and the server allows .htaccess files then the PHP configuration can be altered this way.

Create a .htaccess file in your PN root (with index.php, admin.php, user.php etc.). Turn on displaying of errors to the browser with

php_flag display_errors on

For other server configurations or problems with these directives seek help from either the server administrator, host, generic PHP support or operating system vendor.

What now?

You should now have access to the actual error generated either via the browser window or via the error log. At this point how you procede depends on the error message itself but it will have narrowed the places to look and avenues to seek further help on identifying the problem.

Notes
1) If on a windows server you can log errors to the server event log using error_log = syslog

[ThricebornPhoenix]

The thread is going around in circles. I've used Freehostia and have no problem. In fact I had extensively modified a second server on Freehostia with no problems.

Try re-downloading 1.1.0 and reunpacking it and reuploading it, then get rid of all the modules, and then fix all the game settings. Make sure it all works. I expect it will! Then add the modules a few at a time.

It works fine in 1.1.0. I just reinstalled my 1.1.1 and also installed 1.1.0. The former got 51'd, the latter did not. Then I did an upgrade from 1.1.0->1.1.1, and now that one gets 51'd as well.

Has anyone contacted the host (who does provide support) to ask whether 51 means anything to them? It might be an error code they understand.

Good idea. I just searched their forums and found the answer - apparently, Freehostia has some sort of content filter in place that outputs a page with numbers, depending on why it was blocked.

http://forum.freehostia.com/viewtopic.php?t=2137
http://forum.freehostia.com/viewtopic.php?t=924

In case you don't care to read those, the response was to submit a ticket.

You have to open a trouble ticket for this issue. We will assist you there in resolving the issue.

[SaucyWench]

Great, thanks for the detective work Thrice! I wonder what on earth could be triggering their filter in the settings... hopefully someone who's seeing this will submit a ticket and see what the staff have to say.

[Oridin]

If the configurations.php file is still not working properly and you KNOW that this is what the problem is than you should re-download the whole program, unzip the file, and copy that one file into your FTP

[Talisman]

If the configurations.php file is still not working properly and you KNOW that this is what the problem is than you should re-download the whole program, unzip the file, and copy that one file into your FTP

We have just established it's a server/host issue.  Please don't throw wild guesses out here...

[ThricebornPhoenix]

I just submitted a trouble ticket. And, because I was curious, I compared 1.1.0's configuration.php to 1.1.1's and recorded all the lines that had been added (I don't think any were removed). It all seems innocuous to me...

Update: upon receiving the following reply, I commented lines 267-274 ("paypalcountry-code"), and now it's not blocked.

Hello,

The'51' error is caused by our servers content filter,please check you page for words/phrases such: "Overdrafts"+"Business Services"+"Online Banking"+"Specialist Sectors","bank"+"of"+"ireland"+"Website","CAJA"+"MADRID"

When you find some , please remove then and this will unblock the page which is causing that issue.
Best Regards,
Jazzy