external links to file paths don't work

links in the form file:// as external links in the documents module don't work, the validation tries to prevent file:// links, but even if that is fixed as the links open through a javascript based process the file links are blocked by the browser sandboxing of javascript. Clearly external file links are only going to work when the path can be resolved, so probably on a LAN, but this is a customer requirement from time to time.

@alanbell we will check and get back to you.

@alanbell As the documents stored on a local file server, can be uploaded to the CRM through the Download Type as Internal. Download Type as External is to provide an URL of your external file location from where the file can be downloaded. We need to restrict the internal file location's during the URL validation. We will upload a patch for this validation.

yeah, they could put them in vtiger as internal attachments, but they really want to link to them on a file server, so that when they click on the document associated with a customer the current editable file on the server opens up, where they can edit it and save it.

Yes I agree with you, In case of multi users this wont work, The documents stored on a local file server which is created by one user cant be accesable by the other users. Google docs is the best option to keep on the record update.

it would work fine for multiple users! They access the same files on the same network share that they can all access from within the LAN.

looks like browsers don't really do this any more, there are some extensions to allow it in specific browsers, but it probably isn't a good idea. Editing the regex on line 179 of modules/Vtiger/resources/validator/FieldValidator.js to something like var regexp = /(^|\s)(((https?:|file:\/*)\/\/)?[\w-]+(\.?[\w-]+)+\.?(:\d+)?(\/\S*)?)/gi; does allow you to put in a file: link, which works if you install the chrome locallinks extension or firefox equivalent https://chrome.google.com/webstore/detail/locallinks/jllpkdkcdjndhggodimiphkghogcpida

however I kind of agree that this is too broken to support by default.

Status changed to closed

Milestone changed to 6.5.0