Closed (works as designed)
Project:
Commerce Checkout Progress
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
4 Apr 2012 at 23:19 UTC
Updated:
24 Jul 2015 at 14:26 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
applicity_sam commentedThe attached patch makes the change in behaviour described. I have added a configuration option so that it will not change the behaviour for existing implementations. You will need to check the box in the module configuration in order for the new behaviour to be seen.
Comment #2
andrewbelcher commentedRather than duplicating code, which could lead to similar issues, we switch to using
commerce_checkout_page_access()which is specifically for this?Patch attached.
Comment #3
nvahalik commentedTagging related issue already in the queue.
Comment #4
nvahalik commentedTwo reasons why I'm opposed to this change.
The first is that
commerce_checkout_page_accesswon't allow it either because it disallows access to any checkout page whose weight is greater than it's own:The second is that being able to navigate to any point visited in the checkout process could cause issues. For instance, let's say I have these steps:
Now, for one reason or another I travel to gift information, which then changes which shipping options are available, the customer won't have a chance to choose their shipping option again because they won't see it let alone know that the options have changed. Keeping track of these changes are also likely complex and probably more trouble than what it's worth.
Maybe rszrama or mglaman might have more to say.
Comment #5
mglamanYeah, I think you shouldn't be able to skip back three pages then resume, order information might become stale, etc. "Here let me hijack my shipping info..." because it's on its own page (by default.) I also don't think I've seen this functionality else where and it'd go against how Commerce Checkout operates.
In my honest opinion this module is a user experience enhancement of the main module, not something to alter how it functions at its core.
Comment #6
nvahalik commentedComment #7
andrewbelcher commentedWhat about making it an option? Our use case is a booking system that you can come back to multiple times to add tickets/adjust accommodation and make either whole of partial payments (ie deposits/instalments).
Due to those exact issues, we have a number of checks that happen at the final 'payment' stage, so people can't pay a deposit/instalment/balance without passing checks (such as enough accommodation for the tickets added). An option, would allow these 'advanced' processes to work.
Comment #8
nvahalik commented@andrewbelcher: It sounds like a one-off use. Patches are always welcome. Until those links can be trusted to properly ensure form state, the safest and only supported way to navigate forward in the checkout process is to use the form buttons at the bottom.