So forgive me if I am wrong on this, but when you designate a Sub Mos in the LTR_TN_EXPRESS_WEB_DEFAULTS table, is TNEW not supposed to automatically shift users into this MOS when they are sent to TNEW using the /packages or /packages/renewals URLs? We are working on setting up our renewal campaign and need to test somethings but I can't get any published packages to display on the /packages URL. The /packages/renewals does the MOS shift and displays the applicable renewal orders. I don't remember us needing to use any sort of promo code triggered MOS shift other than for specific pre-sales but once those ended I think people were always sent to the generic link. I added the keyword, the MOS is currently active, its just not moving people into that MOS.
So I'm either misremembering how the package link is supposed to work, or there is some other detail I've forgotten?
v15 or v16? There's a bug in v16 around this. There's always been some weirdness in my experience, where the MOS seems to not be changed initially but is at some further point in the process.
We're still in V15 in live. Thing is I created a promo code to shift into the correct MOS just so I could test the things I wanted to, but even after forcing it into the correct MOS, the packages were still not displaying.
In case it is something simple, did you Reset the Custom Forms and Cache in the TNEW Admin (assuming you use TNEW)? I've been stung by that issue too many times.
I'm pretty sure my last forum post here was just an issue with not resetting the cache, so I've been trying to make a habit of doing that before I post or submit tickets to Tessitura.
I like to think of it as I'm standing right next to a huge billboard sign with the text "Reset Custom Form and/or Cache lately?" I'm too close to it to see the sign. Remembering to zoom out to see the sign can be the hard/frustrating part.
I've been that guy. Also, the "why are you formatting this form field with 9 unicode characters (because it seems to have taken the site down)?" guy
Not so much with unicode for me, but I was certainly the guy that took all of our performance pages down for a half a day because of a misplaced ending brace, "}", character and an if/then statement that is only actually processed on 1% of our performance pages but decided that day was going to make itself known.
Did you know that if you accidentally include two TNEW aliases for the same Payment Method you take down payment processing for every site in your consortium?