Copy link to clipboard
Copied
Hi there,
We have plenty of software restrictions enforced (We are a secondary school),
Unfortunately Dreamweaver's IDE allows users to view the entire folder structure of the local hard disk, Windows explorer method's stop this, this also causes us headaches as students can then right click and create new folders in system writable areas.
Out of all the Adobe products Dreamweaver is the only one to use this built in IDE (the rest are based off windows explorer).
Is there any way to restrict the folder view?
Thanks
The only way I have been able to resolve this is to now hide the drive as well as deny access to the drive in windows explorer, using group policy, denying access (which works correctly in any "File explorer dialog window" wasn't enough to stop Dreamweaver being able to populate the file and folder structure.
Copy link to clipboard
Copied
The problem can easily be solved if you use a flash drive for your site. This needs you to set the site up in Dreamweaver.
Copy link to clipboard
Copied
Thanks for the reply, unfortunately there is nothing stopping them clicking the "Files" tab or "Windows > Files" and navigating through that way.
Copy link to clipboard
Copied
I assume that you are the IT person for the school. How do you stop the students form doing the same in Explorer?
Copy link to clipboard
Copied
We use group policies and software path restrictions to stop them navigating through explorer, which works correctly.
The dreamweaver IDE still allows students to navigate through the drive structure, which in turn allows to read files and folders they wouldn't generally get access to.
They can then write folders and files in system writable folders eg c:\users\public or c:\windows\temp.
All other Adobe products use file explore based dialog boxes which are then protected by group policies and path restrictions.
Copy link to clipboard
Copied
The only way I have been able to resolve this is to now hide the drive as well as deny access to the drive in windows explorer, using group policy, denying access (which works correctly in any "File explorer dialog window" wasn't enough to stop Dreamweaver being able to populate the file and folder structure.