[BUG] Better default wording for selling virtual products, services or mixed content

Open Beginner friendly
#93 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
php
Domain
payments

Research direction

Review payment_return.tpl, bankwire.html.twig, and ps_wirepayment_intro.tpl, starting with the three wording locations identified in the report. Reproduce a bank-wire order to view the payment page and notification email. Done means the default text is suitable for digital products, services, and mixed orders without implying physical shipment.

Written by the indexing model from the issue text.

Description

Prerequisites
Describe the bug and add attachments
  1. In the payment_return.tpl file (Thank you page in the order process), there is the sentence:
    "Your order will be sent as soon as we receive payment."

I suggest removing this sentence or replacing it with a more universal one, because the merchant may be selling digital products, services, or mixed content that cannot be "sent" in the traditional sense.

More universal wording:
"Your order will be processed once payment is received."

  1. Correct wording in the notification email template - bankwire.html.twig:
    "You can expect delivery as soon as your payment is received."

  2. ps_wirepayment_intro.tpl file

"_Goods will be reserved %s days for you... _"

Please make better default module texts for universal use.

Expected behavior

Last page of the payment process.

Steps to reproduce
  1. Make testing order, use Bank wire module
  2. Check the last payment page and bank wire email notification
PrestaShop version(s) where the bug happened

ps_wirepayment 2.2.1

PHP version(s) where the bug happened

8.1

Your company or customer's name goes here (if applicable).

No response

Dominant language
PHP
Stars
17
Forks
41
Avg merge
19h 22m
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.