If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Although I thought I did ask a question, thanks for the suggestion on mvt:assign. I forgot that this was introduced into morph until after my original question was posted. I actually used that solution earlier this morning with success.
What I'm actually trying to do is update the shipping method prices for all the methods in the array at the OSEL page. While I am able to update the values using mvt:assign, I can't seem to figure out how the selected shipping method's price value is passed to the OPAY page. I figured it would be pulled from the array, but I was mistaken.
oh don't mind me...having one of those mornings...but i do encourage folks to ask "how do i get this result" and not "how to do this thing I'm doing" cause often times the answers are different, and so are the outcomes (i.e., you don't get the result you want).
Ah, well, unfortunately it's not easy to get there from here. Any 'price' related data shown on the front side of miva is there as a 'read' only value. The actual value that gets loaded into the database is pulled anew based on the selections a customer makes. You'd need to use Marketing rules (if possible) or possibly some heavy duty SMT scripting.
Thanks. That's what I figured. I'm trying to figure out where it pulls this information before saving it to the basket_charges table. Is it recalculating it after submitting the OSEL form or is there a temporary table that holds the values calculated when OSEL opens? Maybe it would be better to update this on the OPAY page.
A bit of both, you'd have detect the need to change OSEL, but process it on OPAY. There is an additional problem here in that you'd have to also repeat the local frontside pricing shown on OPAY as the OPAY data has already been constructed and output to the page based on the original values of OSEL. The only workaround would be to do the Basket Charge table changes as an ajax call, probably attached to the action of making the shipping selection. This type of thing better accomplished with a module as modules let you make changes 'in between' pages.
Comment