Although they appear to be available for inclusion in the system file path field, node tokens aren't populating. Even the node:title doesn't populate but appear in the directory as [node:title]/
So far, I've tried:
1. Using the [node:field_?] tokens (they don't populate as described above)
2. Hard coding a system file path "default" in filebrowser.module using the [node:feed-node:field_?] values, and then populating the field_? values through a node feed, but the [node:feed-node:field_?] tokens don't populate either.
3. Using the [node:original:field_?] tokens (with the intent of running a Rule upon directory creation to reopen the directory, change a checkbox value, and then re-save it ... just to get the token to populate), but the [node:original:field_?] tokens don't populate either.
4. I've looked for other specific attempts to work around this using Feeds, Rules, Filefield tokens, and so on, but no one has integrated any of these options.
5. I've looked at using File (Field) Paths, which would work perfectly, but for the fact that the "files" are not exposed as actual fields in filebrowser, so there's no file path data for File (Field) Paths to latch on to.
Without working [node:field_?] tokens, no feeds integration, and no rules integration, there's no real way to batch create directories with filebrowser which, in turn, would seem to indicate that there's no way of migrating anything to it.
If you could provide some guidance on a workaround for this, I'd really love to use filebrowser for my project and I would wrap any configurations into an add-on module (i.e. a gui for globally changing the default options on list/icon, columns, etc ... which would make it easier to use with feeds).
Thanks, and thanks for the great module, it seems to be a MUCH more straightforward and MUCH more lightweight than IMCE and Media, especially for a small office DMS where you don't need to have all of these documents actually stored in the database.
Closed: won't fix
4.0
Directory Listing Pages
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.