sub-content class

Wednesday 19 May 2004 9:59:50 am

Hi Dries,
what I usually do, is to create a new class of content (in your case: <i>product review</i>) and create <i>product reviews</i> as children objects of the <i>product</i> object, using the <i>Create here</i> button in the admin interface.

That is, you don't impose the relation at a design level (i.e. when specifying classes), but at an implementation level (i.e. when creating objects).

It's questionable, but it works.

Remember, though, that you have to enforce a policy, so that the user you choose to authorize, can only create <i>product reviews</i> under a <i>product</i> object and nowhere else (it can be done in the <i>role</i> sub-section of the <i>user</i> section of the admin interface.

Sounds complicated, but it's absolutely not.

Bye,
Guglielmo

Thursday 20 May 2004 3:55:23 am

Well, Dries,
the Article class is treated as an exception in the default administration interface. I don't know exactly why (I suppose it's a bug, but you'd better ask somebody in the crew).

You can very easily change this behaviour, anyway, by modifying the following file:

[ezRoot]/design/admin/override/templates/article.tpl

All you have to do is remove the comment around the

<div class="buttonblock">

block where the <i>create here</i> button lies.

Well ... that's what I've done :-)

Guglielmo