Separate directory for development and content contribution

shahzamaj

I want to make datacapture.cfg in data-type folder not modifiable in a dir called "user" i.e. only content contribution and DCR generation can be done in "user" dir.
Secondly I want to block a form to open in dir called "dev" i.e. only development can be done in this dir and no content contribution activities allowed

How can I control this kind of access ? Do I need two datacapture.cfg ? Or can I do it with only one datacapture.cfg ? Please give me some inputs.

Thanks

Adam Stoller

I want to make datacapture.cfg in data-type folder not modifiable in a dir called "user" i.e. only content contribution and DCR generation can be done in "user" dir. Secondly I want to block a form to open in dir called "dev" i.e. only development can be done in this dir and no content contribution activities allowed How can I control this kind of access ? Do I need two datacapture.cfg ? Or can I do it with only one datacapture.cfg ? Please give me some inputs. Thanks

Using the submit.cfg file you should be able to control the access rights on the DCT such that content contributors can read but not modify the DCT - which should take care of your first item. The second items is basically the same thing except that you would have to control who can create content using the DCT via the templating.cfg file -- but I think that's a big mistake as your developers need to be able to create content in order to fully test the DCT code (including but not limited to: DCT, FormAPI, inline scripts, callServer scripts, callout scripts) - and the way one normally handles this kind of process is by having two (or three [or more?]) servers - i.e. a DEV TS server and a PROD TS server - where the developers would have complete access on the DEV server but the content contributors would only have access (and just read-access to the DCT) on the PROD TS server.