Jump to content


  • Content count

  • Joined

  • Last visited

  1. Well, lemme answer part of my own question. The fact that I'm indirectly suggesting that tax should be applied to purchases fully covered by a voucher is most likely double jeapordy. The tax would have been collected on the original voucher purchase. I definitely need to play with the "include/exclude" settings more for coupons and GV's to get a better sense of how this works. Anyone have any recommendations on simple, vanilla values to for GV and coupon tax settings that make sense? Thanks.
  2. Just finished installing, and something has me concerned. I like how the mod turns off the payment options buttons if the available vouchers cover the total purchase. However, if I have tax and shipping set to be excluded from voucher use, the system apparently doesn't provide me with the ability to pay those amounts (i.e., I never get to choose a payment option for the few dollars I'll owe). Am I missing something? Thanks. - Mike
  3. zman818

    Google Analytics module

    For example... <?php // set in app_top //$request_type = (getenv('HTTPS') == 'on') ? 'SSL' : 'NONSSL'; if ($request_type == 'SSL') { ?> <script src="https://ssl.google-analytics.com/urchin.js" type="text/javascript"> <?php } else { ?> <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"> <?php } ?> </script> <script type="text/javascript"> _uacct = "UA-xxxx-x"; urchinTracker(); </script>
  4. zman818

    Google Analytics module

    Thanks for the contribution. Just a couple comments... The analytics.php versions for ssl/non-ssl are identical. It would probably make sense to distribute one copy only, in order to avoid confusion and facilitate editing/updating in the future. Additionally, you could use the SSL/Non-SSL conditional logic already included throughout much of osCommerce to eliminate the need for two checkout_success versions as well. Your placement of the urchin.js reference outside of the HEAD section is incorrect. Google directs users to place the urchin.js script reference within the HEAD section. (<script> tags should only appear within the HEAD or BODY sections. Placing them anywhere else is technically invalid). Your approach might work today, but might not tomorrow.