Kimss Posted February 3, 2016 Share Posted February 3, 2016 Hi guys So, long story short. I upgraded to 1.6.1 and >> obviously << pretty much everything stopped working. Specifically for the purpose of this post: The one-page-checkout started throwing the error that it didn't find the customer's first and last name, despite those fields actually being filled. That problem turned out to be caused by my customized OPC-file. So I updated the file and did some customization. The standard file had the customer input her name twice, and then pulled the name information from the second set of input fields. Therefore I've swapped the code in the first set of fields with that of the second set and commented out the second set - getting the OPC to function properly again, without having the customer to input the same information more than once. The problem then, is that the BO now tries to pull the wrong name information. Apparently, it tries to pull the information from the original first set of fields, which I've changed so that they now use the code from the second set. In other words, my order- and customer-overview in the BO lists the customer names as "undefined", and the emails (order confirmation, shipping confirmation etc.) goes out with "undefined" when I use the shorthand {firstname} in the templates. The question is then: How do I fix this? More specifically, where can I see what Prestashop tries to pull when you use shorthand like {firstname}, and can I theoretically change that to any attribute from the OPC (like: id, name and so on )? Any help would be hugely appreciated! Link to comment Share on other sites More sharing options...
Kimss Posted February 4, 2016 Author Share Posted February 4, 2016 Bump Link to comment Share on other sites More sharing options...
obewanz Posted June 23, 2016 Share Posted June 23, 2016 Overwrite all of your custom files with their original 1.6.1.x files... a lot has changed in that part of the API. ... otherwise you may want to consider hiring a developer to customize the OPC correctly. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now