New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can not use the windows shares after the update to Detritus #1302
Comments
Here additional slashes are trimmed: 83b7e38, since November 2014 Since 2005 the three slashes where already there: Why has it work fine for so long time, but is it recently that people observe this behavior? btw, What is the syntax that you used in the wiki text? |
Three slashes should be correct. The first two are the protocol divider. The third is the root directory. |
The syntax is very simple: [[\server\data\ict\sheet.xlsx|Here is the sheet]. And it has worked for years. After the upgrade to Detritus it does not work. IE reports that the page can not found and the link in the address space is: If I manual adjust the url to file://server/data/ict/sheet.xlsx then it works. Should it matter if my PHP version is 5.3.4? It should be supported, I mean. |
Windows shares haven't worked for me since a while as well. Will try to figure out if it does work for me before that change. |
According to this two slashes is correct, http://blogs.msdn.com/b/ie/archive/2006/12/06/file-uris-in-windows.aspx |
We have the exact same issue, after updating to Detritus none of our windows share links work. Removing one of the slashes from the file part of the URL fixes the problem. How can I fix this? edit: I figured it out. Followed the link to issue 1304 and then found where xhtml.php was edited to add two slashes to the file url on line 1037. |
Fixed by #1309 |
My existing links to files via Windows shares in dokuwiki don't work after the update to Detritus. I have found that the code put too much slash by:
file:///server/test.xlsx
And that must be only two slashs such as file://server/test.xlsx.
Can somebody fix it? :-)
The text was updated successfully, but these errors were encountered: