Hmm...
I just modified my build to not have the samples module included, and
redefined my module the to be of the
info.magnolia.module.admininterface.SimpleContentModule and now my
templates are showing up in the list of pages that I can edit.
I don't want to use the samples module in my production app anyway,
so getting rid of it helps. Also, it bootstraps much faster when it
doesn't have to create all of those content nodes :)
Ryan
On Aug 29, 2007, at 2:14 PM, Ryan Gardner wrote:
David,
That is how I have mine organized, I just left the modules node off...
What kind of module is your module defined as in the src / main /
resources / META-INF/ magnolia / modulename.xml file?
Here is my module definition:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE module SYSTEM "module.dtd" >
<module>
<name>ytc</name>
<displayName>YTC Templates</displayName>
<class>com.ytc.pubsite.YtcTemplateModule</class>
<version>1.0.0-SNAPSHOT</version>
</module>
The only main difference between my module and the samples module
is that samples is of class
<class>info.magnolia.module.admininterface.SimpleContentModule</class>
and it defines a default public URI in it's properties.
:(
I'm glad to know that you are able to get yours working, but really
wondering why mine wont work.
Ryan
On Aug 29, 2007, at 2:05 PM, David Smith wrote:
How about this in the config repository:
modules /
ytc /
templates /
[template defs here]
paragraphs /
[paragraph defs here]
dialogs /
[dialog defs here]
That's how I organize it and it works (Magnolia 3.0.3).
--David
Ryan Gardner wrote:
I'm using Magnolia 3.0.4 snapshot (building from the svn 3.0
branch) -
I'm trying to build my templates, dialogs, and paragraphs in a
module so that I can have an easier way to handle moving them
around. I have the module building and importing, and I can see
my nodes that I have bootstrapped inside my module (named ytc)
For starters, I've basically renamed the samples files I plan
to use new prefixes and adjusted their configurations to match
the new names.
Here's what the node for my module looks like in AdminCentral:
ytc /
config / (empty)
templates/
ytcContent
... etc
dialogs/
ytc-page-properties
... etc
paragraphs/
ytcTextImage
... etc
In AdminCentral - I don't see my ytcContent node. Instead of
using the properties file for a name, I hard coded it to "YTC
Two Column Content" - but when I got to either create a new page
or edit an existing one, I don't see the "YTC Two Column
Content" anywhere in my list of templates to choose from. I only
see the ones from the samples module.
my YTC module was built using the maven archetype, and is in a .
I wonder if instead of being a module of my own type, I need to
make it a
"info.magnolia.module.admininterface.SimpleContentModule" which
is the same kind of module that the samples module is.
I suppose if I can't figure out how to get this to work, I can
just move my stuff into the root WEB-INF directory and put the
bootstrap files in the common bootstrap area.. building them as
a module feels a lot cleaner to me though.
Ryan
On Aug 29, 2007, at 1:26 PM, David Smith wrote:
In my experience, if the dialogs, pages, and paragraphs sections
of config are stored in modules section of the config tree and
exported out and saved in the bootstrap, it does deploy
correctly (paragraphs available, etc., ...) Can you provide
more detail on exactly what you are doing and what version of
Magnolia you are working with?
--David
Ryan Gardner wrote:
For sanity's sake, I want to put all of my templates in my own
custom module - very similar to how the samples module has
the templates in their module. I've got my module set up and
building, and doing all of what I want it to do except I have
noticed that my templates are not available as page templates.
When I go to a page and click on the popup menu - none of the
templates in my custom module show up. If I copy one of the
template notes out of my module and paste the node into the
Templating tree - I see the node there.
How does the Samples module manage to get it's template node
visible to the website part, but not my module?
Is there any way for me to get my module's templates to be
treated the same way as the samples module one?
Ryan
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
