default dokuwiki install - media uploads do not link to files

Hi there,

when I do a fresh install of dokuwiki (latest version),

upload a file

the I get a broken link to the file (see screenshot). It's naturally also not showing when embedded into any wiki page.

I suppose it has something to do with the rewriting rules, but since I have no clue about the topic I'm not really getting anywhere right now.

Can someone point me into a direction where to look for the problem?

Thanks in advance

Replies (6)

Hmm, I thought it may have been a hostname issue

Reply 1 2016-11-17

But assuming when you say http://host/_media/xxx.png that "host" = "your real FQDN or IP address" then that's obviously not the issue and it must be something deeper.

My guess is that it's either a bug in the Debian DokuWiki package (which seems somewhat unlikely, but possible) or our default config is flawed.

I couldn't see an issue on the tracker so I created one so it doesn't slip through the cracks.

Unfortunately I'm going to have to come back to this when I have some more time so I'm not much help to you right now. But thank you tons for reporting this. In the meantime, if you manage to resolve it, please let us know. Assuming that we can reproduce the bug, we can develop a manual workaround for it for now. And include a proper fix for v14.2.

Hi Jeremy,

Reply 2 2016-11-17

the URL is http://host/_media/xxx.png which seems consistent to the rewriting rule

RewriteRule ^_media/(.*)              lib/exe/fetch.php?media=$1  [QSA,L]

I will post the bug report on github.

Thank you

Hey Max

Reply 3 2016-11-17

Unfortunately I'm not particularly familiar with the specifics of DokuWiki so can't specifically answer your question.

Out of interest, where is DokuWiki looking for the file? You should be able to right click on the broken image and open it in a tab. It will no doubt fail and give you an error but the address bar should give you the url. Or probably even just getting the url from the text link.

That will hopefully give us a hint on what might be going wrong.

Also it's probably worth posting an issue on our tracker as it appears to be a bug.

Hey Max - Are you still about?

Reply 4 2017-01-16

Apologies on such a delay but we finally got a chance to look into this and confirmed the bug. After much more research and tweaking than initially expected, we discovered the fix.

Thank you so much on reporting it. We won't be fixing this in the appliance just yet. But as we are currently working on the v14.2 release, hopefully the new fixed version won't be too far away. In the meantime you can apply the workaround on your existing server if you'd like.

Please let me know if you need a hand implementing it.

No problem Max

Reply 5 2017-01-17

I completely understand. Regardless, the next release will include the fix. In the meantime if you (or anyone else) do want some insight on how to apply the fix to an existing server, please let me know.

Hi Jeremy,

Reply 6 2017-01-17

thanks for looking into the issue. In the meantime I helped myself with a vanilla debian installation and will stay with it for the time being. But thanks for the support anyway.