CMS Made Simple Forums

Hello,

It would be real progress if developers had the possibility on the forge to indicate the latest php version compatible with their module.(without any notice warning and with)
I don't know if it's possible to set it up simply, if the interface provides for it. In any case, this would be a significant time saver for CMSMS users today who are likely to download a module that does not work with the version of PHP used on their site.

It's not really possible on the current forge, but it's very high on the wish list for the replacement (whatever form that ends up taking). I'd also love to see Module Manager check for it too.

Hello Digi3,

Thank you for your answer. So we'll see that when the redesign has been finalized.

The Release Notes and/or Changelog is the right place

Hello JCE,

I do not believe. Having the information as soon as possible, i.e. from the module download page seems preferable to me. There are no small savings when it comes to saving time.

The idea of integrating it directly into the module manager in addition, as Digi3 suggests is excellent. Address the problem as early as possible.

from the module download page seems preferable to me

Yes, that's exactly
- Let's take an example of a module: this is the download page http://dev.cmsmadesimple.org/project/files/1429
You have directly here v1.5 Released On: 2024-04-02 13:12 | Release Notes or Changelog
The latest version, Release Notes or the Changelog may have PHP version 8.3
The previous version is likely to be another, earlier version, e.g. PHP 8.1 for v1.3
- All the developer has to do is indicate the PHP version
-> Depending on the version of your server, you can adapt the version of your module.

Dear JCE,

It seems pretty obvious to me that the information in the changelog file requires an extra click to read. Are you a telepath?

Are you a telepath?

No, I'm just being logical in order to obtain reliable and verified information !

JCE,

I forgot, when the developer puts his module on the Forge, he will necessarily choose an incorrect PHP version for compatibility, while in the changelog it's a completely different story, of course.Fortunately, some are keeping a close watch !