1
fishspon
Upgrading from 2.0.5.2 to 2.2 with other modules - easy or not?
  • 2005/10/29 22:55

  • fishspon

  • Not too shy to talk

  • Posts: 164

  • Since: 2003/11/23


Hey people...

I'm currently running XOOPS 2.0.5.2 with the following modules:

- contact v1
- mylinks v1.1
- newbb v1
- news v1.1
- xoopsmembers v1
- xoopspoll v1
- mydownloads v1.1
- xoopsfaq v1.1
- wfsection v1.01
- myalbum v2.6
- glossaire v1.6
- counter v1
- liens v1
- whosonline v1
- lykos_blocks v1.2
- lykos_googled v0.1
- myAds v3
- waiting v0.4
- xoopsheadline v1
- catads v1.23

The most critical modules (i.e. the ones that must work at the end of all this) are mylinks, newbb, news, xoopsmembers, xoopspoll, wfsection (or some equivalent), myalbum (or some other photo album i can upgrade to), glossaire (or some other glossary i can upgrade to), liens (or some other "Link to us" module), catads (or some other Classified Ads module i can upgrade to).

All other modules *could* be uninstalled prior to the upgrade if necessary.

What is the best upgrade route, as recommended by the good people on this forum?

I have already downloaded the following files, but am i really going to have to go through them one-by-one until i get to the latest stable version?

- xoops-2.0.5-to-2.0.6.patch.zip
- xoops-2.0.6_to_2.0.7.zip
- xoops-2.0.7_to_2.0.9.2.zip
- Xoops-2.0.9.2-to-2.0.10.zip
- Xoops-2.0.10-to-2.0.12a.zip
- Xoops-2.0.12a-to-2.0.13.zip
- xoops-2.0.13-to-2.0.13.1.zip
- Xoops-2.0.13.1-2.0.13.2.zip
- Xoops-2.0.13-to-2.2.zip

Basically, i'm looking for the best upgrade path, which will cause the least glitches in the system.

Non-core modules, like the Photo album etc... *could* be uninstalled if it really had to be, but then i'd have to try and upload all the photos again as the same users as before, and it'd just be a huge nightmare, so what do you suggest?

Thanks in advance to anyone who can help!!

Hobbs.
[size=x-small]><> fishsponge <><
[HiFi Forum] [UNIX/Linux Forum] [Richard Hobbs][/size]

2
JMorris
Re: Upgrading from 2.0.5.2 to 2.2 with other modules - easy or not?
  • 2005/10/29 23:53

  • JMorris

  • XOOPS is my life!

  • Posts: 2722

  • Since: 2004/4/11


First, before you do anything, backup your site! You'll thank me for the suggestion if anything goes wrong.

Secondly, I wouldn't recommend 2.2.x as of yet. If for no other reason than the fact you're going to have a heck of a time finding the modules you need that work with that version.

Finally, in reference to...
Quote:
I have already downloaded the following files, but am i really going to have to go through them one-by-one until i get to the latest stable version?


The *safe* answer is Yes. LazyBadger released a *bundled* update, but a)I cannot find his post about it. and b)It may not be appropriate for your situation.

Hope this helps.

James
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.

3
pmcnamara
Re: Upgrading from 2.0.5.2 to 2.2 with other modules - easy or not?
  • 2005/10/30 0:10

  • pmcnamara

  • Friend of XOOPS

  • Posts: 147

  • Since: 2004/12/3


Hobbs.. check out www.warpigw2.com, John has a very easy to follow tutorial which will walk you right through it. I did it with no problems.

http://www.warpigw2.com/modules/AMS/article.php?storyid=98

4
fishspon
Re: Upgrading from 2.0.5.2 to 2.2 with other modules - easy or not?
  • 2005/10/30 22:05

  • fishspon

  • Not too shy to talk

  • Posts: 164

  • Since: 2003/11/23


hey people!

i have now begun the upgrade process, but i have a problem...

I have done the following successfully:

2.0.5.2 -> 2.0.6 -> 2.0.7

So i'm now at 2.0.7, and everything appears to be working.

However, when i apply the changes as per "xoops-2.0.7_to_2.0.9.2.zip", all i get is a blank page, and when the source of this blank page is viewed, all that is produced is:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<
HTML><HEAD>
<
META http-equiv=Content-Type content="text/html; charset=iso-8859-1"></HEAD>
<
BODY></BODY></HTML>

The page goes blank around half-way through uploading the files thru FTP, if you keep refreshing it during the course of the upload. I'm not sure which of the uploaded files causes the problem, but with a long task of uploading all 250-odd files one-by-one, i'm sure i could find the offending file if you think it's necessary.

There are no entries in the web server logs to coincide with this, so does anyone know what the problem could be?

Thanks again to anyone to can help
[size=x-small]><> fishsponge <><
[HiFi Forum] [UNIX/Linux Forum] [Richard Hobbs][/size]

5
fishspon
Re: Upgrading from 2.0.5.2 to 2.2 with other modules - easy or not?
  • 2005/12/15 16:43

  • fishspon

  • Not too shy to talk

  • Posts: 164

  • Since: 2003/11/23


anyone got any ideas on how to get from 2.0.7 -> 2.0.13.2 at all?
[size=x-small]><> fishsponge <><
[HiFi Forum] [UNIX/Linux Forum] [Richard Hobbs][/size]

6
NeoFenix
Re: Upgrading from 2.0.5.2 to 2.2 with other modules - easy or not?
  • 2005/12/15 19:25

  • NeoFenix

  • Just popping in

  • Posts: 31

  • Since: 2005/7/8 3


first of all, activate the debug mode in the main admin section (php debug first), then load the page that cause de error and look what module is causing it, i'm pretty sure that is an old module.

The just deactivate that module and see what happen

PD: when you update so many version at once, or one after another, is better to deactivate the modules, and then reactivate one by one, to actualice their templates and see if they are compatible with the new update.

Login

Who's Online

79 user(s) are online (60 user(s) are browsing Support Forums)


Members: 0


Guests: 79


more...

Donat-O-Meter

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

Latest GitHub Commits