-
-
Notifications
You must be signed in to change notification settings - Fork 437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add email link to set password. See issue #1205. #1283
Conversation
<p class="highlighted-text"> | ||
Use the following values when prompted to log in:<br/> | ||
<strong>Email</strong>: {{var customer.email}}<br/> | ||
<strong>Password</strong>: (the password you set) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't this line redundant/confusing? (considering that the main call to action in this email is to click a link and set a password, therefor they don't have one already set?)
@@ -49,6 +49,7 @@ public function render(Varien_Data_Form_Element_Abstract $element) | |||
if ($element->getNote()) { | |||
$html .= '<p class="note"><span>' . $element->getNote() . '</span></p>'; | |||
} | |||
$html .= '<p id="email-passowrd-warning" style="display:none;" class="note"><span>' . Mage::helper('customer')->__('Warning: email cotains password in plaintext will be sent.') . '</span></p>'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this isn't true because a link is sent instead of a password? this email template sends (the password you set when creating your account)
in place of the password.
IMO the automatic email for a manually set password should be removed (if the manual password set feature is retained).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's also a couple of typos: cotains
and email-passowrd-warning
Warning: an email containing the plaintext password will be sent.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO the automatic email for a manually set password should be removed (if the manual password set feature is retained).
Hmmm... but it's hard to know if a use case exists where it's necessary to send a plaintext password to customer.
Anyway, the objective of this PR is to provide the UI for the backend admin to email a link to set password, especially for customer accounts created in the backend. The automatic email is an existng feature that can be addressed separetely, I don't want to do too many things.
* Better exceptions for file upload * PHPCS fixes * PHPCS fixes
Instead of checking the results of preg_match by counting the length of the string, simply check for the success value. This prevents PHP 8.1 deprecation warnings.
…e#1490) * New event so more validation classes can be added on the fly I ran into a situation where I needed more complex validation rules like min and max length for strings and min and max values for integers. Without this change, I cannot make it. * Added missing cast to array * resolve codestyle issue * change arrays append to ArrayObject->append() Co-authored-by: Daniel Fahlke <[email protected]>
…penMage#1490)" (OpenMage#2910) This reverts commit a22d834.
… js/prototype/validation.js (OpenMage#2609)
I tried to rebase by following this guide: https://gist.github.com/scottyhq/299e4d36018a2f13acfb2528a1553002. But it doesn't seem to work. Is there a guide I can use to rebase? |
I follow this guide from @colinmollenhour and it works perfectly: OpenMage/rfcs#10 (comment) (I always use the "squash" part of the guide) |
I would close this PR and create a new one because the number of modified files appears to be +5000, being attached from other PRs. I can't test it because there are too many conflicts. |
See PR #3262 |
Description (*)
When a customer account is created in backed, the password should not be emailed in plaintext. This PR add a new email template, which is modifed from the welcome email, by adding a link to set password.
For existing account, the email template used is the same as the forgot-password email.
This PR does not change existing feature on emailing plaintext password from backend, but it'll show a warning:
Related Pull Requests
Fixed Issues (if relevant)
Manual testing scenarios (*)
There are 2 scenarios:
Creating New Customer
Existing Customer
Questions or comments
The landing page of the link is
customer/account/changeforgotten
with page title RESET PASSWORD. See screenshot. Does it need to be changed?Contribution checklist (*)