19
Quote:
The recent repeated comments on ICMS forums from your leaders trying to scare people, and your above negative announcement related to XOOPS 2.3, shows clearly that there is a lot of FUD coming from ICMS side. Because you're on the other side of the fence, I'm sure you'll see things differently
scare people, i don't see it like that.
i have seen comments from people saying that some modules do not work on XOOPS 2.3 because there are some changes that have been made which can break compatibility with XOOPS 2.0 modules. and if you think that is scaremongering, then i think you are also holding a huge grudge towards them, and in which case you can't offer an unbiased opinion about them.
so what are the changes from XOOPS 2.0.x and 2.3.1? there is no information at all. module developers are having to do trial and error.
there is differences YES. for 1 instance. in XOOPS 2.0, mail was using function &getMailer() but in 2.3 this function was renamed to xoops_getMailer()
that 1 simple change is enough to break compatibility because unless the module developer changes references to that in his modules, then mail system of the module will not work.
without proper information on changes like that, how do developers know what to do and what to look out for?
i can see their anger over there, and i can also see their point to an extent. It WAS promised by XOOPS devs that ALL modules that currently work with XOOPS 2.0.18 will work with XOOPS 2.3, but that isn't true, because clearly they don't all work.