XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk
  1. Board index / 
  2. XOOPS Community Support forums / 
  3. Installation Troubleshooting 
  4.  / Upgrade to 2.0.14 went south
Register
1
ViperSBT
Upgrade to 2.0.14 went south

  • 2006/6/30 7:05

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


Upgraded from 2.0.13 to 2.0.14, went through all the steps and everything appears to have gone normal, but when I go to the site everything is blank. I am not getting any errors that I can identify, but all the pages come up blank. If I force it to admin.php it takes me there and allows me to login with my password.

All of the preferences links show nothing or send me back to the previous screen. The rest of the admin section appears to work normally... What gives?

PHP 4.4.1
Apache 2.0.54
MySQL 4.1.16
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com
2
ViperSBT
Re: Upgrade to 2.0.14 went south

  • 2006/6/30 12:57

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


I have gone into recovery.php and set debugging to 1 and still not getting any additional errors that are showing what is the problem. As backup insurance I edited common.php to for error reporting to E_ALL, and still not getting any errors either on screen on in my phperror.log.

I then checked my php.ini settings. I had Display_Errors = Off, but I was using Error_Logging. So just to follow the FAQs I enabled Display_Errors and restarted Apache, still nothing.
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com
3
ViperSBT
Re: Upgrade to 2.0.14 went south

  • 2006/6/30 13:14

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


I have turned on Register-Globals which did nothing.

I made sure the cache directory was properly CHMODed. While looking in the cache directory I noted that there was a backend.php cache. I executed the backend.php script and it displayed properly.

Uploaded and changed back to phpkaox theme to see if it was a theme problem and still nothing.

Made sure that the cache, uploads, templates_c directories are CHMOD 777, still nothing.
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com
4
ViperSBT
Re: Upgrade to 2.0.14 went south

  • 2006/6/30 13:46

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


I've completely gone through the system and re-CHMODed all files and directories to appropriate settings, still nothing.

I've disabled all modules, still nothing.

I tried going to user.php and was redirected to userinfo.php?uid=3 but the page was still blank and no errors were generated.
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com
5
ViperSBT
Re: Upgrade to 2.0.14 went south

  • 2006/6/30 14:23

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


I have tested that the webserver will generate and report errors by testing some small scripts of my own. But still not getting anything from XOOPS but the blank page.

I have reviewed the mainfile.php and cleaned it up to resemble the dist.php. Basically this involved removing old protector script that was added to mainfile. But still not getting anything.
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com
6
Bender
Re: Upgrade to 2.0.14 went south

  • 2006/6/30 14:38

  • Bender

  • Home away from home

  • Posts: 1899

  • Since: 2003/3/10


How about renaming your XOOPS folder and uploading a fresh XOOPS 2.0.14 to see if that works at all.

(using a different database or at least different files of course)

So you know if its caused by the updated or if really XOOPS 2.0.14 does not work with this specific server configuration.
Sorry, this signature is experiencing technical difficulties. We will return you to the sheduled signature as soon as possible ...
7
leostotch
Re: Upgrade to 2.0.14 went south

  • 2006/6/30 17:42

  • leostotch

  • Just popping in

  • Posts: 76

  • Since: 2006/4/1 1


Quote:
I have gone into recovery.php and set debugging to 1 and still not getting any additional errors that are showing what is the problem. As backup insurance I edited common.php to for error reporting to E_ALL, and still not getting any errors either on screen on in my phperror.log.


I think it is not enough as error reporting is disabled in other places too. The only safe way to enable debug mode when you don't have access to the admin interface is by changing the config value manually in the DB (as indicated in the "troubleshooting blank page" FAQ if I remember).
Also, complete blank pages can often be the consequence of PHP parse errors. Did you check that you uploaded your files correctly using the file integrity checking script ?
8
ViperSBT
Re: Upgrade to 2.0.14 went south

  • 2006/6/30 17:54

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


I guess I need to cover my steps. I used wget to pull the tar.gz version of the 2.0.14 package to my server. I then untarred the package, deleted the mainfile.php from the htdocs directory and did a 'cp -Rf * /www/htdocs/'.

With that said I don't see how I could have any corrupted files. But, take a look at my MD5 check: http://www.u-fli.com/xoops_md5.php

There are way too many "content invalid" files to list here. What did I do wrong?
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com
9
ViperSBT
Re: Upgrade to 2.0.14 went south

  • 2006/6/30 17:57

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


I checked the debug value in the database and it is: a:1:{i:0;s:1:"1";}

So, I have to assume that recovery.php did its job and set it appropriately.
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com
10
leostotch
Re: Upgrade to 2.0.14 went south

  • 2006/6/30 18:28

  • leostotch

  • Just popping in

  • Posts: 76

  • Since: 2006/4/1 1


Quote:
There are way too many "content invalid" files to list here. What did I do wrong?


Don't know... that's weird. That's what I did too, with no problem.
I just tried to redo an install quickly, dloading the tgz again, untarring and all, and everything goes fine (well, xoops_md5.php tells me 3 files are invalid but I saw in another thread it's due to a packaging error in the tgz and can be ignored).
So I don't know... I think you should try the upg again (get a new package, and do the copy again). Maybe you could try to check your new files perms too (owner and chmoding).
(1) 2 3 »

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

338 user(s) are online (221 user(s) are browsing Support Forums)

Members: 0

Guests: 338

more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Nov 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits