Module incompatibilities
 After buying a Prime license and a few modules I have become really disappointed with Boonex or the developers. Everything seems to be going good then to realize that the modules are not compatible with each other.
For example;
After installing a module from one developer and its working fine then installing another module from another developer, the first module lost its functionality or the second module does not function correctly because of the first module. This has happened several times.
Then trying to get help from the developers, either they do not respond to my questions or they say sorry but they do not know how the other module works so they cannot be of any help.
Should'nt there be a developement standard such as that all modules are compatible with all modules?
Otherwise what is the sense in buying the modules if they do not work together?
Is anybody else having these very frustrating issues or is it just me?
Signed: Very Frustrated |
Even if a standard of some kind was developed, it still would not be possible to prevent incompatibilities. I am guessing incompatible modules would be modules that provide similar abilities. https://www.deanbassett.com |
Yes you are correct they are similar.
Global Localization Module versus Dependant Fields and Profile Types Splitter Modules.
The reason I did not mention these is because I did not want to make any body feel bad or give anybody any trouble.
Dependant Fields and Profile Types Splitter Modules work well together but after having the Global Localization Module installed and then creating dummy profiles with different profile types they do not show up when doing searches were they should show up.
Steve |
Hi thecrassman, did the Global Localization module work as it should before? Only reason Im asking is I was interested in this but have yet to see a working demo... Even the demo site linked to the module doesnt actually filter anything. |
The new Dolphin solution is powered by UNA Community Management System.