Staff are wishing for non-LDAP/CMS linked staff to access files on a local shared network, and using the website/website pdf's behind a login as a portal to those documents.
I understand as a general rule this is frowned upon, and I agree. <_< However it possible in the CMS in some way?
Using the method of adding "file:///" at the beginning, with spaces filled with “%20” in the filenames, can work in IE.
PDF results:
CMS renders PDF local link with the added domain the PDFresides in every time: http://www.domain.com.au/fsww01.localdrive.xx.com.au/shared/documents/
Staff are wishing for non-LDAP/CMS linked staff to access files on a local shared network, and using the website/website pdf's behind a login as a portal to those documents.
I understand as a general rule this is frowned upon, and I agree. <_< However it possible in the CMS in some way?
Using the method of adding "file:///" at the beginning, with spaces filled with “%20” in the filenames, can work in IE.
PDF results:
CMS renders PDF local link with the added domain the PDFresides in every time: http://www.domain.com.au/fsww01.localdrive.xx.com.au/shared/documents/
Well the PDF based links are created internal to Microsoft Word before converstion to PDF using the Hyperlink, as the client would do, with and without the "file:///" added to the front.
And the html links are both hardcoded in the code view:
<a href="file:///\\fsww01.domain.com.au/shared/documents/" target="_blank">link to Thedrive</a>
And then tested adding "file:///" to the selected text link, using the WYSIWYG link tool. Kept a blank protocol drop down within that linking screen so none overrode.
We are linking to another application - the link goes to the application but can no longer brings up the individual entry - we have 68 catalogue entries that require this style of url webpath.
YEAH
I've just converted my window to RAW html - the links are staying with back slashes - but this is not ideal as our editors will not be able to the EES or SEI editors.
I've just converted my window to RAW html - the links are staying with back slashes - but this is not ideal as our editors will not be able to the EES or SEI editors.
Will there be a fix for the WYSIWYG editor?
I don't know of any fixes. Those slashes are Microsoft style slashes and are not standard for the web, so I am assuming that is why the WYSIWYG editor converts them because those don't work in website URLs.