We only create custom modules for sites if they have custom
functionality (i.e. custom Java code). In all other cases the export/
import/activate method worked fine for us.
-will
On 10.06.2009, at 15:34, Grégory Joseph wrote:
On Jun 10, 2009, at 3:05 PM, Jechoux, Corentin wrote:
Hello dear Magnolia user !
my question is simple : does every web site manage by magnolia MUST
be a module ? or is there another wzay to deal with it ?
No, this is not a must. Packaging functionality and/or content in a
module is just one possible way to share/transport it.
Other possibilities are simple export/imports, activation, the
packager module, ...
-g
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
