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

JAVesey wrote:
Quote:

yeppers wrote:

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.

Sorry - I don't recall seeing that. Can you direct me/us to that?

I do remember seeing phrases like "most modules should work okay but we can't be certain" and "as this is a stepping stone to XOOPS 3.0, some modules may need modifying" and "all modules written for XOOPS 2.3.x will work with XOOPS 3.0", but I don't recall it in such cast-iron terms as you descibe for the XOOPS 2.0.x to XOOPS 2.3.x transition.

Not having a go - I'm genuinely interested as what you say would be quite a claim for the dev crew to make

Modules written for 2.0.* and 2.2.* will work with 2.3; applications developed for 2.3 will be compatible with XOOPS 3.0 automatically.

Both backward and forward compatibility are guaranteed as much as possible

skenow wrote:

Leading one to wonder - which is it?