Automatic Customer Password: setup and help

1. Upload the Automatic Customer Password ZIP in Modules > Module Manager.
2. Open Configure > General.
3. Set Apply To to the account flow you want to test.
4. Choose Password Field Behavior and Email Mode.
5. Review Strength Rules and save.
6. Create a test account, check its email and verify that you can sign in.

Requires PrestaShop 1.6 or later and PHP 7.1 or later.

Registration targeting includes authentication, registration and identity. Checkout targeting includes order, orderopc and order-opc.

Only detected account-creation forms are filled on the selected pages. Existing-customer login and account identity forms are excluded. In optional mode, existing field values are preserved. New-account emails are sent only after registration through a form marked by the module.

Lowercase letters are always included. One password is generated in the browser for the page, then used to fill detected password and confirmation fields as needed. The normal PrestaShop account form submits it. Generation and shuffling use the browser's cryptographically secure crypto.getRandomValues. If that API is unavailable or fails, the script leaves the account form unchanged.

With Enable Automatic Password on, the module handles new-account email for registrations through forms marked by the module, including an edited password in optional mode. In password email mode, it emails the password submitted with the account form. It does not generate a second password on the server.

On versions with native reset tokens, setup-link mode stores a token valid for 24 hours and emails a link to the native password page. On PrestaShop 1.6, the link uses the native flow to generate and email a new password; customers can then sign in and change it in My account. The module does not store a reset token or promise 24 hour expiry on 1.6. Test the received link before using this mode on a live shop.

Silent mode suppresses only this module's password email. Native shop account emails can still be sent. Customers use normal account and password-reset facilities after registration. The module does not convert guest orders or back-office accounts by itself.

• Create a test account on each selected page type. Confirm hidden fields are filled, or that visible fields can be edited and confirmation fields follow the change.
• Confirm the normal account submission succeeds and the email mode behaves as selected. For setup links, follow the received link and test the new password.
• Test existing-customer login, identity changes and forms injected during checkout. The script observes inserted form content, but custom account flows may not match its selectors.
• If fields are not handled, inspect JavaScript loading and the displayHeader and actionFrontControllerSetMedia hooks. Standard input names include password, passwd, confirmation and password_confirmation.
• If account creation succeeds but the module email is missing, check for the mprcustpass_auto hidden field and test PrestaShop mail delivery. Social-login flows that bypass the password form may never add the flag.

The module includes these mail templates, each in HTML and text versions:

mails/en/mprcustomerpassword_account.html
mails/en/mprcustomerpassword_account.txt
mails/en/mprcustomerpassword_setup.html
mails/en/mprcustomerpassword_setup.txt

Both email types receive {firstname}, {lastname}, {email}, {shop_name} and {shop_url}. Password emails also receive {passwd}. Setup emails receive {setup_link}, {setup_instructions} and {setup_validity}. Setup templates are also supplied under mails/de/, mails/fr/, mails/pl/, mails/it/ and mails/es/; password email templates are supplied in English.

For a setup message, preserve {setup_link}, {setup_instructions} and {setup_validity} so the wording follows the native password flow. The validity text is empty on PrestaShop 1.6. For a password message, place {email} and {passwd} where you want the account credentials to appear.

Use .mprcustpass-info to style the notice. Use input[data-mprcustpass="1"] to style prepared password fields. Preserve normal input names in customized account templates.

Turn off Enable Automatic Password to stop the module behavior. Uninstall from Module Manager to remove its menu entries and module configuration. Existing customer accounts and their stored passwords remain in PrestaShop.