Migration Plugin

[Luke 37100]

2 hours ago, ulrick65 said:

@LukeI am not sure if there are any plans to change this behavior, but it would be good to know about it in advance before it is changed.  Currently, everything works fine as long as the path points to the parent (metadata) folder and a "people" folder is located within it as @pünktchendiscovered above.

Just wondering...no problem as it stands now at all.

Thanks.

The reason why you get the extra layer underneath is because prior to us adding that, we were constantly troubleshooting situations where users configured the same folder for lots of things, e.g. cache, metadata, transcoding-temp, etc, and then the server going haywire due to lots of different things stepping on each others toes. So that became one way to never let users get caught into that situation again.

[pünktchen 1259]

1 hour ago, Luke said:

The reason why you get the extra layer underneath is because prior to us adding that, we were constantly troubleshooting situations where users configured the same folder for lots of things, e.g. cache, metadata, transcoding-temp, etc, and then the server going haywire due to lots of different things stepping on each others toes. So that became one way to never let users get caught into that situation again.

Understandable, but then when a user enters/picks a custom path you should append "metadata", "cache" or "transcoding-temp" to that path in the GUI, so the user sees/understands what is happening.

[Luke 37100]

On 7/23/2023 at 4:36 PM, pünktchen said:

Understandable, but then when a user enters/picks a custom path you should append "metadata", "cache" or "transcoding-temp" to that path in the GUI, so the user sees/understands what is happening.

Hi, yes this would be a good idea. Thanks.