In the Home > Utility Settings > Add/Remove Modules screen, the Description for the module will update if the module is updated, but the Version number appears to never update. (did not test the Provider, since that should change infrequently if ever.)
Announcement
Collapse
No announcement yet.
Utility Settings- Add/Remove Modules - version does not update
Collapse
X
-
Utility Settings- Add/Remove Modules - version does not update
Gordon Currie
Phosphor Media - "Your Success is our Business"
Improve Your Customer Service | Get MORE Customers | Edit Any Document Easily | Free Modules | Follow Us on Facebook
phosphormedia.comTags: None
-
Re: Utility Settings- Add/Remove Modules - version does not update
The version number displayed on that screen comes from the Modules table, whereas the description is pulled directly from the module. The version number will update if you go to the domain Modules screen and update the module, which will update the version number in the database. This will also trigger Module_Upgrade and Module_Upgrade_Store, as appropriate.
FWIW until you update the version number in the database you will be unable to install the module in a store, as (since PR6 or so), the software verifies that the version reported by the module is the same as the version number stored in the database. You will receive an error message similar to the following:
The version of module 'Custom Fields' in the database (5.9000) does not match the version reported by the module (5.9007).
-
Re: Utility Settings- Add/Remove Modules - version does not update
Right, I know all this - I just thought it was an - interesting - design decision that might need revisiting. It seems to be there as a safety mechanism?
Since you mentioned it, is there any API method to update the record in the Module table? We are trying to do an auto-update, so the aim is to avoid having the customer go to the domain Modules screen at all.Gordon Currie
Phosphor Media - "Your Success is our Business"
Improve Your Customer Service | Get MORE Customers | Edit Any Document Easily | Free Modules | Follow Us on Facebook
phosphormedia.com
Comment
-
Re: Utility Settings- Add/Remove Modules - version does not update
Originally posted by Gordon - Phosphor Media View PostWe are trying to do an auto-update, so the aim is to avoid having the customer go to the domain Modules screen at all.
LeslieLeslie Kirk
Miva Certified Developer
Miva Merchant Specialist since 1997
Previously of Webs Your Way (aka Leslie Nord leslienord)
Email me: [email protected]
www.lesliekirk.com
Follow me: Twitter | Facebook | FourSquare | Pinterest | Flickr
Comment
-
Re: Utility Settings- Add/Remove Modules - version does not update
Originally posted by Gordon - Phosphor Media View PostSince you mentioned it, is there any API method to update the record in the Module table? We are trying to do an auto-update, so the aim is to avoid having the customer go to the domain Modules screen at all.
I assume you're already making sure to run your upgrade code for each store if the module is installed in multiple stores.
Things will get more complicated if you are adding or removing features, especially if the added/removed feature is one of the features that only permit a single module per store, like tax, currency, or boxpacking.
Comment
-
Re: Utility Settings- Add/Remove Modules - version does not update
Leslie:
Actually, I misspoke - it's not auto-update, but one-click update we are designing.
It's counter to good UX to do something potentially disruptive without explicit involvement of a user.
We're just trying to reduce many clicks to one.Gordon Currie
Phosphor Media - "Your Success is our Business"
Improve Your Customer Service | Get MORE Customers | Edit Any Document Easily | Free Modules | Follow Us on Facebook
phosphormedia.com
Comment
-
Re: Utility Settings- Add/Remove Modules - version does not update
Originally posted by burch View PostIf you're not adding or removing any features from the module, it should be as simple as just calling [ g.Module_Library_DB ].Module_Update( l.module ).
Originally posted by burch View PostI assume you're already making sure to run your upgrade code for each store if the module is installed in multiple stores.
Originally posted by burch View PostThings will get more complicated if you are adding or removing features, especially if the added/removed feature is one of the features that only permit a single module per store, like tax, currency, or boxpacking.Gordon Currie
Phosphor Media - "Your Success is our Business"
Improve Your Customer Service | Get MORE Customers | Edit Any Document Easily | Free Modules | Follow Us on Facebook
phosphormedia.com
Comment
Comment