By default, PrestaShop does not allow setting the customer's DNI (National Identity Document) when creating an account. Instead, the field is saved at the address level, which for some cases is not the most appropriate. There's also no additional validation for the DNI field; a customer can have multiple addresses with different DNIs, and even the same DNI can be used for multiple addresses for different customers. This module adds a new field to the registration and edit form of the customer, changing the handling of the DNI field at the customer's personal information level. The module also provides additional validation options for the DNI field, such as making it required, unique, and validating it against a regular expression.
- Adds a new field to the registration and edit form of the customer, allowing them to save their DNI.
- Displays the DNI field in the back office as well, so it can be easily viewed and edited by back office users. It also displays the DNI in the customer list.
- Allows setting the DNI as required, unique, and validate it against a regular expression using the module's configuration page.
- Option to overwrite the DNI field of the addresses when the customer DNI changes, so that value is copied to all the addresses of that customer. Useful for modules that use the address DNI field.
- Additional validations can be added by uploading a custom validation class inside the module's
custom_validatorsfolder. The module includes a custom validator that checks if the DNI is a valid chilean RUT. - The DNI is stored in a new table in the database, linked to the customer's ID, so it can be easily retrieved and used in other modules or customizations.
- Provides custom hooks to add additional functionality programmatically.
- The module is fully translatable.
- Tested on PrestaShop 8.1, but should work on any version of PrestaShop 1.7.7 or higher.
- PHP 8.0 or higher.
- Composer, to generate the necessary autoload files.
- Download this repository to a folder named
customer_dni. - Enter that folder, and run the following command to generate the necessary Composer autoload files:
composer dump-autoload -o --no-dev- Compress the folder into a ZIP file.
- Upload the ZIP file to your PrestaShop instance. You can do this by going to the back office of your PrestaShop store and navigating to the
Modulessection. Click on theUpload a modulebutton and select the ZIP file you just created. You can also upload the ZIP file directly to themodulesfolder of your PrestaShop installation. If you choose this method, make sure to extract the ZIP file after uploading it, so thecustomer_dnifolder is created inside themodulesfolder. - After uploading the ZIP file, the module should appear in the list of modules in the back office, where you can install it.
- Once the module is installed, click on the
Configurebutton to access the module's configuration page. - Configure the module according to your needs and save the changes.
- The module is now ready to use. The DNI field should be displayed in the registration and edit form of the customer.
The module has a configuration page where you can set the following options:
- Display customer DNI in back-office: Show the DNI field in the customer list of the back office, which also allows filtering and ordering by DNI value.
- Mark as required: Make the DNI field required in the registration and edit form of the customer.
- Mark as unique: Make the DNI field unique, so the same DNI cannot be used by multiple customers.
- Overwrite address DNI field: Overwrite the default DNI field in the address form, so when the customer saves the DNI in the customer form, it is also saved in the address DNI field for all the addresses related to that customer. Keep in mind that the default DNI field for the address has a maximum length of 16 characters, so if the customer DNI is longer than that, it will be truncated.
- Validate against a regular expression: Set a regular expression to use for validating the DNI.
- Use custom validators: Enable the use of custom validators for the DNI field.
You can upload a custom validation class inside the module's
custom_validatorsfolder to add additional validations to the DNI field.
Once the module is installed and configured, the DNI field should be displayed in the registration and edit form of the customer. The DNI field is also displayed in the back office, so users with customer edit permissions can easily edit it.
The DNI field is stored in a new table in the database, linked to the customer's ID.
Upon resetting or uninstalling the module, the DNI field will be removed from the customer form, but previously saved DNI data will remain in the module's customer_dni table.
You can use the DNI field in other modules or customizations by retrieving it directly from the database table customer_dni using the customer's ID.
You can customize the module by adding additional validators for the DNI field.
To do this, add a custom validator class that implements the CustomValidator interface to the custom_validators folder.
The module has a built-in custom validator that checks the DNI against the chilean RUT format.
You can use this class as a reference to create your own custom validator.
The module also offers two custom hooks that can be used to add additional functionality programmatically:
actionCustomerDNIAddAfter: Triggered when the customer DNI is saved to the database, being either a new DNI or an update to an existing one.actionCustomerDNIDeleteAfter: Triggered when the customer DNI is removed from the database, which usually happens when the customer is deleted. This hook will trigger even if no DNI was associated with the customer at the time of deletion.
Both hooks return the customer ID and the DNI value as parameters.
This module is released under GNU General Public License version 3. You can find a copy of the license in the LICENSE file.
Ideas for future improvements not covered in the current version of the module:
- Add support for PrestaShop 1.7.6 and earlier versions.
- Allow selecting the location of the DNI field in the customer form of the front office (e.g., before or after the email field).
- Validate the DNI during customer creation through the API.
- Define hooks to add additional custom validations to the customer's DNI programmatically.