Skip to content

Conversation

@robinsowell
Copy link
Contributor

@robinsowell robinsowell commented Apr 30, 2025

Also, additional developer logging. Docs ExpressionEngine/ExpressionEngine-User-Guide#1021

Proposed hooks:
member_auth_send_reset_token_start
cp_login_send_reset_token_start
email_from_address
email_to_address

Finalized hooks:
member_auth_send_reset_token_start
cp_member_send_reset_token_start
email_from_address
email_to_address

Also, additional developer logging.
@robinsowell robinsowell added this to the 7.5.13 milestone May 15, 2025
@robinsowell robinsowell marked this pull request as ready for review June 3, 2025 20:52
Copy link
Contributor Author

@robinsowell robinsowell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm leaning strongly toward removing the logging. I tend to think it should be in the extension rather than the core.

Also some concerns about how much this could fill up logs if they're sending emails to member groups and such.

@robinsowell robinsowell modified the milestones: 7.5.13, 7.5.x Jun 13, 2025
@TomJaeger TomJaeger modified the milestones: 7.5.x, 7.5.14 Jun 13, 2025
robinsowell added a commit to ExpressionEngine/ExpressionEngine-User-Guide that referenced this pull request Aug 4, 2025
Documenting new hooks related to email address overrides. ExpressionEngine/ExpressionEngine#4805
Get it consistent with the other hooks in that file
{
// email_from_address allows overriding the from address
if (ee()->extensions->active_hook('email_from_address')) {
$from = ee()->extensions->call('email_from_address', $from, $name);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since we pass $name, do we want the ability to set it as well?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see no reason not to. I'm also not 100% sure why we pass it there, but giving them the extra flexibility seems reasonable. I'll make it so.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, my concern was that if they end up changing the email and the name, but then the name is the original name, and the email is the new email, it might send like that.

@TomJaeger TomJaeger modified the milestones: 7.5.14, 7.5.15 Aug 6, 2025
@robinsowell
Copy link
Contributor Author

@matthewjohns0n this one is ready for final (hopefully) review.

The main changes that are worth a look/thought are - in email library, what do we want to default to if the extension doesn't set something. And- do we want to do end_script on all of the new hooks. I actually thought end_script was uniform across all hooks. As in- if it's a hook, there's an end_script. This does not look to be the case so, I figure it's worth an eyeball.

Once approved, I'll tweak docs to match the final product.

@TomJaeger TomJaeger merged commit 5e28919 into 7.dev Aug 20, 2025
23 of 24 checks passed
@TomJaeger TomJaeger deleted the feature/hooks-email-forgotten-pass branch August 20, 2025 13:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants