On Sep 30, 2009, at 11:48 PM, Denis Demichev wrote:
Hello there!
I want to ask for a help - spending last 2 days trying to package a
primitive custom module for magnolia 4.1 community edition.
I've read http://documentation.magnolia-cms.com/reference/custom-module.html
and trying to follow this how to:
1. Created following file structure:
META-INF
mgnl-bootstrap
mgnl-bootstrap-samples
mgnl-files
The module descriptor xml must be in META-INF/magnolia/<module-name>.xml
Bootstrap files and files-to-extract have to be in mgnl-bootstrap/
<module-name>/ and mgnl-files/[...]/<module-name>/ respectively.
4. created dummy com.abc.cms.ABCModule and placed it into module
folder
Not needed.
5. Placed *.jsp template files to
mgnl-files\templates\ProofOfConcept\templates\custom.jsp
This path does not contain your module name: the file will never be
extracted.
however due to some exception or misconfiguration it fails to
import actual data.
Got a stacktrace we could look at somewhere ?
On Oct 1, 2009, at 8:50 AM, Bert Leunis wrote:
Did you create a ModuleVersionHandler?
Not required. Denis' simple case should work with the default. (I
would recommend having an MVH of course, but it's just not needed here
yet, and isn't the reason why his module doesn't "work")
On Oct 1, 2009, at 9:09 AM, Andreas Weder wrote:
a module only imports data (DMS, Data module, Website repository),
if you set the magnolia.bootstrap.samples property to true.
Not true. Everything under mgnl-bootstrap/<module-name>/ will be
imported by default; it's the stuff under mgnl-bootstrap-samples/
<module-name>/ that will be imported only if the
magnolia.bootstrap.samples property is set to true.
Cheers,
-g
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
