Synchronize File System is broken (again) - You are ignoring the root folder

Description

Synchronize File System is broken (again) - You are ignoring the root folder of any not-local provider. E.g. Amazon, etc.
You've changed this, it was not used to be like this on previous DNN versions.

Let's say (very common!) I already have folders in my S3 bucket. Until now (previous DNN versions), once the mapping to the bucket is created, a 'Synchronize File System' operation added (as expected) the remote folders and files into the DNN Folders tree. Now nothing happens. It just work for subfolders, which means you have to manually create each folder (and with the same case) in the DNN file manager for the could folder to be synchronized.

Please let me know as soon as possible if this will ever be fixed or not. Maybe this was intended, and now it is the way it is and will be. I'm not asking for an 'ASAP fix'. I'm just asking for feedback . I need to know to adjust things that depends on this.

I've been asking for feedback in other issues since many months ago and go no reply. I hope you'll be kind enough to at least reply to this one.

Thanks.

QA Test Plan

None

Assignee

Unassigned

Reporter

Horacio Judeikin

Story Size

None

Severity

Major

Triage

New

Reported in Build #

None

Fixed in Build

None

Dev Owner

None

Includes Code Fix

No

Documentation Required

None

Trouble Ticket

None

Requires More Info

None

QA Story Points

None

QA Owner

None

Injected

None

Automation Required

None

Code Review Owner

None

Components

Affects versions

Priority

High
Configure