Incompatibility with sourcerer plugin? [Not a jDownloads bug]

[avee]

On my project use the plugin Sourcerer and jDownloads. Sourcerer is a plugin which allows to insert php code into an html module. I use it for some general site elements (possibly until I develop custom modules to do the jobs at hand).

On jDownloads pages on the website the {source} tags in the html modules are not processed though. Users are presented with plain php. There is nothing confidential in it, but it looks like a mess. It works on other pages of the site. My solution for now was to disable these site modules on jDownloads pages, but it is not pretty.

Is it some misconfiguration that I caused myself, or is it a problem with jDownloads 3.2? I am using jDownloads  3.2.12 Beta

Thanks!

[ColinM]

Hi
Could you clarify a little for me please.  When you say jDownloads 'pages' what is it you are showing? Is it one of the jDownloads modules? Do you have an example we could look at or may be a screen dump?  Where you putting the {source} tag in a jDownloads layout?  Are you perhaps putting the tag in the 'before' or 'after' section of a jD module?

I am familiar with the Sourcerer plugin from NoNumber and I presume that is the one you are using.

Please also note that the jDownloads Content plugin that allows showing download info in an article is not yet available for the jd 2.5 or jD3.2 series.

Colin

[ColinM]

With regular content Plugins then jDownloads outputs the result of the plugin.  However in the case of the Sourcerer Plugin the output is code which should be obeyed.  jDownloads does not 'know' that it is code to be obeyed. 
It is considered however that obeying the code is too much of a security gap should an editor account be compromised. In the cases where sourcerer is used to outsmart editor restrictions this was solved by using another editor for the administrator.

Further it is considered better to develop appropriate modules to handle the required php code. Maybe Sourcerer gives too much power to anyone able to reach an editor.

Accordingly this has been re-classified as Not a jDownloads bug.

Colin