White page after trying to post on forums with admin account

New Member Joined: Jul 22, 2006 Posts: 18

Hi guys! I have searched the forums, but maybe I am not using the terminology correctly.

I have a fresh install of ravennuke 2.4. I have activated the forums in the modules admin, and I can see and create new categorys and forums but when I try to make a post with my god account, I get a white page.

Can anyone help? Thanks for your time!

*EDIT* I turned on error reporting and the error I now receive is

I turned on error reporting in the config.php and the error I receive is:

Fatal error: Call to undefined function: mb_internal_encoding() in /**path removed by admin**/includes/class.autokeyword.php on line 113

registered · Posted: Sun Nov 15, 2009 3:19 pm

http://www.ravenphpscripts.com/postp142079.html

Posted: Mon Nov 16, 2009 9:41 pm

"Dear Sir/Madam, Thank you for contacting online support. No, we only allow the php_mbstring.dll extension is only available with Dedicated and Virtual Dedicated server accounts. If you wish to have this feature you will need to upgrade to a virtual dedicated or dedicated server."

I have had no problem running any nuke on godaddy let along RN. Now I need to pay almost 30 bucks a month for something I did for 5?

Posted: Mon Nov 16, 2009 11:25 pm

i formerly had a hosting acct with godaddy. cheap prices but you get what you pay for. Slow sql servers, overloaded hosting, and a bunch of disabled settings instead of frequent patching and updates... Sad

Switched to http://www.ravenwebhosting.com/ and I've been happy ever since Smile

not sure what hosting package you need, but it will be alot cheaper than the $30mo godaddy quoting you.

registered · Posted: Tue Nov 17, 2009 6:43 am

b14ze, unbelievable! So, what GoDaddy is saying is that on their shared hosting plans, they basically will not allow true handling of UTF-8 and internationalization! How do they expect people to handle multi-byte character sets without the use of the mbstring extension?!?!?!?!?!?!?!

You know why they are saying this I suspect? It is so that they can pack more hosting clients onto the same server as multi-byte handling is going to take a little extra RAM and CPU. There is no other reason. Unfortunately, this is why you have countless people across the net complaining about the same things spasticdonkey has mentioned.

While I sympathize with your situation, if you continue to use cheap hosting, you are going to be left behind.

Someone more familiar with the internals of nukeSEO(tm) DH will have to comment on how it can be disabled without causing other issues. I think kguske is going to have to chime in on this one.

Posted: Tue Nov 17, 2009 8:19 am

Hmm. I installed phpnuke 8.0 and this works fine. Even the forums.. I installed it on a 5.x database.

After doing some research, I think what really is going on is THEIR .php ini. You can run either a 4.x database and a 5.x database and I don't believe they have the mb strings extension compiled into the old php.

Unfortunately I did try RN with a 5.x database and ended up with the same errors.

I'm afraid if I had to pay more then what I am paying for now my wife would kill me. I don't think I should have to. I am a long time customer of theirs and have tried a bunch of nuke distrobutions on this host. (with Ravennuke being my fave)

But if they can't figure out how to make it work for me, their customer, then I will seek out other hosting at a similar price.

I am such a noob tho, will I have to change my domain registration with them? I believe I pay for it by year...

Posted: Tue Nov 17, 2009 9:07 am

I hear what your saying, just my 2 cents. As for the domain name, it isn't an issue you can just login to the domain control panel @ godaddy and change the nameservers to your new hosting company (if you decide to change).

hmmm, if i remember right godaddy runs in php4 by default.. try adding this at the top of your htaccess

AddHandler x-httpd-php5 .php
AddHandler x-httpd-php .php4

i still actually have my godaddy acct and use it as a file server, or a small scale CDN. I have a test install of RN there so it should work (at least somewhat) Smile

thinking back, pretty sure I got that same error before I added that code to htaccess.

Posted: Tue Nov 17, 2009 10:03 am

@ spasticdonkey - if you still have that account, I would be VERY interested to see if a phpinfo() returns the same when you switch between PHP4 and PHP5 for mb_string availability.

Posted: Tue Nov 17, 2009 11:31 am

Yes I still have it.. Smile

Removed the add handler and i get this:
Fatal error: Call to undefined function: mb_internal_encoding() in /home/xxxxx/html/includes/class.autokeyword.php on line 113

was having some problems viewing the phpinfo when i downgraded to php4, but I have a screenshot of what is enabled at version php5.2.5 if your curious. Not sure if the htaccess changes had not fully propagated but kept only displaying phpinfo for version 5.2.5

obviously some sensitive info so if you interested just let me know where to email. I don't use the site for anything other than testing (and as a fileserver for my sites) so if the RN team is interested I could give them access to test stuff on a cheap godaddy server. let me know.

Posted: Tue Nov 17, 2009 12:06 pm

No thats ok. I was just curious to see if they were allowing mb_internal_encoding in PHP 4.x and not in PHP 5.x which negates their argument about it not being enabled, period.

New Member Joined: Jan 28, 2006 Posts: 1

spasticdonkey wrote:

I hear what your saying, just my 2 cents. As for the domain name, it isn't an issue you can just login to the domain control panel @ godaddy and change the nameservers to your new hosting company (if you decide to change).

hmmm, if i remember right godaddy runs in php4 by default.. try adding this at the top of your htaccess

AddHandler x-httpd-php5 .php
AddHandler x-httpd-php .php4

i still actually have my godaddy acct and use it as a file server, or a small scale CDN. I have a test install of RN there so it should work (at least somewhat) Smile

thinking back, pretty sure I got that same error before I added that code to htaccess.

I was having the same prob. so I added
AddHandler x-httpd-php5 .php
AddHandler x-httpd-php .php4
to my htaccess file and all works good.
So my question is what is this doing?
My server is running PHP Version 4.4.9 but they told me I can upgrade my server to PHP Version 5.0 if I like.
If i did that would it correct the prob. and I could remove the 2 lines?
What do you think?

Posted: Sun Oct 24, 2010 9:27 pm

It all depends with how they have php complied. If there is not a reason that you are using PHP 4 I would go with PHP 5.