Altough I understand that the module does not function properly in non clearn url mode, there are some things that can be done to make it work a bit better.
The url's for images generated in the webdav_listing.tpl.php are wrong for instance. If they are prefixed by '$GLOBALS['base_url']. "/". ' they link correctly to the module images in both clean and non clean url mode.
Example
<img
src="<?php print $GLOBALS['base_url']. "/". drupal_get_path('module', 'webdav')."/images/up.png"; ?>" /></td>
The same holds for the mime type images inside the template.
My guess is that the same holds for the files as well.
Comments
Comment #1
wvd_vegt commentedHi,
My observation seems correct. If the template is changed a bit more the file system module works in both clean and non clean url mode.
Change (around line 70):
into:
and files can be access properly too. Navigating into the webdav's folders also works, navigating up still fails.
Last problem to solve is the up link.
Comment #2
wvd_vegt commentedHi,
If up code link is changed in webdav_listing.tpl.php like below, it nicely works in both url modes.
Note, this only holds for the browser visible inside drupal!
I just tested webdav access though windows network and that one trips on non clean url's.
Windows also seems to dislike '/drupal/' in the url for now (not sure what causes it, the webdav module or windows).
Comment #3
Yoran commentedYep, not using clean URL is a big issue when using webdav.
About the internal browser, I'm not sure I'll keep it forever. Basicaly I less and less se the point of it. If you have any opinion I'm really interested.
Comment #4
Yoran commentedfeel free to open this again is your issue is not solved.
Comment #5
SQP commentedWrong post , should have be that one
Comment #6
SQP commentedsorry, browser bug forced me reopening the issue, and I choosed the wrong one, I restore as it was
Comment #7
mably commented