So that interception would fail?
How can I inspect that?
paul
On 19 juil. 2013, at 16:06, Edo Beutler wrote:
Yes, that's the plugin. If you found it configured
in xwiki.cfg and got it
in velosity it's active. I suppose it's in oldcore because it's a plugin
and not a component and, afaik, it's not (yet) possible to do it in a
component since it intercepts the download action.
Every time you access a file using the download action
(/xwiki/bin/download/...) the downloadAttachment method in the plugin gets
called and the plugin checks the file.
On Fri, Jul 19, 2013 at 3:52 PM, Paul Libbrecht <paul(a)hoplahup.net> wrote:
>
> On 19 juil. 2013, at 15:38, Paul Libbrecht wrote:
>
>>> 2. The image can not be properly decoded and hence not resized. One (of
>>> many) reasons for that: the image uses CMYK colour scheme (from print)
>>> instead of the RGB expected by the image plugin. You can check that in
> any
>>> decent graphics editing program.
>>
>>
>> Also not the case: the result of identify:
>> 200x256 200x256+0+0 8-bit sRGB 50.8KB 0.000u 0:00.000
>>
>> The image plugin would be doing this?
>> Indeed it is configured:
>> com.xpn.xwiki.plugin.image.ImagePlugin,\
>>
>> It seems to be living inside xwiki-platform-legacy-oldcore-5.1.jar but
> maybe that plugin is disabled?
>
> Not disabled: in velocity xwiki.image gives me:
> com.xpn.xwiki.plugin.image.ImagePluginAPI@2fc98f55
> Can it be the image plugin is not called?