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

[2011-06-10] sync re-creates files in the database #320

Closed
silverstripe-issues opened this issue Apr 3, 2013 · 5 comments
Closed

[2011-06-10] sync re-creates files in the database #320

silverstripe-issues opened this issue Apr 3, 2013 · 5 comments

Comments

@silverstripe-issues
Copy link

silverstripe-issues commented Apr 3, 2013

created by: mmichelli
created at: 2011-06-10
original ticket: http://open.silverstripe.org/ticket/6664


When the "Look for new files" button is pressed, Once in a while, a FOLDER seems to think that it is new, which recursively removes all sub-files from the FILES table and re-creates them in the FILES table. This breaks all galleried that use the Files ID.

For bigger sites this is a huge bug.

http://www.silverstripe.org/dataobjectmanager-module-forum/show/14115?start=8#post290785

@silverstripe-issues
Copy link
Author

comment by: mmichelli
created at: 2011-06-15


I've tried to make all my images use the image class to no avail. This error does not happen when I use a sitetree with a $has_one Image. But does break with DataObject has_one Image.

@silverstripe-issues
Copy link
Author

comment by: mmichelli
created at: 2011-06-24


I've tried making not extending the image class but that does not help. I think it's the DataObject image relation that is not updated, in the same way a SiteTree -> image relation is. If that makes sense.

@silverstripe-issues
Copy link
Author

comment by: mmichelli
created at: 2012-06-25


This is a huge issue. If an image is connected to a data object it disappears when you sync the images with the file system.

@simonwelsh
Copy link
Contributor

If this is still an issue, please create an issue for it on silverstripe-framework.

@andrelohmann
Copy link

Noticed this issue today on a Silverstripe 3.1.5 Installation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants