M@rcel

To be certain, I've doublechecked my own store. Everything works as expected, even during checkout. The old prices are not shown during checkout, only the deducted prices are visible. I suspect that some other contribution is interfering with SaleMaker. Or perhaps your installation is not entirely correct? Are there other Salemaker-users that can comment on this? Marcel

Like this? http://www.oscommerce.com/community/contributions,1202

Right Deborah, The shopping cart only shows the new "on sale" price. Did you enable the sale by clicking on the green button?

8) 8)

Can you report back here, after installing, if SaleMaker does what you want it to do? I am always in for improvements (if feasible).

AutoLogon 1.03 is NOT compatible with MS2. I'll start working on this as soon as I find the time.

Does this mean that the problem is not SaleMaker related?

Can you give me an url to test?

Thanks for the feedback! I'm glad it works! And remember: We're all just humans :D

International dates were not handled correctly. Fixed. Update instructions are in the ReadMe. SALEMAKER NEEDS AT LEAST OSC 2.2MS2 TO FUNCTION CORRECTLY!

Could you email me the hmtl-source of your checkout_confirmation page? Just do a view source in your browser. I'll pm you my private emailaddress.

There are two modules in the contributionssection. Which do you use?

Hmm, I'll have to look into this. Which payment module do you use?

Just to make sure we are talking about the same thing here: You need OSCommerce 2.2MS2 (released today!)

Ok, this is what I've done: I downloaded and installed a fresh copy of OSCommerce 2.2ms2. I downloaded and installed the contribution. Everything works as expected. But: You need ms2 Javascript must be enabled in your browser

Remember: You need MS2 to install this successfully!

Added some screenshots. Look for them in the contributions.

The "Must Agree To Terms" contribution enhances standard OSC Checkout logic by forcing the customer to agree to the store's terms in order to place a new order. Use only on MS2 or above Find it here

The "Must Agree To Privacy-statement" contribution enhances standard OSC account-creation by forcing the customer to agree to the store's privacy-statement in order to create his/her account. Module is to be used with Milestone 2 and above. Do not use with older versions! Find it here

The SaleMaker contribution provides store-owners with the necessary tools for defining, managing and exploiting StoreSales. Use only with MS2 and above! Find it Here

I don't know this contribution, but perhaps you have cache enabled in your admin. Check configuration/cache. You can clear the caches in your admin: tools/cache control. The caches will automatically be recreated. If this doesn't fix it: sorry, it's all I can think of.

Great! thank you, Harald :)

The restore button in admin should also restore the ordercontents into the cart.

Warren, I think that the problems lies in the way osc handles order-statuses. There is no way in osc to define in which order the statuses are. It are just self-incremental values. The contrib, however, uses a highest status to prohibit the restoration of an order. The statusnr for "received" may be higher (or lower) than "shipped". A solution? mmmm. I think it would be best if one could enumerate the statuses in admin with a multi-select dropdown. These are, however, not (yet) implemented in admin. HTH

Thanks for the feedback :D