Content Plus pages not displaying (blank page)

Hangin' Around Joined: Nov 12, 2006 Posts: 41

I have a fresh Installation of RavenNuke_v2.40.00 that includes the script Content Plus. The issue is when I'm attempting to look at a Content Page. I can create the page just fine, and Edit it, but when you go to look at the page itself, I get a blank page (The website cannot display the page). If I desactive the page I can see it (as admin only) -- but if activated I can not see it (as admin or user).

MySQL version 4.1.22-standard
PHP version 5.2.8

Site http://portal.nosotros.com/portal/index.php

Please help. Thanks advance

Posted: Mon Jan 18, 2010 9:40 am

If you set
$display_errors = true;
in config.php do you get an error message?

Posted: Mon Jan 18, 2010 10:00 am

It was configured as
$display_errors = false;
I changed it now to
$display_errors = true;
and when trying to display the Content Plus page it shows:

Fatal error: Call to undefined function mb_internal_encoding() in /home/portaln/public_html/portal/includes/class.autokeyword.php on line 113

Posted: Mon Jan 18, 2010 10:39 am

are you sure you are running php5?
try adding this at the very top of
portal/.htaccess

Code:

AddHandler x-httpd-php5 .php


AddHandler x-httpd-php .php4

if that doesn't work you'll probably have to contact your host.
http://www.ravenphpscripts.com/postp143667.html

Posted: Mon Jan 18, 2010 11:00 am

I included your info and now the site download the index.php file...

Posted: Mon Jan 18, 2010 11:02 am

whoa ya thats not right... not sure where you added that, but it should be added to:
html/.htaccess

the top looks something like:
before:

Code:

#####################################################


#  READ THIS COMPLETELY IF YOU CHOOSE TO USE THIS FILE


#  THESE INSTRUCTIONS APPLY TO ALL Options DIRECTIVES


#


# The lines below this section that begin with Options may cause problems


# with some server configurations.  They are required for certain functions


# of Apache and RavenNuke(tm), but may already be set by your server administrator in a way


# that dissallows changing them in your .htaccess file.  If using any of them causes your server


# to error out, comment them out (add # to beginning of line), reload your site in your browser


# and test the functionality that is affected.  If it works, then it has been set by your server


# administrator and you do not need it set here.


#####################################################

after

Code:

AddHandler x-httpd-php5 .php


AddHandler x-httpd-php .php4 #####################################################


#  READ THIS COMPLETELY IF YOU CHOOSE TO USE THIS FILE


#  THESE INSTRUCTIONS APPLY TO ALL Options DIRECTIVES


#


# The lines below this section that begin with Options may cause problems


# with some server configurations.  They are required for certain functions


# of Apache and RavenNuke(tm), but may already be set by your server administrator in a way


# that dissallows changing them in your .htaccess file.  If using any of them causes your server


# to error out, comment them out (add # to beginning of line), reload your site in your browser


# and test the functionality that is affected.  If it works, then it has been set by your server


# administrator and you do not need it set here.


#####################################################

if that is where you added it and it's still behaving this way then remove it, contact your host and find out if mb_internal_encoding is enabled.

Posted: Mon Jan 18, 2010 11:05 am

I put it like this (only the beginning send here):

AddHandler x-httpd-php5 .php
AddHandler x-httpd-php .php4
#####################################################
# READ THIS COMPLETELY IF YOU CHOOSE TO USE THIS FILE
# THESE INSTRUCTIONS APPLY TO ALL Options DIRECTIVES
#
# The lines below this section that begin with Options may cause problems
# with some server configurations. They are required for certain functions
# of Apache and RavenNuke(tm), but may already be set by your server administrator in a way
# that dissallows changing them in your .htaccess file. If using any of them causes your server
# to error out, comment them out (add # to beginning of line), reload your site in your browser
# and test the functionality that is affected. If it works, then it has been set by your server
# administrator and you do not need it set here.
#####################################################

# 'Options +FollowSymLinks' is required for use of mod_rewrite.

Posted: Mon Jan 18, 2010 11:13 am

hmm ok, well you better remove it then Sad

Next step is to contact your host and find out if mb_internal_encoding is enabled.

Posted: Mon Jan 18, 2010 3:57 pm

Or if you go into the Forum administration are, I think there is a phpinfo() link so you should be able to search for it there.

Posted: Mon Mar 08, 2010 9:02 am

aespinal, Did you get to solve this?

Posted: Sat Mar 13, 2010 1:18 pm

It works fine, but created some issues in other php applications, like this gallery

Notice: Undefined offset: 8192 in /home/xxx/public_html/gallery/include/debugger.inc.php on line 112

Also, in oscommerce stores, we had to change functions to show errors to "off"

registered · Posted: Sat Mar 13, 2010 2:00 pm

You will want to change $display_errors back to false. It should only be set to true when trouble shooting, not on production sites.

Posted: Sat Mar 13, 2010 2:03 pm

what is your $error_reporting setting in rnconfig.php? The default setting should not display notices... I doubt it's related to enabling mb_internal_encoding.