cluster Posted February 6, 2021 Share Posted February 6, 2021 I use a hook for checkout.tpl to generate a valid secure user password ... However, the password is not sent w/ v 8.10 in the welcome email, is there any way to integrate the password in the welcome email? I noticed that many customers quit their order when they are asked to enter a secure password again and again. The auto generate password button also makes no sense if the customer cannot see the password or it's not sent. 0 Quote Link to comment Share on other sites More sharing options...
cluster Posted February 7, 2021 Author Share Posted February 7, 2021 ### bump ### even if I remove the auto generate button, the ordering process is still unacceptable for new customers ... I tried at least to set the fields to autocomplete = "off" - which is ignored you first have to delete the password asterisks to be able to enter a new password Is there a way to get help on this? 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted February 7, 2021 Share Posted February 7, 2021 16 hours ago, cluster said: I noticed that many customers quit their order when they are asked to enter a secure password again and again. 16 hours ago, cluster said: The auto generate password button also makes no sense if the customer cannot see the password or it's not sent. they should see it in a modal window - are you using a a custom theme? 0 Quote Link to comment Share on other sites More sharing options...
cluster Posted February 7, 2021 Author Share Posted February 7, 2021 It seems my modal window function is probably being overlapped by the EU cookie bar crap 😉 Wouldn't it be possible to skip the password completely in the checkout for new customers? Maybe a welcome e-mail which contains a password reset link ... if a password can no longer be sent? The whmcs checkout is complicated for new customers (require lots of patience) if you compare with other order systems or shops. 0 Quote Link to comment Share on other sites More sharing options...
cluster Posted February 7, 2021 Author Share Posted February 7, 2021 ok, so I don't want to show the PW generator in checkout.tpl ... would it be possible to display the password directly as plain text when a customer entering it? that shouldn't be a security problem - or does it? 0 Quote Link to comment Share on other sites More sharing options...
cluster Posted February 7, 2021 Author Share Posted February 7, 2021 I have no idea how to solve these issues and will probably have to stay w/ whmcs 7.10 I can't create a completely new template right now 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted February 7, 2021 Share Posted February 7, 2021 2 hours ago, cluster said: Wouldn't it be possible to skip the password completely in the checkout for new customers? I suppose you could make them hidden fields, generate a password value and not bother the user... but then you have the issue that they would be unable to login to the client area in the future without having to go through the password reset process first. 2 hours ago, cluster said: Maybe a welcome e-mail which contains a password reset link ... if a password can no longer be sent? i'm not sure a welcome email could include a unique password reset link... obviously, you could still post the generic link to the password reset page... 2 hours ago, cluster said: The whmcs checkout is complicated for new customers (require lots of patience) if you compare with other order systems or shops. have you removed "unnecessary" fields from the form or tried to simplify it ? if you make the changes from the above thread, then more parts of the form will be remembered if there is an error on submission. 16 minutes ago, cluster said: ok, so I don't want to show the PW generator in checkout.tpl ... then remove it from the template. 20 minutes ago, cluster said: would it be possible to display the password directly as plain text when a customer entering it? you should just need to change the password input fields in checkout.tpl from input type="password" to input type="text". 21 minutes ago, cluster said: that shouldn't be a security problem - or does it? it's not ideal... especially if the user was ordering from a public location. 1 Quote Link to comment Share on other sites More sharing options...
cluster Posted February 7, 2021 Author Share Posted February 7, 2021 (edited) because of the PW modal window which is not displayed here .... I guess something is missing somewhere in the theme or is overlaid by other additional JS. Isn't the password stored in browser cache too when the modal window shows the generated PW? Edited February 7, 2021 by cluster 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted February 7, 2021 Share Posted February 7, 2021 10 minutes ago, cluster said: Isn't the password stored in browser cache too when the modal window shows the generated PW? not sure - doubt it would be if the user was using the browser's privacy mode when ordering 11 minutes ago, cluster said: because of the PW modal window which is not displayed here .... I guess something is missing somewhere in the theme or is overlaid by other additional JS. what happens when you run the site using Six & SC.... I assume the modal window appears then 0 Quote Link to comment Share on other sites More sharing options...
cluster Posted February 7, 2021 Author Share Posted February 7, 2021 I created a new order theme from the current standard-cart, the main theme is ecohost. The PW modal window in my custom order theme works when I set six as the main theme. 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted February 7, 2021 Share Posted February 7, 2021 3 minutes ago, cluster said: I created a new order theme from the current standard-cart, the main theme is ecohost. HTML or WP? looking at the changelogs, I don't think the HTML version has been updated for 8.1 yet. 5 minutes ago, cluster said: The PW modal window in my custom order theme works when I set six as the main theme. so it's likely a JS Clash with EcoHost - might be worth you contacting them to see what they say. 1 Quote Link to comment Share on other sites More sharing options...
cluster Posted February 7, 2021 Author Share Posted February 7, 2021 (edited) I would try without the PW generator, but in Chrome some data is always inserted (in my VAT custom field and in the first PW field). I'm not able to deactivate autocomplete in checkout.tpl, it's ignored. the customer should start with empty fields at checkout Edited February 7, 2021 by cluster 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted February 7, 2021 Share Posted February 7, 2021 7 minutes ago, cluster said: I would try without the PW generator, but in Chrome some data is always inserted (in my VAT custom field and in the first PW field). that's just Chrome's AutoFill feature isn't it - and nothing to do specifically with the form itself ? certainly, when I view my checkout form in Chrome, it's empty. you can always clear the AF cache for a given period if that helps your situation. 14 minutes ago, cluster said: I'm not able to deactivate autocomplete in checkout.tpl, it's ignored. I think various versions of Chrome react differently to autocomplete - with some releases not obeying it being turned off or disabled. 0 Quote Link to comment Share on other sites More sharing options...
cluster Posted February 7, 2021 Author Share Posted February 7, 2021 hmm, so chrome will always autofill when save passwords is set ... maybe an onLoad() function could work 0 Quote Link to comment Share on other sites More sharing options...
cluster Posted February 7, 2021 Author Share Posted February 7, 2021 (edited) autocomplete="new-password" works <input type="password" name="password" id="inputNewPassword1" class="field form-control" placeholder="Password"{if $remote_auth_prelinked} value="{$password}"{/if} autocomplete="new-password"> and <form method="post" action="{$smarty.server.PHP_SELF}?a=checkout" name="orderfrm" id="frmCheckout" autocomplete="off"> Edited February 7, 2021 by cluster 0 Quote Link to comment Share on other sites More sharing options...
cluster Posted February 11, 2021 Author Share Posted February 11, 2021 How can I hide the second (validation) password field (password2) in the checkout.tpl? The value of the first password field should be adopted in hidden password2 (validation). <input type="password" name="password2" id="inputNewPassword2" class="field form-control" placeholder="{$LANG.clientareaconfirmpassword}"{if $remote_auth_prelinked} value="{$password}"{/if} autocomplete="new-password"> intead of the PWvalidation I will add a show PW function. 0 Quote Link to comment Share on other sites More sharing options...
brian! Posted February 11, 2021 Share Posted February 11, 2021 17 minutes ago, cluster said: How can I hide the second (validation) password field (password2) in the checkout.tpl? change its type to hidden ? 🙂 0 Quote Link to comment Share on other sites More sharing options...
cluster Posted February 11, 2021 Author Share Posted February 11, 2021 yeah, but the validation will block the submission afterwards when password2 value is empty or different 😉 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.