Issue when upgrading 1.0 to 1.3 - no page displayed

mwa · Post by **mwa** » Fri Nov 21, 2008 12:31 am

Hello,

I just did an upgrade of serendipity on my webserver and
unfortunatly my pages are not displayed anymore

website is : www.noahdeveley.com

i don't have any clue of the issue as the upgrade tool just
asked if I wanted to update the database and all seems fine.

So it could really help if you have any idea of where the issue could come
from, because I've no error message and I can't access to the admin
page as it's also not displayed

thanks for your support

Best regards

Sly

judebert · Post by **judebert** » Fri Nov 21, 2008 3:52 am

The blank white screen usually means something has gone wrong on the server. If you have access to the error logs, they'll often say exactly what the problem is.

Since s9y 1.3 is known to work well, I can think of only two easy explanations: first, something in the .htaccess could be invalid for your server. Start by backing it up, then removing it.

Second, the newer version of s9y could be using more memory than the old. You may need to increase the amount of memory available for PHP processes. This can be done in the php.ini, but some servers allow you to do it in the .htaccess. You'll have to ask your server to find out where you should do it.

Good luck. If neither of these work, we'll see what else we can do.

mwa · Post by **mwa** » Fri Nov 21, 2008 1:52 pm

So I tried the .htaccess and it doesn't change nothing.

I will ask the hosting company for the php.ini, but I don't think that they will do anything.

As usual, I didn't do a backup before the overwriting of the files and the database update.

Is there any temporary work around ?

What are the other tests, not depending on the hoster I could do ?

Content of the database ?, pages?

I don't have access to the logs, but how could we track the errors that
might occur

Thanks in advance

Sly

judebert · Post by **judebert** » Fri Nov 21, 2008 2:37 pm

We've got to figure out what's going on; for that, we need PHP to tell us the problem.

Depending on your hosting service, you might be able to enable error logging in your .htaccess. I found a great article about it at http://perishablepress.com/press/2008/0 ... -htaccess/.

To get the most error information, add this to your .htaccess:

Code: Select all

php_flag display_startup_errors off
php_flag display_errors off
php_flag html_errors off
php_value error_reporting integer 8191

You probably don't want these errors to be displayed for long, since they might give away information about your host. Change the .htaccess, access your website, and put the .htaccess back the way it was. Then tell us what errors are displayed, and we'll see where we can go from there.

kleinerChemiker · Post by **kleinerChemiker** » Fri Nov 21, 2008 2:50 pm

judebert wrote:We've got to figure out what's going on; for that, we need PHP to tell us the problem.

Depending on your hosting service, you might be able to enable error logging in your .htaccess. I found a great article about it at http://perishablepress.com/press/2008/0 ... -htaccess/.

To get the most error information, add this to your .htaccess:
Code: Select all
php_flag display_startup_errors off
php_flag display_errors off
php_flag html_errors off
php_value error_reporting integer 8191
You probably don't want these errors to be displayed for long, since they might give away information about your host. Change the .htaccess, access your website, and put the .htaccess back the way it was. Then tell us what errors are displayed, and we'll see where we can go from there.

you copied the wrong code. The right code is:

Code: Select all

# PHP error handling for development servers
php_flag display_startup_errors on
php_flag display_errors on
php_flag html_errors on
php_flag log_errors on
php_flag ignore_repeated_errors off
php_flag ignore_repeated_source off
php_flag report_memleaks on
php_flag track_errors on
php_value docref_root 0
php_value docref_ext 0
php_value error_log /home/path/public_html/domain/PHP_errors.log
php_value error_reporting 999999999
php_value log_errors_max_len 0

<Files /home/path/public_html/domain/PHP_errors.log>
 Order allow,deny
 Deny from all
 Satisfy All
</Files>

judebert · Post by **judebert** » Fri Nov 21, 2008 3:07 pm

Duh. I was deriving those myself, and meant to change them to "on". Thanks for the assist!

mwa · Post by **mwa** » Fri Nov 21, 2008 5:44 pm

Thanks,
there's a final error in the script,php_value was missing in the last line

I'll check the logs and keep you posted

# PHP error handling for production servers
php_flag display_startup_errors off
php_flag display_errors off
php_flag html_errors off
php_flag log_errors on
php_flag ignore_repeated_errors off
php_flag ignore_repeated_source off
php_flag report_memleaks on
php_flag track_errors on
php_value docref_root 0
php_value docref_ext 0
php_value error_log path/to/PHP_errors.log
php_value error_reporting 999999999
php_value log_errors_max_len 0

<Files /path/to/PHP_errors.log>
Order allow,deny
Deny from all
Satisfy All
</Files>

mwa · Post by **mwa** » Fri Nov 21, 2008 5:55 pm

Hello,

so it seems that there's an error with the template, I've several time the following 2 error messages.

and my issue is that I don't have the kubrik template in the "template_c" folder but only in the "template" folder, is it normal ?

(thanks already a lot for you help !!!!, the logs are just helping much than any other tries)

[21-nov-2008 17:49:40] PHP Warning: Smarty::fetch() [0function.include0]: Failed opening '/var/www/vhosts/noahdeveley.com/httpdocs/templates_c/kubrick^%%07^07C^07C1328C%%content.tpl.php' for inclusion (include_path='.:/usr/share/pear:/mnt/nfs/vhosts/noahdeveley.com/httpdocs/bundled-libs/:/mnt/nfs/vhosts/noahdeveley.com/httpdocs/bundled-libs/Smarty/libs/:/mnt/nfs/vhosts/noahdeveley.com/httpdocs/:') in /mnt/nfs/vhosts/noahdeveley.com/httpdocs/bundled-libs/Smarty/libs/Smarty.class.php on line 1262

[21-nov-2008 17:49:41] PHP Warning: Smarty::fetch() [0function.fetch0]: open_basedir restriction in effect. File(/var/www/vhosts/noahdeveley.com/httpdocs/templates_c/kubrick^%%BA^BAF^BAF5A0AF%%index.tpl.php) is not within the allowed path(s): (/var/www/vhosts/noahdeveley.com/httpdocs:/tmp) in /mnt/nfs/vhosts/noahdeveley.com/httpdocs/bundled-libs/Smarty/libs/Smarty.class.php on line 1255

Post by **garvinhicking** » Sat Nov 22, 2008 12:10 pm

Hi!

You need to contact your provider, it seems that he configured open_basedir not properly. The real path is "/mnt/nfs/vhosts" but he put "/var/www/vhosts" into the open_basedir configuration, so s9y cannot access its files properly.

Regards,
Garvin

mwa · Post by **mwa** » Sat Nov 22, 2008 7:27 pm

hi,

is it possible to correct it also by changing the path in the script ?

'cause I'm really not sure that the hosting company will change the
open_basedir

Anyway I will ask, but if I can change parameter in files already
it could make the blog alive again

and by the way I didn't have this issue with the previous version...strange

Best regards

Sly

Post by **garvinhicking** » Sun Nov 23, 2008 12:57 am

Hi!

No, the right path needs to be entered in the PHP config, it's the actual path that needs to be enabled ther.e It's definitely an error frmo your hoster.

Regards,
Garvin

mwa · Post by **mwa** » Sun Nov 23, 2008 10:07 pm

Hello,

so it's seems that the hosting platform is running under plesk
which have the hosts under /var/www so no chance for the hoster to change it,.
If I run phpinfo(); I've got following results :

open_basedir /var/www/vhosts/noahdeveley.com/httpdocs:/tmp
DOCUMENT_ROOT /var/www/vhosts/noahdeveley.com/httpdocs

so it seems that /mnt/nfs/vhosts is not the real path on this server

I've checked and seems there's no trick to do with .htaccess this time, so
again, is it possible to do a little hack and force the value of this path somewhere?

is there new functions on the version 1.3 that use this value, because I didn't have the issue before...

thanks for your help

Post by **garvinhicking** » Mon Nov 24, 2008 11:31 am

Hi!

/mnt/ IS the real path! The PHP realpath function (http://de3.php.net/manual/en/function.realpath.php) returns it, and to this directory the open_basedir must be included.

If it is not, it is clearly a hosting setup error.

is there new functions on the version 1.3 that use this value, because I didn't have the issue before...

Smarty uses realpath, so it should've been this way like forever. Maybe your hoster changed the filesystem mappings, this is more likely to be the cause?

Regards,
Garvin

mwa · Post by **mwa** » Mon Nov 24, 2008 11:40 pm

Hi all,

the web hoster just migrate me to another server,
where it seems not to have this mapping issue.

After asking to change the config, they admit they have some config issue.

So I would like to thank you all for your kind support for this issue

the blog of my godson is back up and live

thank you a lot I wish you a good week

Best regards

Sly