Skip to content
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

FTP external storage doesn't get the updates made in the backend #16407

Closed
jvillafanez opened this issue May 18, 2015 · 13 comments
Closed

FTP external storage doesn't get the updates made in the backend #16407

jvillafanez opened this issue May 18, 2015 · 13 comments

Comments

@jvillafanez
Copy link
Member

jvillafanez commented May 18, 2015

Steps to reproduce

  1. Configure a FTP external storage
  2. Upload a file directly in the backend

Expected behaviour

The file should appear in ownCloud, in the configured mount point

Actual behaviour

File is missing in the configured mount

Server configuration

Operating system: ubuntu 14.04

Web server: apache 2.4.7

Database: mysql

PHP version: 5.5.9

ownCloud version: OC 8.1 beta 1

Updated from an older ownCloud or fresh install: fresh install

List of activated apps:

  • encryption: 1.0.0
  • files: 1.1.9
  • files_external: 0.2.3
  • files_locking:
  • files_sharing: 0.6.1
  • files_trashbin: 0.6.2
  • files_versions: 1.0.5
  • user_ldap: 0.6.0
@ghost
Copy link

ghost commented May 18, 2015

Hi,

very likely related to #5036 where some workarounds like using a cronjob to rescan the external storage where posted.

Edit
Another ref to a duplicate reported issue: #11797

@jvillafanez
Copy link
Member Author

I don't think is related to #5036 because that issue affects all external storages (or at least it did). This issue affects only to FTP storage. Other storages get the new file correctly after reloading the page in the web, but not FTP

@ghost
Copy link

ghost commented May 18, 2015

But #11797 says:

None of Amazon/Ceph s3 #11652, Swift #8633, ftp #5655, ftps/proftpd #9630, smb on FAT correctly propagates mtime changes up the directory tree, so our hasUpdated() fails and we have yet to implement backend specific implementations that work.

@PVince81
Copy link
Contributor

It might also depend on the FTP server. Some might deliver proper mtimes (in a format that the FTP stream wrapper from PHP is able to read) which makes it possible to detect updates. Some others might not.

@DeepDiver1975
Copy link
Member

Known issue no some external storages - we need to address this in 8.2. nothing we can do in the livecycle of 8.1

@DeepDiver1975 DeepDiver1975 modified the milestones: 8.2-next, 8.1-current May 21, 2015
@PVince81
Copy link
Contributor

General ticket: sort out external storage update issues: #11797

@PVince81
Copy link
Contributor

@DeepDiver1975 move to 9.0 ?

@DeepDiver1975
Copy link
Member

@DeepDiver1975 move to 9.0 ?

yes from my pov @cmonteroluque objections?

@ghost
Copy link

ghost commented Oct 5, 2015

@DeepDiver1975 @PVince81 Yeah, part of the overall issue with external shares. Tough to accept but no choice at all.

@PVince81
Copy link
Contributor

@DeepDiver1975 @icewind1991 what about the flysystem FTP implementation ? Didn't we want to replace the existing one with this new one ? Would be good to find out whether it fixes the mtime based change detection problem.

@ghost ghost modified the milestones: 9.1-next, 9.0-current Feb 23, 2016
@ghost ghost assigned icewind1991 Feb 23, 2016
@PVince81
Copy link
Contributor

Moving to 9.2

@PVince81
Copy link
Contributor

Please try again with the "files_external_ftp" app which is based on flysystem.

@PVince81 PVince81 closed this as completed Apr 6, 2017
@lock
Copy link

lock bot commented Aug 2, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants