-
I'm not sure if the issue is that they aren't allowed. It seems more like the server detects the static file extension, and transfers it as a cookie-less request.
I'll make the file extension optional (by replacing the dot with a space replacement) for the next build. In the mean time, you can avoid this issue in 2 steps.
1. Create a new plugin.
Product: VaultWiki
Hook Location: vault_url_encode
Execute Order: 5
Title: Fix for Cloud platform
PHP Code:
Code:
if (IMAGE_SPACE AND $namespaceid == IMAGE_SPACE)
{
if ($this->setcache["$langid"] == 'U')
{
$replacementlist['.'] = ' ';
}
else
{
$allowstring = str_replace('\.', '', $allowstring);
}
}
2. Go to AdminCP > Namespace Manager. In the Controls for "Image", click "Rebuild". This should remove the dot from the page URLs to prevent it from being detected as a file extension.
-
Thanks, pegasus! That fixed it. A few quick questions:
1. So users should still be advised to post article names that match the name-and-extension of the file that they are uploading, correct?
2. Will using [image]Image:Imagename_ext[/image] work? Or should they use the actual page title -- Image:Imagename.ext?
3. When we upgrade to the next build of VaultWiki, will we need to remove this plugin, or will it be automatically accepted (and not duplicated)?
Thanks again!
-
1/2. Both works, but they should continue to use the actual page title to avoid confusion.
3. This plugin will not be needed in the next build - it will be overwritten by the upgrade process. Instead, there will be a setting that addresses this.