was recently fixed so it works in 4.2.0
But it was never released to Plugins web on t.o.
I was going to do that when I thought that I'd better test it in 4.1.2 first.
And it does not work at all.
It is really really bad that we end up having to release two versions of plugins for two different TWiki versions.
For customers on 4.1.2 using configure to install or update one of the 4.2.0 only plugins means that they will never get it to work. Especially in the upgrade situation customers can without knowing the danger update a plugin like CompareRevisionsAddOn
and see themselves with a plugin that does not work at all. And with no way to downgrade again with configure.
Plugins should be made so they are compatible one TWiki generation back.
Especially going from 4.1.2 to a 4.2.0 should not be such a big deal.
How could we allow such huge totally not-backwards compatible template changes to take place?? I will NEVER understand why this was needed in a 4.1 to 4.2 update.
How do we get CompareRevisionsAddOn
released in a version that works both in 4.1.2 and 4.2.0?
I cannot overview all these template changes.
We should not release the CompareRevisionsAddOn
to t.o. until this is fixed.
- 11 Dec 2007
I cannot help with this, I'm afraid. other plugins have templates for 4.0, 4.1 already and will now probably have 4.0, 4.1 and 4.2 templates on board (if the maintainers care about backwards compatibility).
The important thing is that we all agree the templates should be thought of as an API and have that as a stated long term goal - but things will
be a bit interesting until we get there .. as I see it anyway.
I think WebPermissionsPlugin
had the same problem recently, but I can't remember what was done there to keep backwards compatibility - anyway, perhaps some inspiration can be found there.
- 12 Dec 2007
This will be fixed with Item5143
- 17 Dec 2007