Skip to content

State what the phone number is used for on the checkout form#100

Open
boo-code wants to merge 2 commits into
PrestaShop:mainfrom
boo-code:feat/phone-purpose-hint
Open

State what the phone number is used for on the checkout form#100
boo-code wants to merge 2 commits into
PrestaShop:mainfrom
boo-code:feat/phone-purpose-hint

Conversation

@boo-code

@boo-code boo-code commented Jul 5, 2026

Copy link
Copy Markdown
Contributor
Questions Answers
Description? The optional phone field gives no reason for asking, and buyers hesitate to hand out a phone number; checkout research recommends stating the purpose next to the field. This adds a translated hint under the delivery and invoice phone inputs — "Only used if we need to contact you about the order or its delivery." — set server-side in AddressFieldsFormatTrait through the FormField availableValues.comment slot the theme's form-fields.tpl already renders as a form-text line (no theme or JS change). Item 4 of #96.
Type? improvement
BC breaks? no
Deprecations? no
Fixed ticket?
How to test? vendor/bin/phpunit -c tests/php/phpunit.xml --filter AddressFieldsFormatTraitTest (asserts the comment on the phone field and its absence on other fields). On a 9.2 checkout the hint renders under the Phone input next to the "Optional" marker — verified live.

@ps-jarvis

Copy link
Copy Markdown
Collaborator

Hello @boo-code!

This is your first pull request on ps_onepagecheckout repository of the PrestaShop project.

Thank you, and welcome to this Open Source community!

@ps-jarvis

Copy link
Copy Markdown
Collaborator

This pull request seems to contain new translation strings. I have summarized them below to ease up review:

  • Modules.Onepagecheckout.Shop ⚠️
    • Only used if we need to contact you about the order or its delivery.

(Note: this is an automated message, but answering it will reach a real human)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Ready for review

Development

Successfully merging this pull request may close these issues.

2 participants