HI! First of all - thanks a lot for the module! It saved me a lot of time
But there is one problem (not sure if it's a bug in any of the involved plugins/your module). Not all plugins are interpreted by the ariprocesscontent. For example:
1.the ariprocesscontent module is set to active
2.the custom php module which i use to test the plugins includes the following code (for googlemaps and tree different flickr photo stream pluins):
{mosmap width='200'|height='180'|lat='52.052312'|lon='4.447141'|
zoom='3'|zoomType='Large'|zoomNew='0'|mapType='Satellite'|showMaptype='1'|
overview='0'|text='sv DWO'|tooltip='DWO'|marker='1'|
align='center'}
{easyflickr count=2,size=t,tag=snow dog}
[flickr photo=2960116125]
{flickr-album} Type=Search, Keywords=world domination {/flickr-album}
3. on the website only map and the easyflickr are embedded as expected, the last two plugins are schown just as a text.

Is this a problem in those plugins? Any idea how can i solve it?


Thanks you very much in advance!

Hello,

This plugins correctly work if you place this code in article content?

Regards,
ARI Soft

Thanks for the very fast reply.
That was a really super question! I tried this in a content article and found out:

inside of the Jommla article every plugin (except {flickr-album} - it is a module) works fine. And (!) on the same page the ARI Process Conten module interprets all included plugins and even {flickr-album} also without any problems .
But as soon as i switch to any other page (not content related (in url there is nothing like: ..index.php?option=com_content..) the problem (i described at my first message) appears again.

Magic!

Since we are all busy and have to bring the things forward asap, i decided to use plugin which was working with ARI Process Conten module from the very beginning. But i am still wondering about the issue with all others plugins.

hello there,
i happen to be working on this module
exactly the same time as you posted
your issue. i was looking for
similar answers, before i go dig the
solution myself, but anyhow since
you're the only soul with this problem
( + me ), here is somethings i
found out which may help you..


two things...

1. the module must be publised
on ALL pages ( unless you specifically
do not want it's services on any
page, it has to be all. ).

2. there is a posibility
that some mambots do not use
onPrepareContent, they may use the
another event,
onAfterDisplayContent, which is think
is only in joomla 1.5.

in any case, *if* you are using
joomla 1.5, to be safe try adding
this in...

$dispatcher->trigger('onPrepareContent', array($row, $params, 0), true);
$dispatcher->trigger('onAfterDisplayContent', array($row, $params, 0), true);

after the line
$dispatcher->trigger
('onAfterDisplayContent'.....

this does the same thing the mod is
designed for catering for those plugins
which uses the other mentioned event.

if you're using joomla 1.0
i have not got around to that
working out a solution yet for that
but it is likely similar, so
you could probably figure it out.



to admin:

i am suffering a little bit as the
width i get from this screen in
the middle column is as you see me
typing.

if at all it is possible for you to
use a wider format to allow us oxygen,
it would help.

bye and thanks.