-
-
Notifications
You must be signed in to change notification settings - Fork 172
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
PATCH Method returned Bad request 400 error #998
Comments
Mmh. Could you find out the error message that the endpoint returns? (By debugging floccus) Firefox
Chrome
|
Okay. Here it is: {"status":"error","data":"invalid children order: To many children"} And here are the parameter: |
This is probably fixed with v3.0.4 of the bookmarks app. |
No, the problem still exists... Just tested with 3.0.4... Now I get 2 PATCH 400 Bad requests at the end of the sync with the same "invalid children order: to many children" error... |
Indeed, this appears to be a problem with floccus.
The data sent to the server shows the same folder twice. I will look into this. |
Perhaps, it's not, though. Does this still happen with the latest bookmarks app version? |
Hi Marcel, with current version it works. But in the meantime I checked that all bookmarks were transferred to the server and synchronized correctly within another Firefox installation on another computer. After that I deleted all entries on the Firefox installation where this error occurred and re-synchronized it again. After this step it worked fine! Regards, |
Describe the bug
After upgrading to 3.0.0 until 3.0.3 I get a PATCH method error 400 "Bad request" at the end of the sync.
To Reproduce
Expected behavior
Syncronization ends without an error
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Server (please complete the following information):
20200202.52+debian91.gbpa71879$ sudo -u www-data php occ app:list
in your command line]sudo -u www-data php occ config:list system
]Additional context
Add any other context about the problem here.
Web server error log
Nextcloud log (nextcloud/data/nextcloud.log)
Browser log
The text was updated successfully, but these errors were encountered: