From 79ffede4a7224a26e1725296db2db1918d52667c Mon Sep 17 00:00:00 2001 From: jhagg Date: Thu, 17 Jun 2010 08:30:38 +0000 Subject: [PATCH] --- ...tachment_upload_does_not_work_for_windows_clients.mdwn | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/doc/bugs/attachment_upload_does_not_work_for_windows_clients.mdwn b/doc/bugs/attachment_upload_does_not_work_for_windows_clients.mdwn index ad3aadbce..4e8c7bdcf 100644 --- a/doc/bugs/attachment_upload_does_not_work_for_windows_clients.mdwn +++ b/doc/bugs/attachment_upload_does_not_work_for_windows_clients.mdwn @@ -11,6 +11,14 @@ whole path a filename. > Still, I don't mind adding a special case, though obviously not in > `basename`. [[done]] --[[Joey]] +>> Well, it's probably something else also, I get **bad attachment filename**. +>> Now, that could really be a bad filename, problem is that it wasn't. I even +>> tried applying the **wiki_file_prune_regexps** one by one to see what was +>> causing it. No problem there. The strange thing is that the error shows up +>> when using firefox on windows too. But the backslash hack fixes at least the +>> incorrect filename from IE (firefox on windows gave me the correct filename. +>> I'll do some more digging... :-) /jh + This little hack fixed the backslash problem, although I wonder if that really is the problem? (Everything works perfectly from linux clients of course. :-) -- 2.26.2