nextcloud / nextcloud/server

Folders not live syncing in browser

Open
#2,742 9 comments 16 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop enhancement feature: files
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

Steps to reproduce
  1. Open up desktop synced folder
  2. Open up nextcloud server in browser
  3. Upload/change name/delete a file on the synced folder on pc
Expected behaviour

The web interface should live update in an interval like the synced desktop folder

Actual behaviour

The webpage doesn't update until being refreshed, and browsing to a changed filename/foldername then given an expected error because the name is not the same after syncing

Server configuration

Operating system:
Ubuntu 16.04.1 server, running in virtualbox for testing purposes

Web server:
Apache 2.4

Database:
MySQL 5.7

PHP version:
PHP 7

Nextcloud version:
10.0.2 stable

Updated from an older Nextcloud/ownCloud or fresh install:
fresh install

Where did you install Nextcloud from:
Through the snap manager in Ubuntu like so: sudo snap install nextcloud

Signing status:

Signing status
No errors have been found.

List of activated apps:

App list
do not know where to find location in snap install

The content of config/config.php:

Config report
do not know where to find location in snap install

Are you using external storage, if yes which one: local/smb/sftp/...
no

Are you using encryption: yes/no
no

Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
not sure

Client configuration

Browser:
Firefox 50.1.0
Microsoft Edge 38.14393.0.0
Google Chrome 55.0.2883.87

Operating system:
Windows 10

Logs
Browser log
Browser log ``` security log: Content Security Policy: Directive 'frame-src' has been deprecated. Please use directive 'child-src' instead.

logging:
JQMIGRATE: Migrate is installed, version 1.4.0 jquery-migrate.min.js:2:542

javascript log:
window.controllers is deprecated. Do not use it for UA detection. ace.js:1716

</details>

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source file or test is named in the report. Start by reproducing the steps in a browser while changing a desktop-synced file, then trace how the web file listing detects updates; this is done when changes, renames, and deletions appear without a manual refresh and stale paths no longer produce errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, php
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.