I have several subdomains, organized in contexts. When I use a TV with a @DIRECTORY binding, I only get the files inside my MODX tree and not of the one, where the context files are stored. To make things clearer, here is my path structure:
/cms (MODX)
/assets
/connectors
/core
/manager
...
/sub1 (subdomain1)
/assets (Assets of subdomain 1)
config.core.php
index.php
/sub2 (subdomain2)
/assets (Assets of subdomain 2)
config.core.php
index.php
...
That should (hopefully) make my problem clear: Editing a resource in the context "sub2" (same name as the directory), having a template variable with "@DIRECTORY /assets", does not list "/sub2/assets/, it lists "/cms/assets". That’s bad because I cannot use "@DIRECTORY /../sub1/assets" for a binding because this would make the TV only usefull for the "sub1" context.
In the context settings for sub1, sub2, etc. I used (without success):
assets_path, assets_url, filemanager_path, filemanager_url and, of course,
site_url, base_url, http_host. Anything left to set here? Must these settings also be set in the "system setting" to work in a context? Or is the context setting enough? I once had a case, where a context setting was ignored because there was no system setting set (what a "set"-crowded sentence ;-).
I already files a bug report (
http://bugs.modx.com/issues/4660) but I also want to use the forum-power in case I just missed something.
THANKS A LOT IN ADVANCE!
Oliver
☆ A M B ☆
MODX Staff