1
Ace_Armstrong
2.0.7 questions

Several questions related to the 2.0.7 upgrade, which should be re-released soon:

1. How difficult will it be to upgrade from 2.0.5 to 2.0.7? I never installed the 2.0.6 upgrade because (a) I've been too busy to mess with it (I customized a lot of the files to adjust things like the width of text areas, and I'd have to go back and re-do all of those changes), and (b) I remembered the 2.0.4 debacle and really didn't need that much stress in my life. Hopefully I'll have enough time to deal with an upgrade if there's a clear path from 2.0.5 to 2.0.7

2. How many known issues are there with 2.0.7? (Again, thinking back to the 2.0.4 nightmares....)

3. Is there a list somewhere of the major changes?

2
meme
Re: 2.0.7 questions
  • 2004/6/15 11:34

  • meme

  • Quite a regular

  • Posts: 271

  • Since: 2002/12/10


you just need to upgrade your XOOPS to 2.0.6 now then wait the new release 2.0.7

just replace the files its easy

3
Mithrandir
Re: 2.0.7 questions

1. When a new upgrade patch is released you just apply the 2.0.5 -> 2.0.6 first, then 2.0.6 -> 2.0.7 and then update the system module. There are no database changes in either versions, so it's just a matter of overwriting old files and update the system module (perhaps a bit more when we get an overview of the vulnerability fix

2. One. Connected with the vulnerability fix, which we will hopefully fix properly soon

3. There was in the release news item and probably will be again in the new release notes. Mainly it is an implementation of bugfixes and patches from the sourceforge project trackers.

4
Ace_Armstrong
Re: 2.0.7 questions

Quote:

meme wrote:
you just need to upgrade your XOOPS to 2.0.6 now then wait the new release 2.0.7


I rather suspected that would be what I had to do...


Quote:

meme wrote:
just replace the files its easy


Not quite so easy, as I explained, because I hacked some of the files to get better display results. I'd have to find each and every little hack and recreate it. That's why I think the width of text areas, etc. should be adjustable variables set in the admin area.

Thanks, though!

5
Ace_Armstrong
Re: 2.0.7 questions

Quote:

Mithrandir wrote:
1. When a new upgrade patch is released you just apply the 2.0.5 -> 2.0.6 first, then 2.0.6 -> 2.0.7 and then update the system module. There are no database changes in either versions, so it's just a matter of overwriting old files and update the system module (perhaps a bit more when we get an overview of the vulnerability fix


That's kinda what I thought. Didn't know if there was an update planned that would go straight from older versions, but I suspected there wouldn't be.


Quote:

Mithrandir wrote:
2. One. Connected with the vulnerability fix, which we will hopefully fix properly soon


I saw that. That already exists in all of the previous verions, though, doesn't it? From what I can tell from the comments, it's not something that was introduced with this new update.


Quote:

Mithrandir wrote:
3. There was in the release news item and probably will be again in the new release notes. Mainly it is an implementation of bugfixes and patches from the sourceforge project trackers.


So the answer is that there's not list now, but there will be when it's re-released, right? Schmoove!

Thanks, mate!

6
Mithrandir
Re: 2.0.7 questions

Only very few of the fixes have to do with presentation - but it may be a good idea to spend some time until we have a new 2.0.7 release to mark the changes you have made, so you can re-apply them if the files are changed

Edit: And yes, apart from the potential security hole, there are no known issues (actually, I'm getting ahead of myself there. I *think* there are no other issues. There was one with the admin-input footer, but I think Skalpa found that one).
The hole is also there in previous versions, but the attempted fix broke some installations.

You can get a pretty good overview of at least the patches by going Here and select the closed patches in 2.0.x category.

Generally, bugs closed after February are also in the update

7
Ace_Armstrong
Re: 2.0.7 questions

Quote:

Mithrandir wrote:
Only very few of the fixes have to do with presentation - but it may be a good idea to spend some time until we have a new 2.0.7 release to mark the changes you have made, so you can re-apply them if the files are changed


Well, the settings that I changed were (if I recall correctly) in mainfile.php and a few of the other core files that set up text area widths, how many icons are shown in the text entry areas before a soft break is entered, and so on. These settings all seem to be in core files that get modified and need to be replaced with each new upgrade. (Hence my desire to have them set in the admin control panel as a variable!) So even if the updates themselves don't change the settings, when I copy the files over my existing files, they will revert back to the state they were in before I modified them. Am I making any sense?

8
Mithrandir
Re: 2.0.7 questions

You make sense - so much more the sense in mapping those changes so you are prepared for the new release

Good luck with it.

9
Ace_Armstrong
Re: 2.0.7 questions

Quote:

Mithrandir wrote:
You make sense - so much more the sense in mapping those changes so you are prepared for the new release


Yeah. That's the headache part I've been putting off!


Quote:

Mithrandir wrote:
Good luck with it.


Thanks,and thanks for the info!

10
meme
Re: 2.0.7 questions
  • 2004/6/15 12:07

  • meme

  • Quite a regular

  • Posts: 271

  • Since: 2002/12/10


you have to find the new changed files then re do the hacked codes for the new files

thats all

you will find the new changes files in the patch

Login

Who's Online

205 user(s) are online (139 user(s) are browsing Support Forums)


Members: 0


Guests: 205


more...

Donat-O-Meter

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

Latest GitHub Commits