You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But I am also running a production evironment whith the actual officially release (ownCloud 8.1.1 (stable)). When I access via devmachine/WebDav my prodmachine/owncloud instance, I get the same error, means that this is also present in stable and not related to my dev instance.
Usually you do not get this error when you do this test with a Windows WebDav client, because it seems that Windows WebDav clients (Windows native, CyberDuck ect) check the directory name to be created against a cached list first so the request does not get passed to the WebDav server and therefore not triggering the error.
The text was updated successfully, but these errors were encountered:
I just have downloaded another Windows WebDav client named CarotDav.
This client does not check if the folder to be created already exists against a local cache entry but sends the request directly to the server. The Fatal Error message also comes up with Windows. This means, that it is proven not to be a issue of Windows/Linux clients.
Steps to reproduce
Expected behaviour
Message from the filemanager: "Target file already exists"
No further error messages in the owncloud log
Actual behaviour
Two Fatal error messages are logged
Server configuration
Operating system: Ubuntu 14.04
Web server: nginx 1.9.4
Database: mysql 5.5.44
PHP version: 5.5.9
ownCloud version: 8.2 pre Alpha git
Updated from an older ownCloud or fresh install: fresh
List of activated apps:
The content of config/config.php:
Are you using external storage, if yes which one: local/smb/
Are you using encryption: no
Are you using an external user-backend, if yes which one: no
Client configuration
Browser: FireFox
Operating system: Ubuntu (same machine)
Logs
ownCloud log (data/owncloud.log)
There are always two error messages coming as pair
Additional Info
The text was updated successfully, but these errors were encountered: