1
hal9000
Upgrading from 2.10 to 2.2 major problems
  • 2005/7/29 10:55

  • hal9000

  • Just popping in

  • Posts: 60

  • Since: 2003/8/6 9


ok here's what happened
i was using 2.10
upgraded to 2.12
upgraded to 2.13
upgraded to 2.2
Followed the 2.2 upgrade instruction EAXCTLY to the letter.
did the refresh bit and waited to click continue to upgrade and white screen!
did it a few more times no change :(
so decided to check out the admin which i had running in a seperate tab.
White screen...
??
where do i go from here?

help

2
Herko
Re: Upgrading from 2.10 to 22 major problems
  • 2005/7/29 10:58

  • Herko

  • XOOPS is my life!

  • Posts: 4238

  • Since: 2002/2/4 1


turn on php debug using the recovery.php in your site root.

Herko

3
hal9000
Re: Upgrading from 2.10 to 22 major problems
  • 2005/7/29 11:00

  • hal9000

  • Just popping in

  • Posts: 60

  • Since: 2003/8/6 9


i did that as part of the upgrade process. and it worked as i checked before uploading new files.

the recovery.php just gives me a white screen as well?

4
marook
Re: Upgrading from 2.10 to 22 major problems
  • 2005/7/29 11:09

  • marook

  • Friend of XOOPS

  • Posts: 89

  • Since: 2002/9/9 1


Hi,

I had this as well, and re-uploaded all files with binary transfer (ftp), and it startet to work.

Just a pointer, if helpful...
Marook,

Want to go on a Safari with me?
(Yes, it is me in that avatar.. )

5
hal9000
Re: Upgrading from 2.10 to 22 major problems
  • 2005/7/29 11:10

  • hal9000

  • Just popping in

  • Posts: 60

  • Since: 2003/8/6 9


cheers i will give that a go now
:)

6
hal9000
Re: Upgrading from 2.10 to 22 major problems
  • 2005/7/29 11:17

  • hal9000

  • Just popping in

  • Posts: 60

  • Since: 2003/8/6 9


YAY super happpy now.. it all worked

cheers everybody for your help - maybe this should be documented?

7
silvrhand
Re: Upgrading from 2.10 to 22 major problems
  • 2005/7/29 19:08

  • silvrhand

  • Just popping in

  • Posts: 42

  • Since: 2005/1/11


Make sure to turn off gzip compression, i had a ton of whitescreen issues as well till I did this.

To confuse the issues if you turn on php debugging it will I think disable gzip compression and everything works fine till you turn back off gzip compression.

8
schipper
Re: Upgrading from 2.10 to 2.2 major problems
  • 2005/7/29 20:54

  • schipper

  • Just popping in

  • Posts: 15

  • Since: 2002/6/5 7


Don't upgrade to 2.2 at this moment, I would say. I tried, several times, several sites. Didn't work. WSOD's, database errors, had to use a backup to get my site back online. What ever the problem is, it looks like the release of 2.2 is too early. It seems to me that there is a lot of pressure to get the next versions of XOOPS out. That is absolutely NOT necessary. XOOPS already is an outstanding CMS. Don't spoil that by releasing semi-stable versions.

9
jdseymour
Re: Upgrading from 2.10 to 2.2 major problems

The version that you speak of as being a rush release was delayed two times because the developers felt that more needed to be fixed. When all was fixed to the developers satisfaction the new version was released, not before. All this general talk of WSOD and database errors needs to be replaced by actual error messages so that we, or the developers can help.

XOOPS 2.2 is stable, but is a stepping stone (as well as a major upgrade with database changes) to the more refined 2.4 release.

10
JMorris
Re: Upgrading from 2.10 to 2.2 major problems
  • 2005/7/30 2:24

  • JMorris

  • XOOPS is my life!

  • Posts: 2722

  • Since: 2004/4/11


Quote:

jdseymour wrote:
The version that you speak of as being a rush release was delayed two times because the developers felt that more needed to be fixed. When all was fixed to the developers satisfaction the new version was released, not before. All this general talk of WSOD and database errors needs to be replaced by actual error messages so that we, or the developers can help.

XOOPS 2.2 is stable, but is a stepping stone (as well as a major upgrade with database changes) to the more refined 2.4 release.


Agreed!

If you're not totally comfortable with making a wholesale switch to 2.2 now, don't. I wouldn't delay too long, but giving it a couple weeks to test this new version out in a non-production environment is not a bad idea.

For sites that are established, stable, and in production, I'm holding off for a couple weeks so I can learn the new interface and see if any more bugs are found. I believe I've found one already and reported it in the appropriate forum.

As with any major software revision (yes, XOOPS is software), you need to make sure you know exactly what it is you're getting into before you dive in head first. As jdseymour stated, this is a major revision. Something to keep in mind is that, while the XOOPS framework may work flawlessly, third-party modules may not work so well with the new API. While upgrading a couple developement sites, I found that modules, not the core, were causing my WSODs.

Just something to consider.

JMorris
Insanity can be defined as "doing the same thing over and over and expecting different results."

Stupidity is not a crime. Therefore, you are free to go.

Login

Who's Online

144 user(s) are online (23 user(s) are browsing Support Forums)


Members: 0


Guests: 144


more...

Donat-O-Meter

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

Latest GitHub Commits