-
Notifications
You must be signed in to change notification settings - Fork 13
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
Be sure to add /admin to your email confirmation url or update your emails in netlify #8
Comments
Really nice of you to write up such a detailed and helpful issue! So apparently if I understood this correctly, this is caused because Netlify redirects to the root domain from the emails, where it expects to find This is something I removed from the main templates and only added to the But if your implementation requires some more authentication support, I'd suggest following @audetcameron's advice above or @tomrutgers advice here: I wont be adding the package to the other pages' Thank you so much for your contribution @audetcameron ! ⭐ |
You might want to consider adding the email templates to the repo along with some instructions on how to install them though, but that's just my two cents 🙃 |
@Knogobert if you need an screeshot on where to add/update your email template files in netlify |
@tomrutgers @audetcameron , Thanks for your input! I was a bit distracted by other work to do this properly. I have now updated the readme to be more extensive and also added |
Currently, if you just deploy directly to netlify you get the email but it directs you to the index page , where it needs to be /admin?and your query
Should this repo add the netlify widget source to index?
See my comment here
https://answers.netlify.com/t/cms-nuxt-template-starter/37634
I ended up creating new email templates in the back end of netlify , identity ->emails. per the user @tomrutgers
suggestions.
I added these to the /static/emails
and then referenced them in netlify.
confirmation.html
recovery.html
invitation.html
email-change.html
The text was updated successfully, but these errors were encountered: