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
11
Bender
Re: Upgrade to 2.0.14 went south

  • 2006/6/30 18:45

  • Bender

  • Home away from home

  • Posts: 1899

  • Since: 2003/3/10


- Download some of the invalid files and do a binary compare
- try unpackaging locally and uploading via ftp for a test
Sorry, this signature is experiencing technical difficulties. We will return you to the sheduled signature as soon as possible ...
12
ViperSBT
Re: Upgrade to 2.0.14 went south

  • 2006/6/30 22:09

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


I did a cmp and diff of the file in the tarball and the file in the website directory and received no variances between the two files.

I downloaded some of the files from the website directory to a local windows machine and then downloaded the .zip file from the repository, extracted the zip and then compared the files and found no differences...

So something besides a difference in the files must be causing the 'invalid content' and the blank pages.
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com
13
ViperSBT
Re: Upgrade to 2.0.14 went south

  • 2006/6/30 22:20

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


I tried starting from scratch on another website on the same servers that I had running an older version of XOOPS 2.0 and am getting the exact same condition. For the PHPINFO report see: http://www.toothnnail.com/phpinfo.php
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com
14
Bender
Re: Upgrade to 2.0.14 went south

  • 2006/6/30 23:05

  • Bender

  • Home away from home

  • Posts: 1899

  • Since: 2003/3/10


Arrghhhh!!! My eyes ... my eyes.
What a color selection is that?


Ok so it is PHP Version 4.4.1.


Which MySql is it?

If you don´t know - this little piece of code can help you:

$link = mysql_connect('mysql', 'mysql_user', 'mysql_password');
if (!$link) {
die('Keine Verbindung möglich: ' . mysql_error());
}
printf("MySQL server version: %sn", mysql_get_server_info());
?>


once you enter your data and save it as a php file.
Sorry, this signature is experiencing technical difficulties. We will return you to the sheduled signature as soon as possible ...
15
ViperSBT
Re: Upgrade to 2.0.14 went south

  • 2006/7/1 0:37

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


MySQL server version: 4.1.16-standardn
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com
16
ViperSBT
Re: Upgrade to 2.0.14 went south

  • 2006/7/1 1:18

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


Anyone willing to IM me to try and figure this out you can get me at ViperSBT on AIM...

I am trying to install a fresh copy on the server right now to see what that does... I just can't figure out why this isn't working...
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com
17
ViperSBT
Re: Upgrade to 2.0.14 went south

  • 2006/7/1 1:25

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


A completely clean install works fine. So there has to be something about my pre-existing installation that is causing a problem... It worked 100% perfect before the upgrade, so the environment is OK.
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com
18
ViperSBT
Re: Upgrade to 2.0.14 went south

  • 2006/7/1 1:50

  • ViperSBT

  • Just popping in

  • Posts: 88

  • Since: 2004/9/27


Stepping through it and trying to find the failuer, I have found that it appears to be dying between the include('header') and include('footer'). So the problem must be coming up in the header...

I went into header and did a little poking around and noticed that it makes several calls to $xoopsConfig, so to see what it was getting I did a print_r($xoopsConfig); and this is the result:

Array ( [xoops_url] => http://www.u-fli.com [root_path] => /home/httpd/vhosts/ufli/)

It seems that there should be a lot more in this array than these two items. I believe this is handled in includes/common.php, but looking at that code, it may be beyond me as to what is happening, and it still isn't generating an error.
Brett M. Williams
Co-Founder, The United Flyball League International
http://www.u-fli.com
19
snow77
Re: Upgrade to 2.0.14 went south

  • 2006/7/1 4:36

  • snow77

  • Just can't stay away

  • Posts: 864

  • Since: 2003/7/23


Quote:

A completely clean install works fine. So there has to be something about my pre-existing installation that is causing a problem.


I've read everything, it's crazy (and no one will read phpinfo with those terrible colors)

-if something is happening with your previous install, it looks to me like if files weren't over writing the correct way, there is a CHMOD problem, or your theme has something wrong.

- if a completely clean install is working why not do the following:

A) put all the modules of your previous version into the new clean install

B) Do a ONLY DATA backup of your previous site

C) Go to phpMyAdmin, go to the database of the new working site, select all tables, and EMPTY them DO NOT DROP-ERASE- them

D) Upload to the database of the new working site the data backup of the previous site

F) Upload the previous theme you had, any custom images - banners -etc to their respective folders

E) All should be ok now. You should have a new site with the latest XOOPS version with the same data as the previous version and you should be able to login as admin the same way as before

I hope to not have missed any important step , anyways you have nothing to lose, you should take care in step B though.
20
JCDunnart
Re: Upgrade to 2.0.14 went south

  • 2006/7/1 6:05

  • JCDunnart

  • Not too shy to talk

  • Posts: 114

  • Since: 2006/7/1 5


If you have a recovery.php file and the config value for debug is serialized (as you say) then it's either a XOOPS 2.2.x site, or maybe you downgraded from version 2.2.x ?

Either way, I'd reupload the original files (before the upgrade to 2.0.14) to restore the site, then perform the upgrade on a local copy of your site, so you can investigate without the time pressure of a site offline
« 1 (2) 3 »

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

336 user(s) are online (227 user(s) are browsing Support Forums)

Members: 0

Guests: 336

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