I’m not sure if this is a bug or not. I have various contexts that each represent a sub-domain. I’m using the One Gateway plugin approach for routing sub-domains to contexts. I want the file manager to point to a different start directory for each context. In implementing this, I ran into some issues.
It seems like the file manager is tied to the web context. I don’t want subdomain managers to have access to the main web context, but whenever I remove access to the web context I can’t get the file manager tab to appear
After creating file manager access in the web context for subdomain users (removed permissions for everything else) I overrode the relevant settings in each subdomain context for the file manager:
[list]
[li]filemanager_path- rb_base_dir
- filemanager_url
- rb_base_url
This works, but there is a minor bug. When the user first logs in, the "Files" tab doesn’t show up. It will show up as soon as a resource is clicked. I’m guessing that clicking the resource activates the context and then the permissions become available. It seems to me that this should happen automatically.
[/li]
[/list]
Does this sound like a bug, or is this the way it should work? If not a bug, any ideas on how to write a plugin to make the file tab appear automatically?
God does not save those who are only imaginary sinners. Be a sinner, and let your sins be strong, but let your trust in Christ be stronger, and rejoice in Christ who is the victor over sin, death, and the world.
It sounds like a bug to me.
