Blank pages when editing messages

Client Joined: Jan 29, 2004 Posts: 624

I'm running RN 2.30.02 on two domains. One is fine but on the new domain I am getting a blank page when I try to edit messages. The blank page just has the www.domain.com at the top. This happens too if I try to delete a message. It happens if I try to add a Weblink as well. Thanks for any ideas.

Posted: Thu Sep 10, 2009 2:41 pm

Have you tried turning error reporting on in the config.php file?

Posted: Thu Sep 10, 2009 3:09 pm

Not yet, I did look in the error log and saw a half dozen instances of

Quote:

[Thu Sep 10 13:43:02 2009] [error] [client xx.xxx.xx.xx] Premature end of script headers: /home/xxxxxxxx/public_html/admin.php

That's me as it is a zero traffic site. I uploaded a fresh admin.php but still a blank page. I'll turn on error reporting and look again.

registered · Posted: Thu Sep 10, 2009 4:46 pm

What theme are you using? If it's not a default RavenNuke theme, try switching themes and see if it works.

Posted: Thu Sep 10, 2009 5:33 pm

I'm using the fisubice theme which is default for RavenNuke, I switched from DeepBlue that is included with RN 2.30.02 but whichever theme I use I get a blank page when I click Edit message or try to add a weblink.

I turned on error reporting but nothing came up.

Posted: Thu Sep 10, 2009 5:41 pm

Usually that problem is due to a file with wrong permissions or a php file that was uploaded in binary instead of ascii.... I would check the file permissions and make sure they are 644 and reupload the file making sure it is in ascii in your ftp client. This may have nothing to do with it, these are just a few common causes for that error.

Posted: Thu Sep 10, 2009 5:56 pm

That is an idea as I do have binary set in my ftp client. I will also check permissions.

Posted: Thu Sep 10, 2009 6:27 pm

I checked permissions and set the /modules files and directories to 644 from 755 then re-u/led files. Still blank.

Posted: Thu Sep 10, 2009 6:51 pm

Most directories should be 755.... and the files 644...

Posted: Thu Sep 10, 2009 8:08 pm

Ah OK... just being thorough lol I'll set only files 644.

Posted: Thu Sep 10, 2009 8:28 pm

OK Directories 755 and files 644. Still a blank. Next?

Posted: Fri Sep 11, 2009 12:44 pm

Have you looked in the dblog (database error log, that you turn on in rnconfig)? Set it to loglevel=1 and try to edit your messages and see what turns up in that file. Any kind of table discrepancy can have the results that you are seeing.

Posted: Fri Sep 11, 2009 1:33 pm

I'll try that though I think log level 1 only records sql errors? It may be corrupt files from u/ling in binary so I may have to re-u/l all RN files with ascii. Its a good thing there is zero traffic as I have to do this a little at a time as time allows.

Posted: Fri Sep 11, 2009 1:59 pm

Yes, log level 1 just records errors. So, any table discrepancies will cause errors and you will see them. The output from loglevel 2 can be voluminous and you would be looking for a needle in a haystack so I don't encourage that except for developers who are looking to improve the efficiency of SQL.

Posted: Fri Sep 11, 2009 3:45 pm

I really don't know what this error means, but it sounds like a corrupt file to me.

registered · Posted: Fri Sep 11, 2009 8:36 pm

Looks to me like you may have modified a file somewhere, possibly one of the config.php files or mainfile.php or maybe a block file and didn't use a good text editor? Just "fishing" here...

Posted: Sun Sep 13, 2009 8:42 pm

No file mods as the site is too new. I think it may well be corrupt files so I'll re-u/l everything the next few days. Other things to do as well and it doesn't affect functionality so it's not a rush thing. I'll let you all know if re-u/ling fixes it.

Posted: Mon Sep 14, 2009 8:29 am

ok I guess I know what u did. Did u upload or edit files to www instead of public_html. If you do that then you screw that file and then it becomes corrupted. Let me know what u did and if u have these kind of folders.

Posted: Wed Sep 16, 2009 11:48 am

Absolutely not. I've always used the root for web accessible files. I u/led in binary by mistake and I'm going to re-u/l in ascii as soon as I get around to it. It's not my main domain but is just a "good deed" for a community so I haven't modded files.

Posted: Wed Sep 16, 2009 12:11 pm

If you can. Try updating to 2.4 and see if that helps this situation.

Posted: Wed Sep 16, 2009 8:36 pm

It's a release candidate at this point.