Re[2]: Re: [Bx-bugs] [Bug 899] doctypes

Sunday, January 29, 2006, 6:38:07 PM, Christian Stocker wrote:
CS> Hi again
CS> I had some idea, about the getStylesheetNameByRequest method.
CS> Why not add another method like $collection->>getPipelineParametersByRequest($filename,$ext)
CS> and the plugins can return a whole array of pipeline parameters, the
CS> xmldoc would then
CS> return array("stylesheet" => "mystylesheet.xsl");
CS> and the bxcms action puts them into the pipeline.
CS> This would make it more flexible to add any parameter to the pipeline
CS> and not just one called "stylesheet".

I have just two questions to understand problem deeper:

1. The 'pipelineName' parameter is retrieved by FIRST plugin listed in .configxml
Thus, it is global for whole collection.
Is it realy plugin what is responsible for choosing pipeline?
/* I imagine plugins as something lower ordered then pipeline and
.configxml, and thus chooseing higher order from lower order looks strange for me */

2. The only pipeline parameter requested by Id is piplinename in
bxcmsadm action.
In this only point the id is always equal to "/$filename.$ext" or "/$filename",
in spite of what could plugin::getIdByRequest($filename,$ext) return.
On the other hand, getPipelineByRequest first converts request using
this plugin method.
What is the logic behind this ?

-- 
 qMax

-- 
bitflux-cms mailing list
[email protected]
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms