We are getting our Test database ready to go for our V16 upgrade. Part of that process means converting all our LWP_VALIDATE_CART validation logic over into their own stored procedures. I've got all the stored procedures built and setup for TNEW to access them but when I try to test it out, the customizations are not activating the pre-cart messaging.
I found the applicable @sessionkey for the order and ran that parameter through my procedure directly in the database. And the HTML meant to be returned for that order is displaying in the results for the procedure. But its not sending me to that message when attempting to trigger that message on our test TNEW site.
Has anyone else successfully converted over to stored procedure customizations and might have an idea of what I'm missing? The documentation stated that the procedures will need a null able @siteroot parameter, so that was there. I commented it out and tried it again but it still did not work. I've setup the rows in TR_LOCAL_PROCEDURE, LTR_TNEW_VALIDATE_CART and enabled the procedures in the TNEW Site admin page. I enabled execute permissions to all ImpUsers. V3 customizations are turned on for our Test site. The item type I am currently testing is for Single Ticket added.
In case anyone was following this post or stumbles upon it. I did figure out what I was doing wrong. The stored procedure customization method requires a variety of additional parameters: @query, @form, @payload, @meta. I was under the impression these were optional since I only referenced the @sessionkey parameter in the procedure itself. But after adding those parameters in as nullable parameters, the customizations started working.
Hey Jesse, sorry have been ludicrously busy - sounds like you worked it out - if you are having trouble catching parameters from TNEW with a stored procedure I can jump on a call with you or give you a buunch of form data catupres I've previously done.
Heath, since I last posted I was able to get the base pre-cart customizations to trigger, however some of our features trigger forms for user data collection that are handled by another stored procedure that is called through a form post with a submit button. This is where I am still having trouble. I know you mentioned you are pretty busy so I don't want to take up too much of your time. If you are willing to send me some of your captures, I can see if I can sort through it. Thanks!
Hey Jessie. Sorry for the delay. Off the back of this we had a long running crisis, so I let it slip. Will send some examples in a DM