1. DMX can ONLY operate that way. Content cannot be viewed across portals.
2. By default it's Portals/0/DMX, Portals/1/DMX etc. You can specify a string that can include the following placeholders:
- [PortalId] which is replaced by the integer ID of the portal
- [HomeDirectoryPath] which is replaced by the relative path to the home directory of the portal.
Kind regards

Peter,

I downloaded the Administrators and Users Guide and do not see [PortalID] and [HomeDirectoryPath] described. Where can I read about this and other configuration features in DMX ?

If each portal has an Admin account, each Admin can go into the DMX Options and change the settings on the Portal tab. If Admin can change the Repository Location (Default or User defined). This would effect the other portals. Is my comment correct and how would I protect again this potential security issue ?

Nathan,

The [PortalId] etc placeholders were only put in place for a custom project and were never thought to serve anyone else, so they went undocumented. They are now documented here is this thread. The reason the other client wanted this was to roll out a huge amount of portals in an automated fashion and still save the DMX documents somewhere else.

The admin can change the repository location of ONLY his own DMX repository. It does not affect the other portals. Potentially he could put this in the same place as another portal. This does not open up the documents of the other portal, however. All documents are renamed and are only identified through the DB and only retrieved in that way. There is no way he'd be able to see the other documents unless he would have full access to the database (which an admin does not have).

Peter

We tried using the value [PortalId] without any success.  It does not seem to try to create the directory if it doesn't exist.  Even when we created the directories manually, it still reports the same error.  We would like the module to automatically create the directory, so that future instances can be provisioned without having an admin go to the file system.

Thanks,
Roger Lim

Roger,
It is not an official feature and the way it was created it was not intended to operate that way. Note that you have to set permissions correctly to move the repository outside the portal home directory.
The only way to have automatic creation is through Portals/0/DMX, Portals/1/DMX etc.
Kind regards