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