mirror of
https://github.com/modoboa/modoboa.git
synced 2026-04-26 01:16:01 +03:00
[GH-ISSUE #1400] Can't Save Parameters #1113
Labels
No labels
bug
bug
dependencies
design
documentation
duplicate
enhancement
enhancement
enhancement
feedback-needed
help-needed
help-needed
installer
invalid
looking-for-sponsors
modoboa-contacts
new-ui
new-ui
pr
pull-request
pyconfr
python
question
security
stale
webmail
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/modoboa-modoboa#1113
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @DarrenCarterSA on GitHub (Feb 19, 2018).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/1400
Impacted versions
Steps to reproduce
Current behavior
The screen refreshes and no parameters are saved, no error or success message displayed on UI. 400 Bad Request on POST https://xxx.example.com/core/parameters/
If you return to the parameters page, all settings are as they were before.
Expected behavior
Display success or failure message on save, changes to reflect when revisiting the parameters page.
Video/Screenshot link (optional)
@w00kie commented on GitHub (Feb 21, 2018):
I had the same issue. I looked at the 400 error response and it said the modoboa_amavis recipient_delimiter was a required field. Mine was empty.
What I did is add the following to my
/etc/amavis/conf.d/50-userfile:And then set the field to
+in the parameters on the web app. Then I could save.@tonioo commented on GitHub (Feb 21, 2018):
@DarrenCarterSA Make sure you're using the latest version of the amavis plugin (1.2.2 now), this issue has been fixed.
@DarrenCarterSA commented on GitHub (Feb 21, 2018):
I have tried the suggestion above and it is still giving me the same issue. I am running the latest version as well.
@tonioo commented on GitHub (Feb 21, 2018):
Have you tried a hard refresh of your browser cache?
@DarrenCarterSA commented on GitHub (Feb 21, 2018):
I have indeed, even tried a web browser I have never used before for the domain.
@tonioo commented on GitHub (Feb 21, 2018):
A 400 error means there is a validation issue in one or more tab (ie. a missing value for a required setting). Have you checked all tabs? (amavis or PDF credentials)
@DarrenCarterSA commented on GitHub (Feb 21, 2018):
I have checked and filled each and every field on each and every tab. Yet still getting the same error.
Is there any way to get better logs? Apart from my browsers debugger, I can't find any other logs on the server regarding the parameter saving issue.
@tonioo commented on GitHub (Feb 21, 2018):
Open your javascript debugger and go to the network tab, then check responses sent by the server.
@DarrenCarterSA commented on GitHub (Feb 22, 2018):
@tonioo That did the trick! My problem was with the default password. I left it as per the default "password" and this is where the form validation was failing. Might be useful to add the password requirements to the "?" tooltip in future.
Thanks everyone for your help on the matter.