james66 Posted March 4, 2011 Share Posted March 4, 2011 I can't find any add-ons for 2.3.1 which would give a one-page checkout or even reduce the tedious process of checking out with the standard version. As a minimum I want to get rid of the requirement to force customers to generate an account with password. I can't be the only one who sees the long-winded checkout procedure as a major sales prevention tool. From sifting thro' the forums I gather there are some significant problems in fixing any 2.2 add-ons to work with 2.3.1 (by significant I mean beyond my very limited abilities). So, the cry for help (this time) is - has anyone else configured their 2.3.1 site to: a) remove the need to open an account in order to place an order; B) reduce the number of steps in the checkout process. If so I would be very grateful for any details, tips, file, code changes etc. Many thanks to anyone who can help. Link to comment Share on other sites More sharing options...
Xpajun Posted March 4, 2011 Share Posted March 4, 2011 this page might be of help to you. My own thoughts: on one page checkout is that it always looks very cluttered and often difficult to understand On payment without account - people that use this type of checkout are only after a single sell otherwise they'd allow you to store your account details so you don't have to tediously fill in your details each time you buy. If you want to speed up the checkout offer just one shipping and payment method - unless you are doing downloads only you'll always need the customers address details so Gary's idea above is a good work around My store is currently running Phoenix 1.0.3.0 I'm currently working on 1.0.7.2 and hope to get it live before 1.0.8.0 arrives (maybe 🙄 ) I used to have a list of add-ons here but I've found that with the ones that supporters of Phoenix get any other add-ons are not really neccessary Link to comment Share on other sites More sharing options...
james66 Posted March 4, 2011 Author Share Posted March 4, 2011 this page might be of help to you. My own thoughts: on one page checkout is that it always looks very cluttered and often difficult to understand On payment without account - people that use this type of checkout are only after a single sell otherwise they'd allow you to store your account details so you don't have to tediously fill in your details each time you buy. If you want to speed up the checkout offer just one shipping and payment method - unless you are doing downloads only you'll always need the customers address details so Gary's idea above is a good work around I thought I was on to a winner until I looked at the code - this is for 2.2 - the 2.3.1 code is completely different . Has anyone found something suitable for 2.3.1? Link to comment Share on other sites More sharing options...
burt Posted March 4, 2011 Share Posted March 4, 2011 "the 2.3.1 code is completely different" Very little difference between 2.2 and 2.3.1 on the create_account page. Link to comment Share on other sites More sharing options...
Xpajun Posted March 5, 2011 Share Posted March 5, 2011 I thought I was on to a winner until I looked at the code - this is for 2.2 - the 2.3.1 code is completely different . Has anyone found something suitable for 2.3.1? I think you have been reading too many posts from the pro coders :-" 2.3.1 code is NOT completely different - just changed slightly for instance this 2.2 code in Gary's coding I referred to <tr> <td class="main"><b><?php echo CATEGORY_PASSWORD; ?></b></td> </tr> <tr> <td><table border="0" width="100%" cellspacing="1" cellpadding="2" class="infoBox"> <tr class="infoBoxContents"> <td><table border="0" cellspacing="2" cellpadding="2"> <tr> <td class="main"><?php echo ENTRY_PASSWORD; ?></td> <td class="main"><?php echo tep_draw_password_field('password') . ' ' . (tep_not_null(ENTRY_PASSWORD_TEXT) ? '<span class="inputRequirement">' . ENTRY_PASSWORD_TEXT . '</span>': ''); ?></td> </tr> <tr> <td class="main"><?php echo ENTRY_PASSWORD_CONFIRMATION; ?></td> <td class="main"><?php echo tep_draw_password_field('confirmation') . ' ' . (tep_not_null(ENTRY_PASSWORD_CONFIRMATION_TEXT) ? '<span class="inputRequirement">' . ENTRY_PASSWORD_CONFIRMATION_TEXT . '</span>': ''); ?></td> </tr> </table></td> </tr> </table></td> </tr> <tr> <td><?php echo tep_draw_separator('pixel_trans.gif', '100%', '10'); ?></td> </tr> Has been changed to this in 2.3.1 <h2><?php echo CATEGORY_PASSWORD; ?></h2> <div class="contentText"> <table border="0" cellspacing="2" cellpadding="2" width="100%"> <tr> <td class="fieldKey"><?php echo ENTRY_PASSWORD; ?></td> <td class="fieldValue"><?php echo tep_draw_password_field('password') . ' ' . (tep_not_null(ENTRY_PASSWORD_TEXT) ? '<span class="inputRequirement">' . ENTRY_PASSWORD_TEXT . '</span>': ''); ?></td> </tr> <tr> <td class="fieldKey"><?php echo ENTRY_PASSWORD_CONFIRMATION; ?></td> <td class="fieldValue"><?php echo tep_draw_password_field('confirmation') . ' ' . (tep_not_null(ENTRY_PASSWORD_CONFIRMATION_TEXT) ? '<span class="inputRequirement">' . ENTRY_PASSWORD_CONFIRMATION_TEXT . '</span>': ''); ?></td> </tr> </table> </div> It is still findable and since the only change you will be doing to it is deleting it... And that is the only difference in the whole of his code. Don't be put off by the scaremongering posts that say 2.3 code is different My store is currently running Phoenix 1.0.3.0 I'm currently working on 1.0.7.2 and hope to get it live before 1.0.8.0 arrives (maybe 🙄 ) I used to have a list of add-ons here but I've found that with the ones that supporters of Phoenix get any other add-ons are not really neccessary Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.