Upgrading into incompatibility

[loukote]

Hi,

a similar message must exist on the forum already. But the problem persists and thus it should be reminded.

When upgrading a module (NMS), nowhere in the path (either when downloading the files or when upgrading via the UI) you are warned that the module version you are going to install will be incompatible with the CMSMS version. So either you upgrade, or you loose the capability (in this case sending newsletters; which is embarasing one month before an event).

I remember a similar situation with another module. How comes that I'm not warned? Such an information should be parsed from the package and shown on the Forge and in your UI.

I use CMSMS since at least 5 years and like it for its versatility. But there are points in times where I just wonder.

Would it be possible to implement some kind of red flags? Or am I just the only one?

[scelle]

NMS is 1.10.x compatible since version 2.3.5. If you're using older CMSMS version - sorry but the rules state that it's your fault for not upgrading.

Anyway, it is my impression that The Forge will be revamped soon. There is a lot of talk these days on this subject, so - no, you're not the only one who's concerned about this.

[loukote]

the rules state that it's your fault for not upgrading.

Are there any red flags at all even between two subsequent releases?

the rules state that it's your fault for not upgrading.

Completely disagree. It seems so obvious to me that you know that this is rubbish... An example if you need one: day 1, a release that breaks some kind of compatibility occurs. As there was a serious bug in that release, there is a new release the following day. Should I really apply the first update first? (Am I allowed to take 2 weeks off?

The Forge will be revamped soon

Rather happy to hear that.