As I build more and more plugins I am finding that there is an
increasing opportunity for collisions in the URI space. This is caused
by plugins needing to have a unique URI pattern so that they know when
they are to process a request.
For example, if the slides plugin is installed there are
Marcus Crafter wrote:
Is http://issues.cocoondev.org/browse/FOR-356 relevant? (I confess to
not having absorbed your problem, or that in the issue, but instinct
seems to link them)
This is the one. From Upayavira's email it looks like it's been fixed
in Cocoon SVN (ie. the writable check isn't
Ross Gardler wrote:
...
So are any of these formats suitable? Which should we document as the
standard:
...
Comments/suggestions?
+0 to any
I honestly don't know if/how they will work one better than the other,
so any will do :-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
On Mon, 2005-01-03 at 22:03 -0600, Antonio Gallardo wrote:
On Lun, 3 de Enero de 2005, 18:47, Ross Gardler dijo:
I would therefore like to add my support to the suggestion (from David I
think) that we simply change the documentation to make it clear that
HTML and XHTML are suitable input
