-
Notifications
You must be signed in to change notification settings - Fork 154
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
Tp1 1760 wagtail permissions update #13523
base: main
Are you sure you want to change the base?
Conversation
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.
Hey @dlopezvsr,
I'm receiving a 500 error upon article creation. Is this because we don't have the gmail credentials yet?
SMTPAuthenticationError at /cms/pages/add/wagtailpages/articlepage/3/
(535, b'5.7.8 Username and Password not accepted. For more information, go to\n5.7.8 https://support.google.com/mail/?p=BadCredentials d75a77b69052e-474691a1f78sm1494131cf.14 - gsmtp')
That's correct @robdivincenzo, as we are still waiting for email access to create the Password App that will allow us to send the emails, for now the environment variables have generic values that are invalid for |
Description
This PR introduces the setup on
settings.py
to allow Wagtail to send email notifications when user requires publishing approval from admins or Strat Comms. To achive this, we will require mostly manual changes on Wagtail CMS, but also it was needed to introduced the corresponding env variables for email service backend such asWAGTAILADMIN_NOTIFICATION_FROM_EMAIL
.Code changes:
WAGTAILADMIN_NOTIFICATION_FROM_EMAIL
andEMAIL_BACKEND
Manual changes required:
Link to sample test page: https://foundation-s-tp1-1760-w-sg1smu.herokuapp.com/en/
Related PRs/issues: https://mozilla-hub.atlassian.net/browse/TP1-1760
Test steps
┆Issue is synchronized with this Jira Story