The main reason to use the hook is in case another plugin or yourself try to reinstall the emails. If one does that, that email you showed creating will be deleted and you will have to recreate it by hand again. That doesn’t seem to be desireable.
Also, creating via the hook, you can use the correct name when sending the email. You say you read it but your last question implies you don’t know how you are doing and seems to be trying a try and catch attempt. Meaning, trying something and seeing if it works.
I’d recommend doing in the BuddyPress way, the correct way, to avoid problems in the future when upgrading BuddyPress or reinstalling emails.
Hi! Hard to say only looking from the outsite. To really confirm what happned requires looking at the code and database. So, I guess you won’t get valuable feedback here.
I’d recommend asking your developer to check the code. See if something changed, a plugin or custom code. Because with the provided information, it is unlikely someone will do more than guess.
I agree it is not that easy to add a new situation or a custom email. That requires custom code and a bit of knowledge of BuddyPress internals. Also that’s not documented anywhere. This is just not an area that a lot of devs look for.
About the email not being sent. It is important the new template has the proper name. single-bp-email-{custom-name}, if you are creating a custom e-mail, that’s how your new email template should be named for.
I’d confirm if your fields validation is front-end or back-end. Also, check the pages that are open to registration and the BP REST API, if any plugin is opening up for signups.
I think this is more of a preference than a requimenent. One could think that if the user is already logged in, he already has the necessary permissions to delete it, so why ask the password another time.
Social medias sites like Facebook and similars, ask that to make it harder for a user to delete their own account.
So I don’t think this is a BuddyPress core issue. You can certainly add another field requiring the password on your social site before deleting the account.
I’d recommend you to confirm if something is disabling that. Maybe the emails are not set up correctly or a theme or plugin is avoiding that to happen. Could be anything.
basically, your developer is requesting information so that the app can authenticate with the BuddyPress site. Due to the fact users are authenticated, the app needs permission to authenticate using those keys you mentioned.
To make that happen you would need to have a token or oAuth plugin setup on your buddypress site. After that, create those API keys and provide to her.
Just be aware that whatever choice you make, there will be a learning curve.
Also, I’d recommend checking how the API will affect the intranet nature of your site. For example, if you intranet is private (the front-end of the site), current BuddyPress API is open. Meaning, some information is open to the public (not logged in information, of course).
Just something to keep in mind. Hope this answer your question, or at least, provides you with next steps (install the plugin and pass the keys information to her).
Even with the BuddyPress CLI, this isn’t feasible. The best option I can think of is you creating a custom command or script to iterate the users and add and accept each other’s friendship requests.
