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
Admin->Advanced Settings-> Notification settings doesn't save / validate data #19
Comments
Yes is totally true, At the moment this part of code is missing. May require a little analysis anyway, because:
The best solution, is separate the notification settings from the node API. Instead of "Advanced Settings" in the Client would be "Mail configuration", and contains the same fields + the mail template. |
This feature prevent blocking of a major part of the workflow that are the notification, let's consider also the quickest approach to make the email notification testing possibile (so the feature working). |
completed with the notification API refactor |
re-opening because saving of fields doesn't work giving internal server error on dev.globaleaks.org. That's the stacktrace: 2013-03-01 08:18:07+0000 [-] [Failure instance: Traceback: <type 'exceptions.ValueError'>: invalid literal for int() with base 10: 'x' |
this thing is working fine since some days... and is unitTested |
The admin interface for the notification settings does not save and does not valdate the data provided as input.
After saving, the data are not shown in the web interface (empty fields) even after a reload.
Additionally it does not do client validation on the following fields format:
SMTP server address
SMTP server port
Username
Password
Transport Security
The text was updated successfully, but these errors were encountered: