Hi John,
I have got a static site and an externally created JSP site to work in preview. I was also trying to use cifs for modifying the html and other JSP files already checked in via bulk import. Basically trying WCM on an ongoing basis.
Here is how I used CIFS.
- Connected to CIFS using \\servername_a\AVM (basically mapping to a virtual server)
- For a virtual server mapped drive no checkin/checkout is provided as in normal Alfresco cifs
mapping.
- Also once you are mapped in cifs there is no security. Basically having logged as me shows me the staging sites for all other users as well and allows me to change their files.
- Changing the file in Mapped drive:\Myproject\HEAD\DATA\www\avm_webapps\ROOT allows me to change any file.
- Once you save it, you can go to the Alfresco UI in your sandbox and submit the changed file again. When approved by the workflow process it creates ia new version.
- So, once the file is updated and saved and submitted to the workflow, versions/rollbacks do work.
- The issue about using CIFS is security for the virtual server. If there are multiple users I could change the files for those users as well.
When you mean "Use CIFS projection" is it this way or some other way? If it is this way then what does one do about security. Even if it is not this way then, any other user can still use this backend approach and change other users files.
thanks,