Hi all,
I've created a new delivery method (Special Delivery Postage) which I only want available online on one performance. At the moment, it's appearing on all productions with the Internet MOS.
For some of our productions, we've used LTR_TNEW_DYN_SHIPPING_METHOD to limit certain productions to e-ticketing only. But, as this is for merchandise, we need the options for standard posting, and collection at box office, to still appear in the drop-down, along with the Special Delivery option.
Is there a way to remove this new delivery method from all productions, and to then make it only available as an option on one?
Many thanks,
Hannah
Not easily. LTR_TNEW_DYN_SHIPPING_METHOD works in two ways. If a performance is not listed, then all shipping methods are available. If at least one shipping method is listed, then only listed shipping methods are available. Managing that table is such a bear (for instance, we only turn on print-at-home shipping for all shows in our new season after our initial unseated subscription sales period has ended) that I built an management utility to help our Box Office.
But basically if you have any kind of global restriction, it means that every show has to have all of its legal shipping methods explicitly entered into the table.
Thanks Gawain, that's what I feared!
You can try coding a checkout customization to interrupt and correct things that are wrong; either by changing the delivery method on them if they choose that delivery method for a performance that should not have it, or you can force them into that delivery method if they DO have that performance (and possibly additional criteria), but that is obviously not the greatest solution. That said, we are getting ready to go live with our own TNEW site soon, and we will be doing that for some things because we have similar situations.
What I have is a system that lets the Box Office control shipping methods on performances using Keywords (which is how it should be set up, frankly). Since that involves running a sql job that re-writes the LTR_TNEW_DYN_SHIPPING_METHOD based on keywords that it finds, I also had to create a secondary table to configure other, standard shipping method controls, particularly for things that didn't accept keywords (we needed to at least be able to specify Gift Certificates' shipping restrictions). I can share it if people are interested.
That'd be wonderful Gawain. My LTR_TNEW_DYN_SHIPPING_METHOD is almost as out of control as my LTR_TNEW_DYN_PAYMENT_METHOD
I've been reviewing it, and it needs some work, actually. For convenience, if I detected a change, then I just deleted all of the current entries in LTR_TNEW_DYN_SHIPPING_METHOD and regenerated it. Not the most efficient thing, but I didn't think it would be a problem.
But now I see that the id column is approaching 3 million, so I think I need to make it just a little more sophisticated... Maybe in time for the conference!
Does anyone remember if v7 handles this differently/better?