[Solved] Latest version of my module doesn't appear in Module Manager

docomo · Post by **docomo** » Sun Jul 13, 2008 12:45 pm

Hi,

I have been developing a module (Podcast Manager). Initially I released version 0.3 Alpha 1, since then I have released a number of versions with the current version being 0.6. Each release has included a .xml and .zip file.

The initial (0.3 alpha 1 version) shows in Module Manager, however none of the other versions appear. I am not that familiar with the way Module Manager works, I wondered if someone could provide some advice on why this is the case.

It may be somthing I have missed. I checked a few things - in the module the Minimum version of CMSMS 1.2.4 and maximum 1.5.0. Any help would be appreciated.

Regards

Michael

Dr.CSS · Post by **Dr.CSS** » Sun Jul 13, 2008 5:54 pm

And what ver. of CMSMS are you using to see if it shows up, newer ver. has the ability to check if module is compatible with the ver. of CMSMS checking for modules, iirc...

docomo · Post by **docomo** » Sun Jul 13, 2008 11:00 pm

Thanks Mark for your prompt response. The version of CMSMS i am using to check Module Manager is 1.3.1.

Regards

Michael

Dr.CSS · Post by **Dr.CSS** » Sun Jul 13, 2008 11:31 pm

But the ver. that the module is good for, most times I've seen a min. ver. of CMSMS never a max. ver. of CMSMS...

function MinimumCMSVersion() {
return "1.0";
}

So if you put a maximum ver. of CMSMS call it may hamper it...

docomo · Post by **docomo** » Sun Jul 13, 2008 11:40 pm

Thanks for that Mark, I'll try removing MaximumCMSVersion method and give it a try - I'll let you know what happens.

Regards

Michael

docomo · Post by **docomo** » Fri Jul 18, 2008 5:44 am

Hi Mark,

I tried removing the MaximumCMSVersion method from the latest release of the Podcast Manager software (version 0.6.1).

Unfortunately this didn't fix the problem - i upload it a couple of days ago, but the original version (0.3 alpha 2) still shows in module manager.

Another possible problem is the version in the Forge release manage, and code are different - in the Forge release manage the package version is '0.3 alpha 1', whilst in my code (GetVersion method) it is '0.3 alpha 2'. This could possibly cause a problem (?)

I will also compare my code to the 'Album' module i originally based it on.

As a last resort i'll probably delete the '0.3 alpha 1/2' package.

Regards

Michael

docomo · Post by **docomo** » Sun Jul 20, 2008 2:22 pm

Hi,

I tried all the ideas to try to get module manager to show the latest version of my module (podcast manager v0.61), unfortunately they didn't seem to fix the problem. The ideas i tried were:

- I tried removing the MaximumCMSVersion method from the latest release of the module.
- Compared the code against the module i based it on (Album) to look for possible issues (I couldn't spot any)
- Finally i deleted the version being reference (0.3 alpha 2) from the file release system (which i did over 2 days ago)

Unfortunately the original version (0.3 alpha 2) is still showing up in module manager.

If anyone has any further ideas or suggestions, they would be most welcome.

Regards

Michael

docomo · Post by **docomo** » Tue Jul 22, 2008 12:14 pm

Hi,

The problem now seems to be fixed. The latest version of Podcast Manager is now appearing in Module Manager (v0.6.1). Yay!!!

I think the fix was deleting the original version 0.3 alpha 1. There was an inconsistancy between the versions - the code ('getversion' method) had v '0.3 alpha 2', whilst the File Release System had v '0.3 alpha 1'.

Regards

Michael

CMS Made Simple Forums