Miva 10 Incompatible (Discontinued) 3rd Party Modules List

[eldon99]

I am finally getting around to upgrading some of my client's stores to Miva 10. I wanted to see if there is a comprehensive list of 3rd party modules that should be removed prior to upgrading? (e.g. Sebenza, Weiland, etc).

[lesliekirk]

I am finally getting around to upgrading some of my client's stores to Miva 10. I wanted to see if there is a comprehensive list of 3rd party modules that should be removed prior to upgrading? (e.g. Sebenza, Weiland, etc).

That would be awesome to have. I know personally, the Sebenza Product Template Manager module has broken an MM10 store. You will be required to remove the Sebenza Category Template Manager. I have had to redo a store using an MvM module. I've had some other weird stuff come up. If it happens again, I'll post it here.

FWIW - I had to use the Toolkit to rework the Sebenza Cattree module.

[Bruce - PhosphorMedia]

While you don't have to remove them, any Phosphor Media module should be updated to the latest version.

https://www.phosphormedia.com/mm5/me...=about-updates

[Rick Wilson]

A couple items of note, there is not a "Master List" partially because we don't have a way of knowing all of the modules that exist in the world.

There is two rules you can follow though for a successful upgrade:

1. We use the Upgrade Advisor in the Upgrade Process which checks for modules with known problems. This list changes over time, so since you've waited months, it's likely a very thorough check. It will prevent you from upgrading with any modules that we know of that would break your store. On the very slight chance you upgrade and there is a problem with a module you have and we didn't catch it, please let us know so we can add that module to the Upgrade Advisor.

2. You should make sure you take out any modules that are no longer supported (Sebenza is the obvious choice and any Emporium Plus module we no longer support, since both companies are no longer in existence) but a quick check of your modules is worth doing.

[William Davis]

A couple items of note, there is not a "Master List" partially because we don't have a way of knowing all of the modules that exist in the world.

There is two rules you can follow though for a successful upgrade:

1. We use the Upgrade Advisor in the Upgrade Process which checks for modules with known problems. This list changes over time, so since you've waited months, it's likely a very thorough check. It will prevent you from upgrading with any modules that we know of that would break your store. On the very slight chance you upgrade and there is a problem with a module you have and we didn't catch it, please let us know so we can add that module to the Upgrade Advisor.

2. You should make sure you take out any modules that are no longer supported (Sebenza is the obvious choice and any Emporium Plus module we no longer support, since both companies are no longer in existence) but a quick check of your modules is worth doing.

Rick,

Can't help being confused. We have a number of old man Weiland's modules installed in our M10 store and some are still being used (e.g.: Toolkit, Waitlist, Miscellaneous Fee, Follow-on Contact, Find and Replace, CIM Activity Log, etc.), many along with other of his modules are still avaialble for sale on the Miva Apps Store.

Many if not all those modules we can't do without because a comparable solution does not exist.

[lesliekirk]

Rick,

Can't help being confused. We have a number of old man Weiland's modules installed in our M10 store and some are still being used (e.g.: Toolkit, Waitlist, Miscellaneous Fee, Follow-on Contact, Find and Replace, CIM Activity Log, etc.), many along with other of his modules are still available for sale on the Miva Apps Store.

Many if not all those modules we can't do without because a comparable solution does not exist.

Bill, I can relate (and understand). I know that I have been one of those who have been nagging for the "equivalent coding" to be able to replace a number of these modules. The Miva team has helped me with a couple of them. It is going to be difficult to replace the brilliance of Bill Weiland's modules. Maybe Rick will let us start a "wish list" of replacement coding (or even modules) that can encompass (and is specific to) the fine nuances of those modules. Bill may have had "logic" that wasn't quite along the same thinking that the brain trust at Miva. Maybe if we (users of the EP modules) were able to give Miva a detailed explanation of how these modules are used maybe that would help. I think that may have partly been what the original intent of this post was (is).

[Rick Wilson]

Since this is morphing into 2 topics, let me answer them before it gets confusing.

1. When it comes to upgrading to Version 10, if we still offer an Emporium Plus module in our App Store, then it means we still support it and there's no current reason to put much effort into getting rid of it.

So ultimately EP modules fall into 3 buckets: First is fully supported and available on the App Store, second is not supported and doesn't work in Miva 10 and third is a more grey area, where they work just fine in 10 but are not supported.

Therefore, there are some Emporium Plus modules that the Upgrade Advisor will catch and stop you from upgrading and then there's another category of modules from EP that work fine (right now on 10) but we no longer support and someday they might break and it's unlikely we'd fix the module (in those cases however there will almost certainly be native functionality to replace any module like that).

When it comes to Sebenza, Sebenza hasn't existed since about 2008 or so and all of there modules should be pulled from any active store.

2. When it comes to feature requests, of course we always want to hear those requests, but this thread isn't a good place for them as they'll undoubtedly get lost. That's why we have the Dream Features forum as a permanent "Parking Lot" where we go back to in order to ascertain demand for features as well as details about feature requests. So by all means if there are things from EP modules that are included in the non-supported but works on V10 list of modules, please post those requests (or any requests really) over in the Dream Features Forum.

[lesliekirk]

Since this is morphing into 2 topics, let me answer them before it gets confusing.

1. When it comes to upgrading to Version 10, if we still offer an Emporium Plus module in our App Store, then it means we still support it and there's no current reason to put much effort into getting rid of it.

So ultimately EP modules fall into 3 buckets: First is fully supported and available on the App Store, second is not supported and doesn't work in Miva 10 and third is a more grey area, where they work just fine in 10 but are not supported.

Therefore, there are some Emporium Plus modules that the Upgrade Advisor will catch and stop you from upgrading and then there's another category of modules from EP that work fine (right now on 10) but we no longer support and someday they might break and it's unlikely we'd fix the module (in those cases however there will almost certainly be native functionality to replace any module like that).

So if it's still in the App Store we can continue to get support? There have been times when I've been told by support that the module is obsolete, so I'll make sure in the future that I make sure it's no longer available in the app store. If it's no longer available, I'll make sure to ask if there is a method that uses native coding instead of the module. This sort of falls under my continuing nag for replacement snippets. LOL, maybe I'm looking for snippets that are "Leslie proof" so Google doesn't find me when I break something

[William Davis]

Well put Leslie and thank you Rick for clarifying things up, good idea both.

I will starting documenting the solutions we currently as you suggested wherein a native one does not exists.

[Rick Wilson]

Leslie, make sure you let Brennan (and me) know if there's something on the App Store and you get stuck with Support.

[lesliekirk]

Leslie, make sure you let Brennan (and me) know if there's something on the App Store and you get stuck with Support.

Always - FYI, Nick has been my hero!

[alphabet]

Could limited parts of the EP discontinued module source code be included in the LSK so we would have a starting point for a solution?