[TYPO3-project-formidable] XML version check against installed version
Jerome Schneider
typo3dev at ameos.com
Tue Feb 24 17:41:38 CET 2009
Hi Adrian,
That's a good idea, and you'll have such a feature in revision 2.0.319
and above.
one may now define /minVersion="X.XX.XXX" and /maxVersion="X.XX.XXX" on
the /formidable xml-tag
if a condition is not met, Formidable displays a mayday screen
I think that it's better to use new tags than the /version one to avoid
future version-locking. So that if the XML has to be tied to a specific
range of Formidable version, he'll have the ability to do so, but by
default it will be executed anyway.
What do you think ?
Jerome
Adrian Föder a écrit :
> Hi there @all,
>
> I just ran into "indiscoverable non-functionality" when gambling with
> some examples from the web page.
> The simple reason was: I didn't have the version installed that the
> example was made for. The required version stands in the root element
> "formidable", e.g.
>
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <formidable version="2.0.296">
>
> </formidable>
>
> Wouldn't it be useful when the formidable engine throws a mayday or
> something like this when it discovers a version string newer then the
> installed one?
>
>
> [AND: I'm, as you surely already noted, new to the project, so please
> excuse when there is a bugtracker available where such feature requests
> should better be posted or it has already been. The BT @ bugs.typo3.org
> has the project "formidable", but it seems a bit outdated and not really
> used...]
>
>
> Thank you very much and
> have a nice weekend!
>
> -adrian
More information about the TYPO3-project-formidable
mailing list