-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
can't delete directory #1965
Comments
Is it possible to see the script which created the broken directory? |
only fix for me: |
Can you please provide the information, how you wrote your entry into the database? |
i guess this was happening: #!/bin/bash |
and then files:scan or how did you populate the file to Nextcloud? |
created on datadir/nextclouduser/files/somewhere direct on the server . Then i do "nothing"... you can then see it in the browser and the sync-client tries to sync the "malnamed" folder and die |
Steps to reproduce
i have a script which transforms an project into static html. There was an failure in the script and it created a folder with an "\n" in the middle.
So the link would be something like:
https://nextcloud.td/index.php/apps/files?dir=/xxx%0Ayyy
The Nextcloud-Server 10.0.1 shows the path, but you can not rename or delete the folder.
Most problematic thing at all is that the behaviour of the client (testet on Windows 2.2.4 breaks the sync completely.
Expected behaviour
First: you should always rename or delete a folder or file.
Second: The sync should display the problem, but so sync all the rest.
Actual behaviour
Can't delete or rename the folder in the frontend.
Can delete the folder in user/files/ but the server don't remove the entries.
Sync-Client breaks.
Server configuration
Operating system:
Linux
Web server:
apache
Database:
mysql 5.5
PHP version:
php 5.5
Nextcloud version: (see Nextcloud admin page)
10.0.1
Updated from an older Nextcloud/ownCloud or fresh install:
fresh installation on a hosting server
No errors have been found.
The content of config/config.php:
Config report
Insert your Nextcloud log here
The text was updated successfully, but these errors were encountered: