Hello!

Quote:

I understand your confusion.

I can assure you (not officially, I am a user!) that there is no version planned to be discontinued. Simply try to understand the two versions and their differences. They differ in their features und programming quality.

Version 2.2.4 is simply making some of the scripts in 2.2.3 more secure and stable. It is not a real full version but only a part. The problems that appeared in the last few months has been incorporated in those scripts supplied in the file.

The version 2.0.xx.x has been existed for a longer time and has undergone a bit vigourous testing. Hence you can be more secure about very small bugs into and can use it on a production site. Most of the conflicts have been solved also at the module developers level as many module developers have brought up tested versions with this.

On the otherside, the version 2.2.3 with the latest upgrade to 2.2.4 is a bit newer one. Hence there may be small bugs or compatibility issues that either they are not yet solved or not yet identified.

So you may decide on your own, if you want to use the older version 2.0.13.2 with a choice of a script more vigorously tested and is stable but with less features or use the stable version of 2.2.4 (2.2.3 + upgrade 2.2.4) with more features and some tiny bits yet to be modified or less important.

Both versions will be continued and will merge into one version ONE day. U can be sure.

deepy,

I would have to disagree to some point, in that crowding one page with tones of info might just make it worse.

but as I originall suggested:

Quote:

By all means include the info you have mentioned, but not here, maybe include it on the download page, so that the home page of XOOPS doesn't become more clutered.

I proposed this idea before, and still think it would be a better way, and

Hallo Tom!

May I ask you why do you say not to use the version 2.2.3 or 2.2.3 + 2.2.4 on a production site?

Did I miss something?

I am using it on a production site!

I just stumbled upon this thread and am horrified. Suddenly my little trouble with xDonations doesn't seem very important at all!

Just two weekends ago I migrated to 2.2.x and must have been asleep at the wheel. I don't remember any obvious warnings that this was the wrong thing to do for a production site. Was the new logo blocking the detour sign?

Not that I'm having any trouble with 2.2.4 though. I rather like it actually. Guess the worst case scenerio then is that I'm stuck here forever?

Actually, never upgrading again is starting to sound better and better. Might get a weekend off one these days. I've wondered what normal people do with all that free time.

Hi!

I am also using it on a production site.

II find it a bit too much to continue this state of unhealthy Versioning and postponing of Upgrade possibilities with 2.2.4!

People get confused. Users who uses or made update has to wait for ages before 2.4 comes out. This is a punishment not deserved at all.

On one side XOOPS lacks a lot of functions that Joomla and other CMS has. Now there is one more gigantic stricke that 2.2.4 users have to sit down and pray to god, before the CORE team breaks-ups. Hope this does not happen here AGAIN like it did with Mambo!

However, if you are using 2.2.4, sleep well as I DO NOT think it is as buggy as being populated into others head. The CORE programmers have taken a careful distance to discuss over this matter and silently continue to program 2.3, which I hope comes out one day!

Well I'm using 2.2.3 and it seems to be OK (had to fix a couple of bugs but can't remember what they were now). I'm not going to upgrade to 2.2.4 as it'll probably introduce more bugs

Hi!

No, probably reduce the ones that are there!

Pl. read whats in there and why upgrade to 2.2.4! Its better!!!

As a person with 14 (I know I'm crazy) 2.2.x sites, I'm not too worried about migration or upgrades. I think I'll bypass version 2.3 as I've been told it is for v 2.0.x users. Version 2.4.x is supposedly where I'll upgrade again.

I don't think that this is too confusing... unless I'm wrong!

As for why we're not listed on opensourceCMS... I still don't understand it. Perhaps we need a XOOPS marketing campaign. We aren't the only software community to have gone through an upgrade hickup... and we're not likely to be the last.

Anyone want to work on getting the XOOPS message out???

I believe Rabideau you are even posting this message in a forum called 'Spread XOOPS project' .

It is because of unclear communication in the past on the subject that XOOPS was removed from the list. But since obviously an official 'recommended' status has been assigned to one of the versions, I guess it is time to send out the update to opensourceCMS.com.

If you have ideas for the marketing project, please have a look at the Spread XOOPS project forum.