Hi,

I've tried to install one of my modules (DTInventory) using Module Manager.
I know that the version available from the forge is not updated to the latest CMSMS vs 1.10...
Installing is done without a problem and in the modules overview, it is clearly stated that the module is only supported up until 1.9.9.
The module is available via eCommerce menu option.
I thought that once the maximum supported version is set to something installation is not possible.
Does this have to do that 1.9.9 is greater than 1.10-beta3 (at least for the server)?
If so, doesn't this give a problem with all modules that have a maximum support set to at lease 1.1...?

Duketown

PS. MinimumCMSVersion() returns 1.8 for this module.

In the updated Module API Docs I read:



http://www.cmsmadesimple.org/apidoc_1.10/

Maybe that has something to do with your "issue"

I never use MaximumCMSVersion in modules. Raises more questions is the forum then it prevents?

_________________

Jos,

Thanks for the reply.
Since retrieval of data and checking if module has been installed is handled differently, I need to check which version is running. In other words on purpose I'm using both MinimumCMSVersion() as well as MaximumCMSVersion() to return 1.8 resp. 1.9.9
At this moment the module has been installed, but is not performing as it should (due to the checking of another module installation which is in my case if ShopMadeSimple is installed).

So there must be something else.

Duketown

Continuing on this minimum and maximum version setting I can even imagine that a version of a module prepared by me with 1.10-beta2 as minimum could be installed using module manager in a CMSMS version 1.9.4.3 environment. This could cause problems as well I think.

Were do I make a thinking mistake?

Duketown

Really like to know if I'm mistaken here.
When is it best to release 1.10 based modules?

Duketown

something with a Minumum version number of 1.10-beta2 should not be allowed to be installed from ModuleManager from CMSMS 1.9.x ... but I am also aware that the ModuleManager does not check MaximumCMSVersion (that data isn't even in the xml file).

So there isn't much you can do.

However, there is no reason you can't set a minimum version of 1.9.x for your module and have the same code work with 1.9.x and 1.10.x ... at least for a while, till most people are on 1.10.x

_________________
Follow me on twitter
Please post system information from "Extensions >> System Information" (there is a bbcode option) on all posts asking for assistance.
--------------------
If you can't bother explaining your problem well, you shouldn't expect much in the way of assistance.