• Replies 15 replies
  • Subscribers 246 subscribers
  • Views 100 views
  • Users 0 members are here
Related

TNEW Package MOS

Jesse Dillman
$organization

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?

Parents
  • $organization

    In case anyone was wondering, turns out it was an issue with the web publish dates for the individual performances. Even though they had no keywords on them, I was still weary about making sure they did not appear online, so I dated them to start way out to when we would start selling them as individual performances and apparently that can prevent the packages from displaying properly. In my response to the ticket, I suggested they include that in the documentation for "Displaying Packages" online.

    As for the MOS shift issue, I was just misunderstanding how it worked. In the package setup in the Component editor on the admin page, there is an option to force a MOS shift when accessing the packages page, and ours was turned on, I just didn't realize the MOS shift was actually happening.

Reply
  • $organization

    In case anyone was wondering, turns out it was an issue with the web publish dates for the individual performances. Even though they had no keywords on them, I was still weary about making sure they did not appear online, so I dated them to start way out to when we would start selling them as individual performances and apparently that can prevent the packages from displaying properly. In my response to the ticket, I suggested they include that in the documentation for "Displaying Packages" online.

    As for the MOS shift issue, I was just misunderstanding how it worked. In the package setup in the Component editor on the admin page, there is an option to force a MOS shift when accessing the packages page, and ours was turned on, I just didn't realize the MOS shift was actually happening.

Children
  • $organization in reply to Jesse Dillman

    Yes.  Which is why I think displaying packages really should have their own thing.  They have their own "on sale" logic.  Why not also their own "display" logic?  The distinction these days between what is visible in the application to staff and what is visible online to the public is a VERY fine line indeed, and BOTH have reasons to be tightly controlled for their own purposes, irrespective of related performances/packages/etc...