Closed (won't fix)
Project:
IMCE
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
16 Jul 2008 at 17:32 UTC
Updated:
17 Jun 2020 at 20:52 UTC
Jump to comment: Most recent
Comments
Comment #1
Renee S commentedI'd love something similar by content type.
Comment #2
nirvanajyothi commentedcan this be done...anyone pls reply
Comment #3
Taxoman commented+1
This would be a very useful feature.
Comment #4
Taxoman commentedSetting this as a feature request instead of a support request.
Comment #5
ufku commentedClosing 6.x-1.x issues as this branch is no more supported.
Comment #6
Taxoman commentedWhat about this functionality for D7?
Comment #7
ufku commentedIMCE usually is not aware of the context that is being used. Custom usage of IMCE is up to the application that calls IMCE as a file browser. File field sources is an example.
This feature doesn't seem to belong to IMCE core.
Comment #8
ufku commentedComment #9
jaypark commenteddon't see how you can say this should stay out of core...
both directories and taxonomies with a simple 1child->1parent hierarchy are both trees.
one primary failure of drupal to become an enterprise level cms is its lack of a robust, integrated, core document management feature. many large organizations have - surprise! surprise! - an organizational hierarchy, that can be supported with a file structure and generalized data structure (imce, taxonomy, respectively).
1. use core taxonomy hooks to sync selected hierarchical vocabulary terms and properties with imce directories.
2. integrate with tac or tac-lite for access control.
3. bring drupal out of the stone age of document management.
this is a work in progress, but i can't share the code (not my decision).
Comment #10
thallesI think this feature will not be implemented