The customer community
http://www.shoppingcartcommunity.com/forum/
http://www.shoppingcartcommunity.com/forum/viewtopic.php?t=1449
Brandeline wrote:Wow, thanks for letting us know. That's awful. Most code that needs a license checks it once. Or just checks it in the admin and leaves the customer facing site alone.
Yes, very disturbing to see our site down for an extended period of time and not be able to do anything but put it in maintenance mode just when we are ramping up on our traffic. The functionality we can't do without because our product names are crazy and they need to stay that way but are bad for URL usage. Now I'm trying to see what the budget is looking like for getting someone else to write something to do the same thing.Martin wrote:Ah... so the module is encoded and requires a license check... Slightly worrying that it's required for EVERY visit.. That's just plain poorly thought out..
That's just poor, poor coding or abject paranoia... Worst case scenario I would have thought they'd have an encoded cache file that would record a successful authentication of the code for say a month, check once a day, at most (generating a fresh cache file each time it was successful) and thus fallback on that if it couldn't reach the mother server... It could even email their support to indicate a problem with your particular license so they could be pro-active but license checking whenever used just means you add a whole level of latency to the system and a bottleneck failover point as you discovered.MegaFemaTron2 wrote:The module and class file are both encoded. And no content shows without that licence checking working so you are correct Martin, it is required for EVERY visit.
With this, we are concerned with our magazine ads right now that have already gone to the magazines with URLs that won't work without this plugin. So whatever we're going to do, we have to do it quick.
Code: Select all
"productSortOrder" => array("dbfield" => "prodsortorder"),
'productTaxClass' => array('dbfield' => 'tc.name'),
'productUPC' => array("dbfield" => "upc"),
Code: Select all
'productURL' => array("dbfield" => "produrl"),Code: Select all
productTypeHelp = "This field will contain \'P\' for physical products or \'D\' for downloadable products."
productTaxClass = "Product Tax Class"
productUPC = "Product UPC"
Code: Select all
productURL = "Product URL"
I upgraded from 6.1.1 to 6.1.8 and even I did modify "\javascript\jquery\plugins\jstree\jquery.jstree.js" the category tree didn't displayed correctly.myshop wrote:6.1.8 is the best version yet - There is only one (new) show stopper - The new catgegory tree jquery plug in has a bug, but can be fixed by commenting out these three lines of code:
\javascript\jquery\plugins\jstree\jquery.jstree.js
if(c === "jstree-checked") {
$t.children(":checkbox").attr("checked","checked");
}
These are lines 2811, 2812, 2813
6.1.8 however still contains what I believe to be bugs caused by negligence on behalf of Interspire - For example, The Google Analytics ecommerce tracking code does not work with the Google Async tracking code - So you cannot use the ecommerce tracking features of analytics without hacking the module - This should be corrected by Interspire.
There are many other various problems which could be easily fixed - you know about them all if you follow this and the interspire forum.