The 7.17.1 release has been deployed to all TNEW LIVE Sites.
For v6 & v7, the following updates were made. The full list of fixes included in this update is published in the v6 release notes section of the v6 TN Express Web User Guide and in the v7 release notes section of the v7 TN Express Web User Guide.
The 7.17.1 release also includes all of the updates originally published in the v7.17.0 release notes below.
For v7, additional fixes and enhancements were released including those outlined below. This is not a complete list. The full list of enhancements and fixes included in this update is published in the v7 release notes section of the v7 TN Express Web User Guide.
Within less than an hour of the v7.17.1 deployment message above, our box office reported two patrons who had "problems checking out as guests" and received a "server error." Several things are odd about this:
Is it possible that when this release was rolled out to Live sites, the guest checkout beta feature was somehow briefly exposed to the public and then disabled? If this is known to have occurred, is it now known to be fixed, or is there any chance it's an intermittent issue that we should be continuing to troubleshoot?
Thanks for any info.
EDIT: I see now that I missed something -- there is some text above the "Register" button on the login screen indicating that guest checkout is an option. Could that have just appeared tonight? I'm wondering if that is what confused our patrons. I'm going to edit that text and hope that's all it was.
Hi Christian,
Yes - the content above the "Register" button in v7 is migrated from Login.aspx/GuestChkText in v6's LTR_TN_EXPRESS_WEB_CONTENT system table. If the content in that field contained reference to guest checkout, then that could be the issue causing confusion with your users hoping to checkout as guest. I double checked your live site just in case but you are correct that guest checkout cannot be enabled on a site that is not running 14.1.10 or 15.0.2 so I do think you probably found the source of the issue being the content.
I am also wondering if the server errors were perhaps related to the timing of the deployment? Do let us know if you are getting reports of server errors as we would want to address that as soon as possible.
Thanks!Nara
Thanks, Nara. I almost forgot about the server error -- partly because I didn't see it myself. But at least two people confirmed seeing that when they clicked through to register a new account. It isn't happening now and we can't replicate it, so I bet you're right that it was the timing on the patch deployment. I think it's resolved and I'm not seeing any other issues at this time. Thank you for responding!