Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use forum.silverstripe.org for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

General Questions /

General questions about getting started with SilverStripe that don't fit in any of the categories above.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

Manual Upload to SS4 File and Image Library. Is there a legacy setting?


Go to End


3 Posts   675 Views

Avatar
tazzydemon

Community Member, 135 Posts

31 July 2017 at 1:49pm

Edited: 01/08/2017 9:48am

I have asked this question before and I'm sure someone posted that there was a legacy behaviour setting - if so I cannot find it.

Is there anyway up uploaded an existing folder/file structure into ss4 and have it parse it for inclusion into the file library (even if it means moving things out of folder roots?

Without this feature, the new abstracted system (I personally hate this abstraction filesystem) I regard as a major inconvenience. SS2 and 3 have always had the command admin/assets/doSync to do just this.

Personally I would rather see the file in use positioned just where it should be and the versioned ones abstracted.

Is there any way to turn this off? Is there anyway to import the filesystem contents?

The config.yml setting

File
migrate_legacy_file: true

does not accomplish this but merely imports the existing ss3 file tables as far as I can see.

Avatar
johncena123

Community Member, 2 Posts

2 August 2017 at 3:48pm

I Like it

Avatar
tazzydemon

Community Member, 135 Posts

2 August 2017 at 4:23pm

It is entirely with anybody's right to like it, but I don't.

It's not the versioning that's bad, it's the fact that the primary published version is abstracted and new files cannot be bulk uploaded and absorbed as part of the filesystem - as has been possible for the entire history of Silverstripe so far. For me that's a showstopper and will at the very least keep me on 3.x for the future. Perhaps even move.