Hi Amir,
it is much easier. You do not have to specify a module class anymore.
Magnolia handles the module just as if you extend AbstractAdminModule.
Just have a try.
Ralf
Amir Mistric schrieb:
Hi
I am trying to figure out what is the appropriate way to have a custom module
which just contains templates and dialogs (simple content module)
So far I used the
<class>info.magnolia.module.admininterface.SimpleContentModule</class> in the
module xml but looking at the class, it extends AbstractAdminModule which is marked as
depracated....
Is there a different class I should be using as a definition (for 3.5) for
simple content modules?
Even if I use maven archotype to create custom module (as described at
http://documentation.magnolia.info/docs/en/developer/custommodules/createmodule.html)
I still get MyModule which extends the info.magnolia.cms.module.AbstractModule
which is also depracated...
So, with
info.magnolia.cms.module.AbstractModule
info.magnolia.cms.module.Module
info.magnolia.module.admininterface.AbstractAdminModule
All being depracated, what is the correct way to have a custom module? A simple
content module?
Much appreciated
Amir
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
