So far it's working great in the magnoliaAuthor, but when I try to publish
to the magnoliaPublic, it's not working. If I use the AdminConsole on
magnoliaPublic and try to look at the data that got published, some of it
seems a bit funky. The JCR browser is showing:
o example
+ boilerplate
o boilerplate1
o boilerplate2
o boilerplate
which is one more (empty) boilerplate than I'm seeing in magnoliaAuthor.
And when I try to view the new Data Type in the Left Nav , the main content
section shows:
[show] <javascript:show();>
info.magnolia.module.admininterface.InvalidTreeHandlerException: No
tree
handler for [boilerplate] found
info.magnolia.module.admininterface.InvalidTreeHandlerException: No tree
handler for [boilerplate] found
at
info.magnolia.module.admininterface.TreeHandlerManager.getTreeHandler(TreeHandlerManager.java:90)
at
info.magnolia.module.admininterface.AdminTreeMVCServlet.getHandler(AdminTreeMVCServlet.java:67)
at info.magnolia.cms.servlets.MVCServlet.doPost(MVCServlet.java:112)
at info.magnolia.cms.servlets.MVCServlet.doGet(MVCServlet.java:69)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:114)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:91)
at
info.magnolia.cms.filters.ServletDispatchingFilter.doFilter(ServletDispatchingFilter.java:162)
Any idea what I did wrong?
(*Chris*)
On Wed, Sep 2, 2009 at 11:46 PM, Chris Pratt <[email protected]>wrote:
> That looks absolutely perfect! Thanks for the push in the right direction.
> (*Chris*)
>
>
> On Wed, Sep 2, 2009 at 11:39 PM, Jan Haderka <[email protected]
> > wrote:
>
>>
>> On Wed, 2009-09-02 at 23:25 -0700, Chris Pratt wrote:
>> > That sounds perfect. Is there any documentation on how to achieve
>> > that? I'm a bit unclear on how to get the reusable text into the DMS?
>> > Especially since this should be achievable by non-programmers (like
>> > the rest of the system). Thanks.
>> > (*Chris*)
>>
>> Data module, _not_ DMS module.
>>
>> [1] and [2] should be enough to get you started.
>>
>> [1] http://wiki.magnolia-cms.com/display/WIKI/Data+Module+-+A+small+%
>> 27how+to%27<http://wiki.magnolia-cms.com/display/WIKI/Data+Module+-+A+small+%%0A27how+to%27>
>>
>> [2] http://documentation.magnolia-cms.com/modules/data.html
>>
>> HTH,
>> Jan
>>
>>
>> >
>> > On Wed, Sep 2, 2009 at 11:08 PM, Jan Haderka
>> > <[email protected]> wrote:
>> >
>> > On Wed, 2009-09-02 at 14:39 -0700, Chris Pratt wrote:
>> > > We're using 3.6.3 and our users want to be able to
>> > essentially create
>> > > reusable chunks of text that they can drop on pages, as
>> > needed. I've
>> >
>> >
>> > Would not it be better to use data module rather then creating
>> > a bogus
>> > pages to keep together bunch of paragraphs that you might want
>> > to
>> > include in some other random pages?
>> > When you define data type in the data module, you can also
>> > define the
>> > dialog with whatever custom fields you want and you don't need
>> > to have
>> > any templates.
>> > So later when you want to use such a chunk of content stored
>> > in the data
>> > module, all you do is create a paragraph with only one control
>> > - link
>> > (or uuidLink) where user can select the chunk from the data
>> > module they
>> > want and the paragraph template just fetches the content and
>> > displays
>> > it. Since you have a path (or uuid) to the content all you
>> > need to do
>> > when retrieving it is not to forget to specify also repository
>> > "data".
>> >
>> > HTH,
>> > Jan
>> >
>> > > been trying to figure out a way to create a Paragraph that
>> > can
>> > > somehow inject a page defined in the website context into
>> > the current
>> > > page, but no matter what I try, it just doesn't work. What
>> > I've tried
>> > > is creating a boilerplateDialog with a link (I've also tried
>> > uuidLink)
>> > > field that refers to the page I want to inject. In the
>> > > boilerplate.jsp paragraph template I've tried:
>> > >
>> > > <cms:setNode var="node"/>
>> > >
>> > > <jsp:insert page="${node.link}"/>
>> > >
>> > > <c:import url="${node.link}"/>
>> > >
>> > > <cms:loadPage templateName="${node.page}"> <!-- I've tried
>> > every
>> > > combination of attributes I can think of -->
>> > > <cms:contentNodeIterator>
>> > > <cms:includeTemplate/>
>> > > </cms:contentNodeIterator>
>> > > <cms:unloadPage/>
>> > >
>> > > If there's a better way to give the users the same
>> > functionality I'm
>> > > all for it. Otherwise is there a way to make this scheme
>> > work?
>> > > (*Chris*)
>> >
>> > --
>> > Best regards,
>> >
>> > Jan Haderka
>> > Magnolia International Ltd.
>> >
>> > Meet us at the Magnolia Conference
>> > http:/www.magnolia-cms.com/conference
>> >
>> > Magnolia® - Simple Open Source Content Management
>> >
>> >
>> >
>> > ----------------------------------------------------------------
>> > For list details see
>> > http://www.magnolia-cms.com/home/community/mailing-lists.html
>> > To unsubscribe, E-mail to:
>> > <[email protected]>
>> > ----------------------------------------------------------------
>> >
>> >
>> >
>> --
>> Best regards,
>>
>> Jan Haderka
>> Magnolia International Ltd.
>>
>> Meet us at the Magnolia Conference
>> http:/www.magnolia-cms.com/conference
>>
>> Magnolia® - Simple Open Source Content Management
>>
>>
>> ----------------------------------------------------------------
>> 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]>
----------------------------------------------------------------
