That was a quite obvious question, that nobody asked before....
The code respects hasModel at the moment. hasContentModel is just used
around the place, disregard it.
And yes, we might make hasContentModel be respected like hasModel, but
hasModel will not be deprecated for a good long while.
On Tue, 2010-01-12 at 11:23 +0100, Renato Furter wrote:
> we plan to upgrade to 3.3 any time soon and I'm a bit confused about the
> content model relation definition.
> Which relation should be used in the RELS-EXT: hasModel or hasContentModel?
> The documentation favors hasModel but still finds a fair amount of
> Showing 1-10 of 96 for hasModel
> Showing 1-10 of 35 for hasContentModel
> Does it matter at all or is one of the deprecated?
> - Renato