Conflicting Contributions, list them here!

**birdoasis** · 26 Apr 2007, 02:11 AM

The funny thing is that many of the contributions are now included in 1.3.7. So paying attention to the version of the contribution you're installing is important.

Of course username one was right, I should have named it in the positive tone.

Now Kobra, I wasn't thinking that someone would just load every single contribution. Just the ones that are for the version that you're using.

So that should bring it down to something like 2000, permutations or combinations right? haha.

**kobra** · 26 Apr 2007, 05:26 AM

(darn slide rule - slipped a decimal)
200x200=4000 NOT!!

200x200=40,000 permutations

**birdoasis** · 26 Apr 2007, 05:31 AM

Whoops. I knew I shouldn't have used your sliderule. Sorry bout the jelly.

**Woodymon** · 26 Apr 2007, 07:40 PM

Originally Posted by birdoasis

I wasn't thinking that someone would just load every single contribution. Just the ones that are for the version that you're using. So that should bring it down to something like 2000, permutations or combinations right? haha.

The estimated 2000 permutations number is significantly low.

More the issue, it just takes one single code change, either a patch to Zen Cart or a patch to a mod, or any other customization, that can change things.

Say Mod ABC v.1 has been tested on a described platform (which we know every platform is different) with Zen Cart 1.37, how should it be conveyed if any patches/code changes were applied to either Zen Cart 1.37 or mod ABC v.1. Then apply this same idea to the multiple mods that might be installed, some customized and some not. And how to convey which checkboxes in all Zen Cart admin menus were checked/enabled during the testing. And which functions/features were tested.

Relatedly if PayPal compatibility is important (and it is to many Zen Cart shop owners) how do we convey which PayPal patch was installed during the testing and how PayPal was configured. And multiply this by the other shipping/payment mods that are installed during the time of the testing".

And payment/checkout providers can change their system at any time. How to control those variables.

Sure a compatibility list or a non-compatibility list can be looked at as a VERY rough guide. But even as a rough guide the lasting power of such a list is not at all worth the extreme effort involved.

Woody