fileBrowserCallback has problems with existing link if they starting with a protocoll
The fileBrowserCallback function has a small problem with e.g. download or external links if they starting with a protocol (http://, ftp://, ...). The advanced link browser just displays an empty page with a "Access Denied" error if you have opened it with such an existing URL. The solution is simple, because you just need to encode the existing value for the page browser. The attached patch should fix the issue without to produce any headache. ;-)
Updated by Thomas Allmer almost 13 years ago
- Status changed from New to Resolved
- Assignee set to Thomas Allmer
Stefan Galinski wrote:
The attached patch should fix the issue without to produce any headache. ;-)
thx for that although this problem didn't appeared to be, but it can't hurt to do it this way...
although this js is most likely to be replaced in the near future, we will use it until then.