Nabble - Magnolia - User

Re: when will 4.2.2 be released?

2009-11-25T23:40:45Z

You're welcome.

On Wed, 2009-11-25 at 20:42 +0100, Grégory Joseph wrote:

Hi Toby,

That issue's been fixed with 4.2.1, which has just been released!  
Thanks for the patch! :)

Enjoy,

-g

On Nov 25, 2009, at 6:30 PM, Toby O'Rourke wrote:

> Hi,
>
> The subject says it all really! We are looking for the fix to  
> MAGNOLIA-2957 to make it into a released version rather than a  
> snapshot...
>
> Cheers,
>
> Toby.
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> ----------------------------------------------------------------


----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

Re: A couple of questions:

2009-11-25T15:33:31Z

If there is indeed a need to extend the jsp better templating to other
servers than tomcat, please let me know. We can either write that or
help you write it yourself. The approach taken in the module is through
the |DirContext| - other servers (JBoss, Websphere) support similar
extension points but they are not standardized through a common API -
that's why we only implemented tomcat at this point.

Ruben

Boris Kraft wrote:

>
> Except there is a community contribution by Headwire which actually
> provides that functionality in certain environments for JSP files.
> Check out "Better Templating" on the wiki:
>
> http://wiki.magnolia-cms.com/display/WIKI/List+of+Magnolia+Modules
>
> (search for jsp templating)
>
> Regards
> Boris
>
>
>
>
> On Nov 20, 2009, at 6:00 AM, Ernst Bunders wrote:
>
>> hello Linden
>>
>> jsp files need to be on the file system, and can unfortunately not be
>> loaded from an arbitrary Reader InputStream (which would be requred
>> for loading templates from reposiotory nodes).
>> So, you can reuse your jsp's (for what it's worth) by placing them in
>> the webapp, but if you want to be able to maintain them in the
>> repository, you'll have to convert them to freemarker.
>>
>> regards,
>>
>> Ernst
>>
>>
>> 2009/11/20 Linden Varley <Linden.Varley@...>
>> Hi all
>>
>>
>> Is it possible to set the “servername” property within the magnolia
>> config, rather than it getting it from the system on startup? (This
>> is useful when using a different domain name when accessing magnolia,
>> such as when proxying to it from another address)
>>
>>
>> Secondly, being able to edit templates within the web interface using
>> the templating kit is great. I’ve got a lot of existing jsp templates
>> on the file system, which I would like to add within the templates
>> node in the templating kit so I can also edit them directly. Is this
>> possible and how?
>>
>>
>> Thanks
>>
>> - Linden
>>
>>
>>
>>
>>
>> The contents of this email are confidential and may be subject to
>> legal or professional privilege and copyright. No representation is
>> made that this email is free of viruses or other defects. If you have
>> received this communication in error, you may not copy or distribute
>> any part of it or otherwise disclose its contents to anyone. Please
>> advise the sender of your incorrect receipt of this correspondence.
>>
>>
>> ----------------------------------------------------------------
>> For list details see
>> http://www.magnolia-cms.com/home/community/mailing-lists.html
>> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
>> ----------------------------------------------------------------
>>
>>
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> ----------------------------------------------------------------
>

Re: Login after backup restore

2009-11-25T14:54:43Z

Jan, thank you very much for your support!

I ended up bootstrapping the sample configuration and then importing all the data again. Here again, the "delete-the-index" hint was really helpful!

Cheers,

Sebastian

On Wed, Nov 25, 2009 at 8:53 AM, Jan Haderka <jan.haderka@...> wrote:

You can try [1] to temporarily disable all security and then try to
reset the passwords.

[1] http://wiki.magnolia-cms.com/display/WIKI/Messed+Up+Security

HTH,
Jan

On Tue, 2009-11-24 at 19:05 +0100, Sebastian Schuon wrote:
> Hi Jan,
> thanks for all the suggestions! Your pointer to re-building the index
> was a good one, since an initial error "can't find user anonymous" was
> resolved, but I still can't login :( Even copying a working instance
> from another system didn't help.
> On how to reset the superuser password, I guess you refer to the
> following document: http://wiki.magnolia-cms.com/display/WIKI/Reset
> +all+passwords . Only thing I don't see is how to ever execute the
> JSP, since for the author space, all JSPs need prior authentication,
> which I am lacking...
> Any suggestions are highly appreciated!
> Cheers,
> Sebastian
>
> On Mon, Nov 23, 2009 at 6:56 PM, Jan Haderka
> <jan.haderka@...> wrote:
>
>
> On Mon, 2009-11-23 at 18:07 +0100, Sebastian Schuon wrote:
> > Hi Jan,
> > thanks for your quick reply. I suspect indexes being
> "repositories
> > \magnolia\workspaces\*\index" right? I've deleted them and
> they get
>
>
> yes that's what I meant.
>
> > rebuild, but no luck logging in... do you have any other
> suggestion?
>
>
> hmm, that is strange. I have had a problem few times and
> re-indexing
> always made it go away (the issue is caused by the fact that
> indexes are
> generated asynchronously and do not stop the shutdown, so
> after the
> restore they might not be finished yet when the main restore
> thread
> already initiated shutdown).
>
> The other things we can look for:
> - were there any errors in the log files from startup?
> - any errors during the restore?
>
> you might want to post your log files to pastebin.com or
> similar service
> and post the links to them here so we can have a look.
>
> ... more thoughts:
> - the DB schema into which you restored the instance was clean
> right?
> - the restore was made into exactly same version of Magnolia
> as the one
> in which the backup was made?
>
> - if nothing else helps, you might want to follow the guide on
> wiki on
> how to reset superuser password.
>
> Cheers,
> Jan
>
>
> > Thanks,
> > Sebastian
> >
> > On Mon, Nov 23, 2009 at 4:35 PM, Jan Haderka
> > <jan.haderka@...> wrote:
> >
> > Shutdown, delete indexes from all workspaces, and
> startup
> > again. Should
> > be ok then.
> > HTH,
> > Jan
> >
> >
> >
> > On Mon, 2009-11-23 at 16:29 +0100, Sebastian Schuon
> wrote:
> > > Hi all,
> > > I use mysql as a repository to magnolia. Now I
> tried to
> > update an
> > > older installation by simply updating the
> database. I am now
> > puzzled,
> > > that I can't login anymore. Since I can login into
> the newer
> > > installation, I am quite positive that the
> password is
> > correct. Can
> > > anyone give me pointers what debug output might
> help?
> > > Best,
> > > Sebastian
> >
> >
> >
> >
> >
> ----------------------------------------------------------------
> > For list details see
> >
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> > To unsubscribe, E-mail to:
> > <user-list-unsubscribe@...>
> >
> ----------------------------------------------------------------
> >
> >
> >
> >
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to:
> <user-list-unsubscribe@...>
> ----------------------------------------------------------------
>
>
>
>

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

Re: Re: custom 301 error message -- moved permanently

2009-11-25T12:10:31Z

Hi Åke,

On Nov 23, 2009, at 6:52 PM, Åke Argéus wrote:

>
>
> 23 nov 2009 kl. 08.52 skrev Matteo Pelucco:
>
>>
>> Åke Argéus ha scritto:
>>> The way we handled this was making a custom virtualURIFilter that
>>> handles responses of the type moved: as well as redirect: and
>>> forward:.
>>> This opened up the whole power of things like regexp-
>>> virtualurimappings.
>>
>> Oh, yes, it is a nice and powerful thing.
>> But how can you handle the response within a virtual uri mapping?
>> A "standard" virtual uri mapping simply redirect towards an
>> internal page...
>>
>> The steps I miss are:
>>
>> 1) How can I retrieve the response inside a virtual uri mapping?
>> 2) Is it safe to close the response (after having set the right
>> header infos) within a virtual uri mapping?
>
>
> Well. In the virtualURIfilter you can most certaintly do whatever
> you want with the response, and it has worked for us to send a 301
> instead of 302 if the virtualurimapping returns moved; instead of
> redirect:.
>
> At least for now we have no cases where we are really interested in
> checking anything in the request in our virtualurimappings though it
> has crossed my mind that we might end up there.
>
> Not sure what the best way to do that is though. It's quite possible
> to extend the virtualurifilter even further and add the ability to
> load a special customized version of virtualurimapping that takes a
> request in it's active methods, and when looping though all the
> existing virtualurimappings you can just do an instanceof to check
> for this special class of virtualurimapping and act accordingly.
> This is a bigger reimplementation of the virtualurifilter, but not
> impossibly big, and shouldn't break a lot of things. You should
> still try to stay within the basic style and framework of the
> existing virualurifilter and could thereby keep the old functions
> while extending it with your own style of virtualurimappings and
> possible response-prefixes.
>
> VirtualUrimappings could be one of the most powerful features in
> magnolia, and it's very flexible, and isn't impossible to extend,
> though I've thought of submitting a patch to make it more extendable
> or powerful.

We'd love to see such improvements in the main code base; you're not
the only in need of such features ! Feel free to send patches over
indeed ! ;)

Cheers,

-g

>
> /Åke
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> ----------------------------------------------------------------

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

Re: when will 4.2.2 be released?

2009-11-25T11:51:15Z

Erm, nevermind... the patch wasn't included in time :(

On Nov 25, 2009, at 8:42 PM, Grégory Joseph wrote:

>
> Hi Toby,
>
> That issue's been fixed with 4.2.1, which has just been released!
> Thanks for the patch! :)
>
> Enjoy,
>
> -g
>
> On Nov 25, 2009, at 6:30 PM, Toby O'Rourke wrote:
>
>> Hi,
>>
>> The subject says it all really! We are looking for the fix to
>> MAGNOLIA-2957 to make it into a released version rather than a
>> snapshot...
>>
>> Cheers,
>>
>> Toby.
>>
>> ----------------------------------------------------------------
>> For list details see
>> http://www.magnolia-cms.com/home/community/mailing-lists.html
>> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
>> ----------------------------------------------------------------
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> ----------------------------------------------------------------

Re: when will 4.2.2 be released?

2009-11-25T11:42:13Z

Hi Toby,

That issue's been fixed with 4.2.1, which has just been released!
Thanks for the patch! :)

Enjoy,

-g

On Nov 25, 2009, at 6:30 PM, Toby O'Rourke wrote:

> Hi,
>
> The subject says it all really! We are looking for the fix to
> MAGNOLIA-2957 to make it into a released version rather than a
> snapshot...
>
> Cheers,
>
> Toby.
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> ----------------------------------------------------------------

Magnolia 4.2 released

2009-11-25T11:27:09Z

Magnolia 4.2 has been released, featuring:

* WebDAV access to template & resources repository
* Code highlighting and line numbering for the inplace-templating module
* Integration of PUR into STK
* Jackrabbit 1.6
* support for data type hierarchies
* Standard Templating Kit 1.2 with many enhancements for SEO and
Accessibility
* New simplified node builder API for easier module maintenance and
node type manipulation

Enjoy!

For download and further info, including introduction videos see
http://www.magnolia-cms.com/4-2

Thanks to all the great community contributions, keep them coming!

- Boris

PS: Happy 6th birthday, Magnolia!

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

Re: A couple of questions:

2009-11-25T11:06:40Z

Except there is a community contribution by Headwire which actually
provides that functionality in certain environments for JSP files.
Check out "Better Templating" on the wiki:

http://wiki.magnolia-cms.com/display/WIKI/List+of+Magnolia+Modules

(search for jsp templating)

Regards
Boris

On Nov 20, 2009, at 6:00 AM, Ernst Bunders wrote:

> hello Linden
>
> jsp files need to be on the file system, and can unfortunately not
> be loaded from an arbitrary Reader InputStream (which would be
> requred for loading templates from reposiotory nodes).
> So, you can reuse your jsp's (for what it's worth) by placing them
> in the webapp, but if you want to be able to maintain them in the
> repository, you'll have to convert them to freemarker.
>
> regards,
>
> Ernst
>
>
> 2009/11/20 Linden Varley <Linden.Varley@...>
> Hi all
>
>
> Is it possible to set the “servername” property within the magnolia
> config, rather than it getting it from the system on startup? (This
> is useful when using a different domain name when accessing
> magnolia, such as when proxying to it from another address)
>
>
> Secondly, being able to edit templates within the web interface
> using the templating kit is great. I’ve got a lot of existing jsp
> templates on the file system, which I would like to add within the
> templates node in the templating kit so I can also edit them
> directly. Is this possible and how?
>
>
> Thanks
>
> - Linden
>
>
>
>
>
> The contents of this email are confidential and may be subject to
> legal or professional privilege and copyright. No representation is
> made that this email is free of viruses or other defects. If you
> have received this communication in error, you may not copy or
> distribute any part of it or otherwise disclose its contents to
> anyone. Please advise the sender of your incorrect receipt of this
> correspondence.
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> ----------------------------------------------------------------
>
>

when will 4.2.2 be released?

2009-11-25T09:30:00Z

Hi,

The subject says it all really! We are looking for the fix to MAGNOLIA-2957 to make it into a released version rather than a snapshot...

Cheers,

Toby.

Re: Making Templates visible/available in website new page menu

2009-11-25T00:15:09Z

Hi Abdul,

if you defined your templates under template node in your module
and developed its script you should be able to see that template
in the drop down list - f.e. have a look at
modules/templating/templates.
Maybe you can add the "visible" node to your template definition
with true value. This property determines if the template is visible
in the template drop-down list.
Also maybe restarting your server could help but Magnolia monitors
the module configuration and restarts the module if there are changes
in the module configuration so this couldn't cause your issue.
Otherwise all about templating for Magnolia 4.* you can find at

http://documentation.magnolia-cms.com/templating-guide.html

--
Best regards,

Zdenek Skodik
Magnolia International Ltd.

Magnolia® - Simple Open-Source Content Management

On Tue, 2009-11-24 at 15:05 +0100, Abdul Nabi wrote:

> Hi again folks,
>
> Hope this is another easy one... Now that the module (non-STK) is built and
> loaded into a fresh instance a it appears that the templates defined in the
> module don't "automagically" appear in the template drop down under pages...
>
> I've looked and cannot find where you link/tell Magnolia about these
> templates to have them show up in the available templates...
>
> I know it's possible since the training module we had did it... Just didn't
> clue in to ask how that magic was done.
>
> Thanks!
> Abdul Nabi
>
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> ----------------------------------------------------------------

Re: Login after backup restore

2009-11-24T23:53:31Z

You can try [1] to temporarily disable all security and then try to
reset the passwords.

[1] http://wiki.magnolia-cms.com/display/WIKI/Messed+Up+Security

HTH,
Jan

On Tue, 2009-11-24 at 19:05 +0100, Sebastian Schuon wrote:

> Hi Jan,
> thanks for all the suggestions! Your pointer to re-building the index
> was a good one, since an initial error "can't find user anonymous" was
> resolved, but I still can't login :( Even copying a working instance
> from another system didn't help.
> On how to reset the superuser password, I guess you refer to the
> following document: http://wiki.magnolia-cms.com/display/WIKI/Reset
> +all+passwords . Only thing I don't see is how to ever execute the
> JSP, since for the author space, all JSPs need prior authentication,
> which I am lacking...
> Any suggestions are highly appreciated!
> Cheers,
> Sebastian
>
> On Mon, Nov 23, 2009 at 6:56 PM, Jan Haderka
> <jan.haderka@...> wrote:
>
>
> On Mon, 2009-11-23 at 18:07 +0100, Sebastian Schuon wrote:
> > Hi Jan,
> > thanks for your quick reply. I suspect indexes being
> "repositories
> > \magnolia\workspaces\*\index" right? I've deleted them and
> they get
>
>
> yes that's what I meant.
>
> > rebuild, but no luck logging in... do you have any other
> suggestion?
>
>
> hmm, that is strange. I have had a problem few times and
> re-indexing
> always made it go away (the issue is caused by the fact that
> indexes are
> generated asynchronously and do not stop the shutdown, so
> after the
> restore they might not be finished yet when the main restore
> thread
> already initiated shutdown).
>
> The other things we can look for:
> - were there any errors in the log files from startup?
> - any errors during the restore?
>
> you might want to post your log files to pastebin.com or
> similar service
> and post the links to them here so we can have a look.
>
> ... more thoughts:
> - the DB schema into which you restored the instance was clean
> right?
> - the restore was made into exactly same version of Magnolia
> as the one
> in which the backup was made?
>
> - if nothing else helps, you might want to follow the guide on
> wiki on
> how to reset superuser password.
>
> Cheers,
> Jan
>
>
> > Thanks,
> > Sebastian
> >
> > On Mon, Nov 23, 2009 at 4:35 PM, Jan Haderka
> > <jan.haderka@...> wrote:
> >
> > Shutdown, delete indexes from all workspaces, and
> startup
> > again. Should
> > be ok then.
> > HTH,
> > Jan
> >
> >
> >
> > On Mon, 2009-11-23 at 16:29 +0100, Sebastian Schuon
> wrote:
> > > Hi all,
> > > I use mysql as a repository to magnolia. Now I
> tried to
> > update an
> > > older installation by simply updating the
> database. I am now
> > puzzled,
> > > that I can't login anymore. Since I can login into
> the newer
> > > installation, I am quite positive that the
> password is
> > correct. Can
> > > anyone give me pointers what debug output might
> help?
> > > Best,
> > > Sebastian
> >
> >
> >
> >
> >
> ----------------------------------------------------------------
> > For list details see
> >
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> > To unsubscribe, E-mail to:
> > <user-list-unsubscribe@...>
> >
> ----------------------------------------------------------------
> >
> >
> >
> >
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to:
> <user-list-unsubscribe@...>
> ----------------------------------------------------------------
>
>
>
>

Magnolia 4.1 Template question

2009-11-24T10:48:33Z

Where can I find a description (hopefully with screen shots) of each template? In example
Template: Large Article:
Description
Typical use
Etc.

I need to know about:
Section
Article
Large article
News
Event
Image Gallery
FAQ
Glossary Letter

Re: Login after backup restore

2009-11-24T10:05:22Z

Hi Jan,

thanks for all the suggestions! Your pointer to re-building the index was a good one, since an initial error "can't find user anonymous" was resolved, but I still can't login :( Even copying a working instance from another system didn't help.

On how to reset the superuser password, I guess you refer to the following document: http://wiki.magnolia-cms.com/display/WIKI/Reset+all+passwords . Only thing I don't see is how to ever execute the JSP, since for the author space, all JSPs need prior authentication, which I am lacking...

Any suggestions are highly appreciated!

Cheers,

Sebastian

On Mon, Nov 23, 2009 at 6:56 PM, Jan Haderka <jan.haderka@...> wrote:

On Mon, 2009-11-23 at 18:07 +0100, Sebastian Schuon wrote:
> Hi Jan,
> thanks for your quick reply. I suspect indexes being "repositories
> \magnolia\workspaces\*\index" right? I've deleted them and they get

yes that's what I meant.

> rebuild, but no luck logging in... do you have any other suggestion?

hmm, that is strange. I have had a problem few times and re-indexing
always made it go away (the issue is caused by the fact that indexes are
generated asynchronously and do not stop the shutdown, so after the
restore they might not be finished yet when the main restore thread
already initiated shutdown).

The other things we can look for:
- were there any errors in the log files from startup?
- any errors during the restore?

you might want to post your log files to pastebin.com or similar service
and post the links to them here so we can have a look.

... more thoughts:
- the DB schema into which you restored the instance was clean right?
- the restore was made into exactly same version of Magnolia as the one
in which the backup was made?

- if nothing else helps, you might want to follow the guide on wiki on
how to reset superuser password.

Cheers,
Jan

> Thanks,
> Sebastian
>
> On Mon, Nov 23, 2009 at 4:35 PM, Jan Haderka
> <jan.haderka@...> wrote:
>
> Shutdown, delete indexes from all workspaces, and startup
> again. Should
> be ok then.
> HTH,
> Jan
>
>
>
> On Mon, 2009-11-23 at 16:29 +0100, Sebastian Schuon wrote:
> > Hi all,
> > I use mysql as a repository to magnolia. Now I tried to
> update an
> > older installation by simply updating the database. I am now
> puzzled,
> > that I can't login anymore. Since I can login into the newer
> > installation, I am quite positive that the password is
> correct. Can
> > anyone give me pointers what debug output might help?
> > Best,
> > Sebastian
>
>
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to:
> <user-list-unsubscribe@...>
> ----------------------------------------------------------------
>
>
>
>

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

Making Templates visible/available in website new page menu

2009-11-24T06:05:26Z

Hi again folks,

Hope this is another easy one... Now that the module (non-STK) is built and
loaded into a fresh instance a it appears that the templates defined in the
module don't "automagically" appear in the template drop down under pages...

I've looked and cannot find where you link/tell Magnolia about these
templates to have them show up in the available templates...

I know it's possible since the training module we had did it... Just didn't
clue in to ask how that magic was done.

Thanks!
Abdul Nabi

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

Re: Issue with creating a custom module skeleton using a Maven Archetype

2009-11-24T03:48:36Z

On Tue, 2009-11-24 at 11:38 +0100, Abdul Nabi wrote:
> Hi Jan,
>
> Thanks for the help... Note that when using:
> http://svn.magnolia-cms.com/snapshots

oops, that was supposed to be http://repo.magnolia-cms.com/snapshots

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

Re: Issue with creating a custom module skeleton using a Maven Archetype

2009-11-24T02:38:02Z

Hi Jan,

Thanks for the help... Note that when using:
http://svn.magnolia-cms.com/snapshots
I got:

[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

GroupId: info.magnolia
ArtifactId: maven-archetype-magnolia-module
Version: 1.0.0-SNAPSHOT

Reason: Unable to download the artifact from any repository

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=info.magnolia
-DartifactId=maven-archetype-magnolia-module \
-Dversion=1.0.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file

info.magnolia:maven-archetype-magnolia-module:jar:1.0.0-SNAPSHOT

from the specified remote repositories:
id0 (http://svn.magnolia-cms.com/snapshots)

However switching to http://svn.magnolia.info/maven/snapshots seems to work.

------------------
So for all looks like the working command is:

mvn archetype:create -DarchetypeGroupId=info.magnolia \
-DarchetypeArtifactId=maven-archetype-magnolia-module \
-DarchetypeVersion=1.0.0-SNAPSHOT \
-DgroupId=com.foo.bar \
-DartifactId=my-module \
-DremoteRepositories= http://svn.magnolia.info/maven/snapshots
------------------

Cheers,
Abdul

On 11/24/09 8:18 AM, "Jan Haderka" <jan.haderka@...> wrote:

>
> Hi Abdul,
> the artifact is a bit outdated. To make build run, you need to replace
> repo link with the valid repo:
>
> mvn archetype:create -DarchetypeGroupId=info.magnolia \
> -DarchetypeArtifactId=maven-archetype-magnolia-module \
> -DarchetypeVersion=1.0.0-SNAPSHOT \
> -DgroupId=com.foo.bar \
> -DartifactId=my-module \
> -DremoteRepositories=http://svn.magnolia-cms.com/snapshots
>
> however the module it will generate will be configured to run against
> Magnolia 3.0, so you need to edit generated pom to change this to
> Magnolia 4.1.1, also need to update the repo reference to
> http://svn.magnolia-cms.com/m2
>
> After that you need to edit the generated MyModule.java and remove all
> references to AbstractModule and its exceptions as this thing doesn't
> exist anymore. In 4.x module class do not need to extend anything (at
> most you might want to have your module class to implement
> ModuleLifecycle interface if you want to have control over restart of
> the module).
>
> HTH,
> Jan
>
>
> On Mon, 2009-11-23 at 21:22 +0100, Abdul Nabi wrote:
>> Hello All,
>>
>> Hopefully a simple/stupid/newbie question (but also a good first start
>> at using the user list)...
>>
>> I¹m ready to create my module and have tried the command from the
>> ³Module QuickStart² Wiki section -
>> mvn org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create
>> -DarchetypeGroupId=info.magnolia \
>> -DarchetypeArtifactId=maven-archetype-magnolia-module \
>> -DarchetypeVersion=1.0 \
>> -DremoteRepositories=http://maven.magnolia.info/m2 \
>> -DgroupId=com.foo.bar \
>> -DartifactId=my-module
>>
>> And from the excerise guide -
>> mvn archetype:create -DarchetypeGroupId=info.magnolia \
>> -DarchetypeArtifactId=maven-archetype-magnolia-module \
>> -DarchetypeVersion=1.0.0-SNAPSHOT \
>> -DgroupId=com.foo.bar \
>> -DartifactId=my-module \
>> -DremoteRepositories=http://svn.magnolia.info/maven/snapshots
>>
>> And in both cases get -
>> [INFO] Scanning for projects...
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD FAILURE
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Invalid task 'DarchetypeVersion=1.0.0-SNAPSHOT': you must
>> specify a valid lifecycle phase, or a goal in the format plugin:goal
>> or pluginGroupId:pluginArtifactId:pluginVersion:goal
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] For more information, run Maven with the -e switch
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: < 1 second
>> [INFO] Finished at: Mon Nov 23 20:11:27 GMT+00:01 2009
>> [INFO] Final Memory: 1M/4M
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> I¹ve tried some variations, but to no avail... Before doing a deep
>> dive and getting three degrees away from my original goal just wanted
>> to check if folks had a quick pointer on this.
>>
>> Note Using Maven 2.0.6 and Magnolia EE 4.1.1
>>
>> Thanks!
>>
>> Mit freundlichen Grüssen,
>> Kind regards
>>
>> Abdul Nabi
>> Technical Architect
>>
>> frog design europe gmbh
>> Kalkofenstr. 51
>> 71083 Herrenberg
>>
>>
>>
>> ______________________________________________________________________
>> ----------------------------------------------------------------
>> For list details see
>> http://www.magnolia-cms.com/home/community/mailing-lists.html
>> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
>> ----------------------------------------------------------------
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> ----------------------------------------------------------------
>
>

Mit freundlichen Grüssen,
Kind regards

Abdul Nabi
Technical Architect

frog design europe gmbh
Kalkofenstr. 51
71083 Herrenberg

+ 49 7032 914-260 Tel
+ 49 7032 914-111 Fax
mailto:Abdul.Nabi@... <mailto:Abdul.Nabi@...>
http://www.frogdesign.com <http://www.frogdesign.com/>
Sitz der Gesellschaft: Herrenberg, Amtsgericht Stuttgart, HRB 245808
Geschäftsführung: Duncan Robertson, Bettina Teschner USt Ident Nr. DE
220 598 284

design mind: http://designmind.frogdesign.com
<http://designmind.frogdesign.com>
twitter: http://twitter.com/frogdesign <http://twitter.com/frogdesign>

P Please consider your environmental responsibility before printing this
e-mail.

CONFIDENTIAL AND PROPRIETARY INFORMATION NOTICE:
The information contained in and/or attached to this e-mail is Confidential
and Proprietary Information of frog design europe gmbh and its operating
companies and subsidiaries. This information is intended only for the
confidential use of the person(s) designated above. If this message has
reached a person or persons not designated above, you are hereby notified
that you have received this document in error and that any review,
dissemination, distribution or copying of this message is strictly
prohibited. If you are not a designated recipient, please notify frog design
europe gmbh immediately by reply e-mail and delete the original message
together with any and all attachments.

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

Re: Issue with creating a custom module skeleton using a Maven Archetype

2009-11-23T23:22:41Z

Actually even simpler - there is a newer version. Just run:

mvn archetype:create -DarchetypeGroupId=info.magnolia \
-DarchetypeArtifactId=maven-archetype-magnolia-module \
-DarchetypeVersion=1.0.1-SNAPSHOT \
-DgroupId=com.foo.bar \
-DartifactId=my-module \
-DremoteRepositories=http://svn.magnolia-cms.com/snapshots

it still sets Magnolia reference to 3.5.2 (so you want to change that in
the generated pom), but at least code compiles straightaway.

Cheers,
Jan

On Tue, 2009-11-24 at 08:18 +0100, Jan Haderka wrote:

> Hi Abdul,
> the artifact is a bit outdated. To make build run, you need to replace
> repo link with the valid repo:
>
> mvn archetype:create -DarchetypeGroupId=info.magnolia \
> -DarchetypeArtifactId=maven-archetype-magnolia-module \
> -DarchetypeVersion=1.0.0-SNAPSHOT \
> -DgroupId=com.foo.bar \
> -DartifactId=my-module \
> -DremoteRepositories=http://svn.magnolia-cms.com/snapshots
>
> however the module it will generate will be configured to run against
> Magnolia 3.0, so you need to edit generated pom to change this to
> Magnolia 4.1.1, also need to update the repo reference to
> http://svn.magnolia-cms.com/m2
>
> After that you need to edit the generated MyModule.java and remove all
> references to AbstractModule and its exceptions as this thing doesn't
> exist anymore. In 4.x module class do not need to extend anything (at
> most you might want to have your module class to implement
> ModuleLifecycle interface if you want to have control over restart of
> the module).
>
> HTH,
> Jan
>
>
> On Mon, 2009-11-23 at 21:22 +0100, Abdul Nabi wrote:
> > Hello All,
> >
> > Hopefully a simple/stupid/newbie question (but also a good first start
> > at using the user list)...
> >
> > I’m ready to create my module and have tried the command from the
> > “Module QuickStart” Wiki section -
> > mvn org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create
> > -DarchetypeGroupId=info.magnolia \
> > -DarchetypeArtifactId=maven-archetype-magnolia-module \
> > -DarchetypeVersion=1.0 \
> > -DremoteRepositories=http://maven.magnolia.info/m2 \
> > -DgroupId=com.foo.bar \
> > -DartifactId=my-module
> >
> > And from the excerise guide -
> > mvn archetype:create -DarchetypeGroupId=info.magnolia \
> > -DarchetypeArtifactId=maven-archetype-magnolia-module \
> > -DarchetypeVersion=1.0.0-SNAPSHOT \
> > -DgroupId=com.foo.bar \
> > -DartifactId=my-module \
> > -DremoteRepositories=http://svn.magnolia.info/maven/snapshots
> >
> > And in both cases get -
> > [INFO] Scanning for projects...
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] BUILD FAILURE
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Invalid task 'DarchetypeVersion=1.0.0-SNAPSHOT': you must
> > specify a valid lifecycle phase, or a goal in the format plugin:goal
> > or pluginGroupId:pluginArtifactId:pluginVersion:goal
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] For more information, run Maven with the -e switch
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Total time: < 1 second
> > [INFO] Finished at: Mon Nov 23 20:11:27 GMT+00:01 2009
> > [INFO] Final Memory: 1M/4M
> > [INFO]
> > ------------------------------------------------------------------------
> >
> > I’ve tried some variations, but to no avail... Before doing a deep
> > dive and getting three degrees away from my original goal just wanted
> > to check if folks had a quick pointer on this.
> >
> > Note – Using Maven 2.0.6 and Magnolia EE 4.1.1
> >
> > Thanks!
> >
> > Mit freundlichen Grüssen,
> > Kind regards
> >
> > Abdul Nabi
> > Technical Architect
> >
> > frog design europe gmbh
> > Kalkofenstr. 51
> > 71083 Herrenberg
> >
> >
> >
> > ______________________________________________________________________
> > ----------------------------------------------------------------
> > For list details see
> > http://www.magnolia-cms.com/home/community/mailing-lists.html
> > To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> > ----------------------------------------------------------------
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> ----------------------------------------------------------------

Re: Issue with creating a custom module skeleton using a Maven Archetype

2009-11-23T23:18:01Z

Hi Abdul,
the artifact is a bit outdated. To make build run, you need to replace
repo link with the valid repo:

mvn archetype:create -DarchetypeGroupId=info.magnolia \
-DarchetypeArtifactId=maven-archetype-magnolia-module \
-DarchetypeVersion=1.0.0-SNAPSHOT \
-DgroupId=com.foo.bar \
-DartifactId=my-module \
-DremoteRepositories=http://svn.magnolia-cms.com/snapshots

however the module it will generate will be configured to run against
Magnolia 3.0, so you need to edit generated pom to change this to
Magnolia 4.1.1, also need to update the repo reference to
http://svn.magnolia-cms.com/m2

After that you need to edit the generated MyModule.java and remove all
references to AbstractModule and its exceptions as this thing doesn't
exist anymore. In 4.x module class do not need to extend anything (at
most you might want to have your module class to implement
ModuleLifecycle interface if you want to have control over restart of
the module).

HTH,
Jan

On Mon, 2009-11-23 at 21:22 +0100, Abdul Nabi wrote:

> Hello All,
>
> Hopefully a simple/stupid/newbie question (but also a good first start
> at using the user list)...
>
> I’m ready to create my module and have tried the command from the
> “Module QuickStart” Wiki section -
> mvn org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create
> -DarchetypeGroupId=info.magnolia \
> -DarchetypeArtifactId=maven-archetype-magnolia-module \
> -DarchetypeVersion=1.0 \
> -DremoteRepositories=http://maven.magnolia.info/m2 \
> -DgroupId=com.foo.bar \
> -DartifactId=my-module
>
> And from the excerise guide -
> mvn archetype:create -DarchetypeGroupId=info.magnolia \
> -DarchetypeArtifactId=maven-archetype-magnolia-module \
> -DarchetypeVersion=1.0.0-SNAPSHOT \
> -DgroupId=com.foo.bar \
> -DartifactId=my-module \
> -DremoteRepositories=http://svn.magnolia.info/maven/snapshots
>
> And in both cases get -
> [INFO] Scanning for projects...
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Invalid task 'DarchetypeVersion=1.0.0-SNAPSHOT': you must
> specify a valid lifecycle phase, or a goal in the format plugin:goal
> or pluginGroupId:pluginArtifactId:pluginVersion:goal
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: < 1 second
> [INFO] Finished at: Mon Nov 23 20:11:27 GMT+00:01 2009
> [INFO] Final Memory: 1M/4M
> [INFO]
> ------------------------------------------------------------------------
>
> I’ve tried some variations, but to no avail... Before doing a deep
> dive and getting three degrees away from my original goal just wanted
> to check if folks had a quick pointer on this.
>
> Note – Using Maven 2.0.6 and Magnolia EE 4.1.1
>
> Thanks!
>
> Mit freundlichen Grüssen,
> Kind regards
>
> Abdul Nabi
> Technical Architect
>
> frog design europe gmbh
> Kalkofenstr. 51
> 71083 Herrenberg
>
>
>
> ______________________________________________________________________
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> ----------------------------------------------------------------

Issue with creating a custom module skeleton using a Maven Archetype

2009-11-23T12:22:10Z

Issue with creating a custom module skeleton using a Maven Archetype Hello All,

Hopefully a simple/stupid/newbie question (but also a good first start at using the user list)...

I’m ready to create my module and have tried the command from the “Module QuickStart” Wiki section -
mvn org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create -DarchetypeGroupId=info.magnolia \
   -DarchetypeArtifactId=maven-archetype-magnolia-module \
   -DarchetypeVersion=1.0 \
   -DremoteRepositories=http://maven.magnolia.info/m2 \
  -DgroupId=com.foo.bar \
   -DartifactId=my-module

And from the excerise guide -
mvn archetype:create -DarchetypeGroupId=info.magnolia \
    -DarchetypeArtifactId=maven-archetype-magnolia-module \
    -DarchetypeVersion=1.0.0-SNAPSHOT \
    -DgroupId=com.foo.bar \
    -DartifactId=my-module \
    -DremoteRepositories=http://svn.magnolia.info/maven/snapshots

And in both cases get -
[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Invalid task 'DarchetypeVersion=1.0.0-SNAPSHOT': you must specify a valid lifecycle phase, or a goal in the format plugin:goal or pluginGroupId:pluginArtifactId:pluginVersion:goal
[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Mon Nov 23 20:11:27 GMT+00:01 2009
[INFO] Final Memory: 1M/4M
[INFO] ------------------------------------------------------------------------

I’ve tried some variations, but to no avail... Before doing a deep dive and getting three degrees away from my original goal just wanted to check if folks had a quick pointer on this.

Note – Using Maven 2.0.6 and Magnolia EE 4.1.1

Thanks!

Mit freundlichen Grüssen,
Kind regards

Abdul Nabi
Technical Architect

frog design europe gmbh
Kalkofenstr. 51
71083 Herrenberg

Re: Re: Little bugs with data module.

2009-11-23T10:00:16Z

On Mon, 2009-11-23 at 17:16 +0100, Danilo Ghirardelli wrote:
> Issue opened (MGNLDATA-92) for the "edit with nothing selected" point,
> the other part is just mentioned.

Thanks.

> > As for the other things you mentioned ... the anonymous user access is
> > already logged as issue by yourself
>
> Yes, I forgot to mention. Someone just told me that I should have asked
> here first and then open the bug. I just changed the steps hoping the
> process is still correct... :-)

It's more of a guidance rather then a rule ... if you are sure that
something is a bug and know to which subproject it belongs, you can log
it directly. If you are not sure or if you want to start discussion
about possible solution for the issue, or if you feel that nothing
happened with the issue in the long time even tho there is a patch or it
is easy to solve, then here (or in the dev list) is the place to start
such a discussion.

cheers,
Jan

>
> Regards, Danilo.
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> ----------------------------------------------------------------

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

Re: Login after backup restore

2009-11-23T09:56:12Z

On Mon, 2009-11-23 at 18:07 +0100, Sebastian Schuon wrote:
> Hi Jan,
> thanks for your quick reply. I suspect indexes being "repositories
> \magnolia\workspaces\*\index" right? I've deleted them and they get

yes that's what I meant.

> rebuild, but no luck logging in... do you have any other suggestion?

hmm, that is strange. I have had a problem few times and re-indexing
always made it go away (the issue is caused by the fact that indexes are
generated asynchronously and do not stop the shutdown, so after the
restore they might not be finished yet when the main restore thread
already initiated shutdown).

The other things we can look for:
- were there any errors in the log files from startup?
- any errors during the restore?

you might want to post your log files to pastebin.com or similar service
and post the links to them here so we can have a look.

... more thoughts:
- the DB schema into which you restored the instance was clean right?
- the restore was made into exactly same version of Magnolia as the one
in which the backup was made?

- if nothing else helps, you might want to follow the guide on wiki on
how to reset superuser password.

Cheers,
Jan

> Thanks,
> Sebastian
>
> On Mon, Nov 23, 2009 at 4:35 PM, Jan Haderka
> <jan.haderka@...> wrote:
>
> Shutdown, delete indexes from all workspaces, and startup
> again. Should
> be ok then.
> HTH,
> Jan
>
>
>
> On Mon, 2009-11-23 at 16:29 +0100, Sebastian Schuon wrote:
> > Hi all,
> > I use mysql as a repository to magnolia. Now I tried to
> update an
> > older installation by simply updating the database. I am now
> puzzled,
> > that I can't login anymore. Since I can login into the newer
> > installation, I am quite positive that the password is
> correct. Can
> > anyone give me pointers what debug output might help?
> > Best,
> > Sebastian
>
>
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to:
> <user-list-unsubscribe@...>
> ----------------------------------------------------------------
>
>
>
>

Re: Re: custom 301 error message -- moved permanently

2009-11-23T09:52:52Z

23 nov 2009 kl. 08.52 skrev Matteo Pelucco:

>
> Åke Argéus ha scritto:
>> The way we handled this was making a custom virtualURIFilter that handles responses of the type moved: as well as redirect: and forward:.
>> This opened up the whole power of things like regexp-virtualurimappings.
>
> Oh, yes, it is a nice and powerful thing.
> But how can you handle the response within a virtual uri mapping?
> A "standard" virtual uri mapping simply redirect towards an internal page...
>
> The steps I miss are:
>
> 1) How can I retrieve the response inside a virtual uri mapping?
> 2) Is it safe to close the response (after having set the right header infos) within a virtual uri mapping?

Well. In the virtualURIfilter you can most certaintly do whatever you want with the response, and it has worked for us to send a 301 instead of 302 if the virtualurimapping returns moved; instead of redirect:.

At least for now we have no cases where we are really interested in checking anything in the request in our virtualurimappings though it has crossed my mind that we might end up there.

Not sure what the best way to do that is though. It's quite possible to extend the virtualurifilter even further and add the ability to load a special customized version of virtualurimapping that takes a request in it's active methods, and when looping though all the existing virtualurimappings you can just do an instanceof to check for this special class of virtualurimapping and act accordingly. This is a bigger reimplementation of the virtualurifilter, but not impossibly big, and shouldn't break a lot of things. You should still try to stay within the basic style and framework of the existing virualurifilter and could thereby keep the old functions while extending it with your own style of virtualurimappings and possible response-prefixes.

VirtualUrimappings could be one of the most powerful features in magnolia, and it's very flexible, and isn't impossible to extend, though I've thought of submitting a patch to make it more extendable or powerful.

/Åke

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

Re: Login after backup restore

2009-11-23T09:07:36Z

Hi Jan,

thanks for your quick reply. I suspect indexes being "repositories\magnolia\workspaces\*\index" right? I've deleted them and they get rebuild, but no luck logging in... do you have any other suggestion?

Thanks,

Sebastian

On Mon, Nov 23, 2009 at 4:35 PM, Jan Haderka <jan.haderka@...> wrote:

Shutdown, delete indexes from all workspaces, and startup again. Should
be ok then.
HTH,
Jan

On Mon, 2009-11-23 at 16:29 +0100, Sebastian Schuon wrote:
> Hi all,
> I use mysql as a repository to magnolia. Now I tried to update an
> older installation by simply updating the database. I am now puzzled,
> that I can't login anymore. Since I can login into the newer
> installation, I am quite positive that the password is correct. Can
> anyone give me pointers what debug output might help?
> Best,
> Sebastian

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

Re: how content2bean resolves classes

2009-11-23T08:28:56Z

ahhh, thanks. the missing link.

regards,

Ernst

2009/11/23 Jan Haderka <jan.haderka@...>:

>
> Hi Ernst,
> there are 2 other places where it looks for the impl classes:
> mgnl-beans.properties file in the magnolia-core.jar
> and modules descriptors (each module can add the mapping in its
> properties section), which is what for example STKdoes ...
>
> <properties>
> <property>
> <name>info.magnolia.module.templatingkit.style.Theme</name>
> <value>info.magnolia.module.templatingkit.style.ThemeImpl</value>
> </property>
> <property>
> <name>info.magnolia.module.templatingkit.sites.SiteManager</name>
>
> <value>info.magnolia.module.templatingkit.sites.STKSiteManager</value>
> </property>
> <property>
>
> <name>info.magnolia.module.templatingkit.beanmerger.BeanMerger</name>
>
> <value>info.magnolia.module.templatingkit.beanmerger.STKBeanMerger</value>
> </property>
> <property>
>
> <name>info.magnolia.module.templatingkit.categorization.CategorizationSupport</name>
>
> <value>info.magnolia.module.templatingkit.categorization.STKCategorizationSupport</value>
> </property>
> </properties>
>
> so you can do the same to associate any interface with the default impl.
> You can also associate path with the implementation class.
> HTH,
> Jan
>
>
>
> On Mon, 2009-11-23 at 15:43 +0100, Ernst Bunders wrote:
>> hello
>>
>> I am trying to understand how the content2bean process picks an
>> implmentation class if there is no class property in the relevant
>> content node.
>> To be specific, i am looking at the enhanced templating kit imaging
>> configuration.
>>
>> in config/modules/standard-templating-kit/themes/pop/imaging/variations
>> there is a whole list of imaging varations, that somehow must use an
>> implementation of the interface Variation. Yet non of these nodes have
>> a class property.
>> The same applies for the rule property of type VariationRule. no class
>> property anywhere.
>>
>> So: there must be a mechanism for registering default implementations
>> for interfaces. Can anybody tell me how this works?
>>
>> thanks,
>>
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> ----------------------------------------------------------------
>
>

--
Ernst bunders
Ontwikkelaar VPRO

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

Re: Re: Little bugs with data module.

2009-11-23T08:16:35Z

Issue opened (MGNLDATA-92) for the "edit with nothing selected" point,
the other part is just mentioned.

> As for the other things you mentioned ... the anonymous user access is
> already logged as issue by yourself

Yes, I forgot to mention. Someone just told me that I should have asked
here first and then open the bug. I just changed the steps hoping the
process is still correct... :-)

Regards, Danilo.

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

Re: Login after backup restore

2009-11-23T07:35:25Z

Shutdown, delete indexes from all workspaces, and startup again. Should
be ok then.
HTH,
Jan

On Mon, 2009-11-23 at 16:29 +0100, Sebastian Schuon wrote:
> Hi all,
> I use mysql as a repository to magnolia. Now I tried to update an
> older installation by simply updating the database. I am now puzzled,
> that I can't login anymore. Since I can login into the newer
> installation, I am quite positive that the password is correct. Can
> anyone give me pointers what debug output might help?
> Best,
> Sebastian

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

Login after backup restore

2009-11-23T07:29:23Z

Hi all,

I use mysql as a repository to magnolia. Now I tried to update an older installation by simply updating the database. I am now puzzled, that I can't login anymore. Since I can login into the newer installation, I am quite positive that the password is correct. Can anyone give me pointers what debug output might help?

Best,

Sebastian

Re: how content2bean resolves classes

2009-11-23T07:22:49Z

Hi Ernst,
there are 2 other places where it looks for the impl classes:
mgnl-beans.properties file in the magnolia-core.jar
and modules descriptors (each module can add the mapping in its
properties section), which is what for example STKdoes ...

<properties>
<property>
<name>info.magnolia.module.templatingkit.style.Theme</name>
<value>info.magnolia.module.templatingkit.style.ThemeImpl</value>
</property>
<property>
<name>info.magnolia.module.templatingkit.sites.SiteManager</name>

<value>info.magnolia.module.templatingkit.sites.STKSiteManager</value>
</property>
<property>

<name>info.magnolia.module.templatingkit.beanmerger.BeanMerger</name>

<value>info.magnolia.module.templatingkit.beanmerger.STKBeanMerger</value>
</property>
<property>

<name>info.magnolia.module.templatingkit.categorization.CategorizationSupport</name>

<value>info.magnolia.module.templatingkit.categorization.STKCategorizationSupport</value>
</property>
</properties>

so you can do the same to associate any interface with the default impl.
You can also associate path with the implementation class.
HTH,
Jan

On Mon, 2009-11-23 at 15:43 +0100, Ernst Bunders wrote:

> hello
>
> I am trying to understand how the content2bean process picks an
> implmentation class if there is no class property in the relevant
> content node.
> To be specific, i am looking at the enhanced templating kit imaging
> configuration.
>
> in config/modules/standard-templating-kit/themes/pop/imaging/variations
> there is a whole list of imaging varations, that somehow must use an
> implementation of the interface Variation. Yet non of these nodes have
> a class property.
> The same applies for the rule property of type VariationRule. no class
> property anywhere.
>
> So: there must be a mechanism for registering default implementations
> for interfaces. Can anybody tell me how this works?
>
> thanks,
>

RE: Little bugs with data module.

2009-11-23T07:15:28Z

Hello Danilo,

The public demo does not have the latest version of the data module. In the newest version (still 1.4-SNAPSHOT now) you can create nested or hierarchical types. That is not possible in the demo, so that is probably still version 1.3.2. (http://demoauthor.magnolia-cms.com/). The behaviour you describe is not appearing in 1.4.

Your second point is very valid. When you click the refresh-button in the menu at the bottom, the 'Edit item' button remains being enabled, without an item selected. In both versions 1.3.2 and 1.4-snapshot it seems to remove all items from the tree when you save the empty dialog you get. This seems indeed a major bug. It looks like the rootpath of the item type is changed even (check the JCR-browser after this unlucky save)! Can you report that in the jira? (http://jira.magnolia-cms.com/)

Your last point you already made in http://jira.magnolia-cms.com/browse/MGNLDATA-87. I supported your point of view there.

Bye, Bert

> -----Original Message-----
> From: user-list-owner@... [mailto:user-list-
> owner@...] On Behalf Of Danilo Ghirardelli
> Sent: maandag 23 november 2009 15:42
> To: Magnolia User-List
> Subject: [magnolia-user] Little bugs with data module.
>
>
> Even in the new release of the data module there are still a couple of
> thing I don't get...
> After I select any of the items in a tree, it seems impossible to
> create
> a new item (button is disabled), even if I de-select the item or click
> the "refresh" button lower right. The only option is to re-click on the
> tree in the left menu. Try yourself with the "Category" data tree in
> the
> public demo, click (single click is enough, just to select) on any of
> the categories and then try create a new one. Is there any reason for
> this behaviour?
> By the way, if I try to click "edit" without anything selected and I
> save it, every other data of the tree just disapperas, and the repo
> seems not really happy...
>
> The other strange behaviour is that the data module by default has no
> access granted to the anonymous role, not even the read only access
> that
> is granted for website and dms repositories. Is there any reason for
> this?
>
> Regards, Danilo.
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> ----------------------------------------------------------------

Re: Re: Little bugs with data module.

2009-11-23T07:14:17Z

On Mon, 2009-11-23 at 16:00 +0100, Danilo Ghirardelli wrote:
> > the categories and then try create a new one. Is there any reason for
> > this behaviour?
>
> Ops, I just noticed that the right click menu is correct, just the
> bottom one is wrong. I suppose it's a bug then.

yep, jira it please ... if you can come up with a patch it would be even
better.

As for the other things you mentioned ... the anonymous user access is
already logged as issue by yourself
and the edit button should be grayed out when there is nothing selected
to edit same way as the "open page" button behaves in the website (so
please log this one as well).
Cheers,

Jan

>
> Regards, Danilo.
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <user-list-unsubscribe@...>
> ----------------------------------------------------------------

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

Re: Little bugs with data module.

2009-11-23T07:00:28Z

> the categories and then try create a new one. Is there any reason for
> this behaviour?

Ops, I just noticed that the right click menu is correct, just the
bottom one is wrong. I suppose it's a bug then.

Regards, Danilo.

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

how content2bean resolves classes

2009-11-23T06:43:39Z

hello

I am trying to understand how the content2bean process picks an
implmentation class if there is no class property in the relevant
content node.
To be specific, i am looking at the enhanced templating kit imaging
configuration.

in config/modules/standard-templating-kit/themes/pop/imaging/variations
there is a whole list of imaging varations, that somehow must use an
implementation of the interface Variation. Yet non of these nodes have
a class property.
The same applies for the rule property of type VariationRule. no class
property anywhere.

So: there must be a mechanism for registering default implementations
for interfaces. Can anybody tell me how this works?

thanks,

--
Ernst bunders
Ontwikkelaar VPRO

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

Little bugs with data module.

2009-11-23T06:41:59Z

Even in the new release of the data module there are still a couple of
thing I don't get...
After I select any of the items in a tree, it seems impossible to create
a new item (button is disabled), even if I de-select the item or click
the "refresh" button lower right. The only option is to re-click on the
tree in the left menu. Try yourself with the "Category" data tree in the
public demo, click (single click is enough, just to select) on any of
the categories and then try create a new one. Is there any reason for
this behaviour?
By the way, if I try to click "edit" without anything selected and I
save it, every other data of the tree just disapperas, and the repo
seems not really happy...

The other strange behaviour is that the data module by default has no
access granted to the anonymous role, not even the read only access that
is granted for website and dms repositories. Is there any reason for this?

Regards, Danilo.

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

Is there something special about mgnl:resource?

2009-11-23T06:24:02Z

Dear Magnolians

I've got the following SQL query, which I am testing in the "JCR Queries" tool on the dms repository:

select * from mgnl:resource where jcr:path like '/path/to/some/folder/%' and ((width = '400' and height <= '300') or (width <= '400' and height = '300'))

When I set the "Result Item Type" to "nt:base", the query returns the dms mgnl:contentnode which contains the mgnl:resource node that matches the required width and height. However, when I set the "Result Item Type" to mgnl:resource, I don't get anything! The same thing happens when I use the path as the sole criteria.

Therefore I must assume that the Magnolia query mechanism does not really work for mgnl:resource nodes, correct? Is this intentionally? What's the reason for this and is there a workaround?

Thanks!
-Will

P.S.: This is on Magnolia 4.1.1

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <user-list-unsubscribe@...>
----------------------------------------------------------------

Re: Problem with templates

2009-11-23T01:53:33Z

Tx a lot but ... i knew ... however being a CE I have no access to update scripts and follo the other instructions:

The update35to36 script is currently only available for licensed users of Magnolia Enterprise Edition using Jackrabbit. If you have no license, you'll have to:

Export all your data, from all workspaces. Check the backup scripts provided on the wiki for a convenient way of performing this. (Do not forget to customize the scripts to add other workspaces if needed)
Import it in a fresh 3.6 instance.
Restart the webapp in order to have the update mechanism applied on your configuration.

hence I exported from the 3.0.1 and imported in fresh 4.1.1 as suggested (unless there are further steps in moving to 4.1.1)

As for the

If you can not use the updatenodetypes and/or update35to36 scripts, here are some details on how to achieve similar functionality:

Nodetypes definitions

The Magnolia node types have changed: mgnl:content, mgnl:contentNode, mgnl:metaData and other module specific node types now have mix:referenceable has a supertype (along with nt:hierarchyNode as before); mgnl:metaData should not have mix:versionable as a supertype anymore.

not fully sure about what to do but exporting template definition it seems everything ok (and congruent with the template dcefinition from the samples) ...

hence I'm a bit stuck ...

xml follows just in case it helps understanding better

<sv:node sv:name="mytemplate">
    <sv:property sv:name="jcr:primaryType" sv:type="Name">
      <sv:value>mgnl:contentNode</sv:value>
    </sv:property>
    <sv:property sv:name="jcr:mixinTypes" sv:type="Name">
      <sv:value>mix:lockable</sv:value>
    </sv:property>
    <sv:property sv:name="jcr:uuid" sv:type="String">
      <sv:value>7402ba24-106b-48f3-9555-c3650ef43abc</sv:value>
    </sv:property>
    <sv:property sv:name="name" sv:type="String">
      <sv:value>mytemplate</sv:value>
    </sv:property>
    <sv:property sv:name="templatePath" sv:type="String">
      <sv:value>/templates/jsp/mytemplates/soci/main.jsp</sv:value>
    </sv:property>
    <sv:property sv:name="title" sv:type="String">
      <sv:value>mytemplate</sv:value>
    </sv:property>
    <sv:property sv:name="type" sv:type="String">
      <sv:value>jsp</sv:value>
    </sv:property>
    <sv:property sv:name="visible" sv:type="String">
      <sv:value>true</sv:value>
    </sv:property>
    <sv:node sv:name="MetaData">
      <sv:property sv:name="jcr:primaryType" sv:type="Name">
        <sv:value>mgnl:metaData</sv:value>
      </sv:property>
      <sv:property sv:name="mgnl:authorid" sv:type="String">
        <sv:value>superuser</sv:value>
      </sv:property>
      <sv:property sv:name="mgnl:creationdate" sv:type="Date">
        <sv:value>2009-11-11T16:19:32.859+01:00</sv:value>
      </sv:property>
      <sv:property sv:name="mgnl:lastmodified" sv:type="Date">
        <sv:value>2009-11-12T10:06:52.178+01:00</sv:value>
      </sv:property>
    </sv:node>
    <sv:node sv:name="subTemplates">
      <sv:property sv:name="jcr:primaryType" sv:type="Name">
        <sv:value>mgnl:contentNode</sv:value>
      </sv:property>
      <sv:property sv:name="jcr:mixinTypes" sv:type="Name">
        <sv:value>mix:lockable</sv:value>
      </sv:property>
      <sv:property sv:name="jcr:uuid" sv:type="String">
        <sv:value>a64c5cba-8f0b-448b-8e74-c7494f877ba4</sv:value>
      </sv:property>
      <sv:node sv:name="MetaData">
        <sv:property sv:name="jcr:primaryType" sv:type="Name">
          <sv:value>mgnl:metaData</sv:value>
        </sv:property>
        <sv:property sv:name="mgnl:authorid" sv:type="String">
          <sv:value>superuser</sv:value>
        </sv:property>
        <sv:property sv:name="mgnl:creationdate" sv:type="Date">
          <sv:value>2009-11-11T16:22:05.535+01:00</sv:value>
        </sv:property>
        <sv:property sv:name="mgnl:lastmodified" sv:type="Date">
          <sv:value>2009-11-11T16:23:12.348+01:00</sv:value>
        </sv:property>
      </sv:node>
      <sv:node sv:name="edit">
        <sv:property sv:name="jcr:primaryType" sv:type="Name">
          <sv:value>mgnl:contentNode</sv:value>
        </sv:property>
        <sv:property sv:name="jcr:mixinTypes" sv:type="Name">
          <sv:value>mix:lockable</sv:value>
        </sv:property>
        <sv:property sv:name="jcr:uuid" sv:type="String">
          <sv:value>371de8d2-4735-43c8-9a70-3a3be29eab7d</sv:value>
        </sv:property>
        <sv:property sv:name="extension" sv:type="String">
          <sv:value>edit</sv:value>
        </sv:property>
        <sv:property sv:name="templatePath" sv:type="String">
          <sv:value>/templates/jsp/mytemplate/soci/edit.jsp</sv:value>
        </sv:property>
        <sv:property sv:name="type" sv:type="String">
          <sv:value>jsp</sv:value>
        </sv:property>
        <sv:node sv:name="MetaData">
          <sv:property sv:name="jcr:primaryType" sv:type="Name">
            <sv:value>mgnl:metaData</sv:value>
          </sv:property>
          <sv:property sv:name="mgnl:authorid" sv:type="String">
            <sv:value>superuser</sv:value>
          </sv:property>
          <sv:property sv:name="mgnl:creationdate" sv:type="Date">
            <sv:value>2009-11-11T16:23:03.257+01:00</sv:value>
          </sv:property>
          <sv:property sv:name="mgnl:lastmodified" sv:type="Date">
            <sv:value>2009-11-11T16:23:58.293+01:00</sv:value>
          </sv:property>
        </sv:node>
      </sv:node>
    </sv:node>
</sv:node>

Jan Haderka wrote:

The node types structure changed between 3.5.8 and 3.6 ... read the
release notes for version 3.6 to find out how to fix the problem.

HTH,
Jan

On Mon, 2009-11-23 at 09:38 +0100, lgilardoni61@... wrote:

Hi. I' setting up a Magnolia4.1 mvoing from a 3.0.1 (CE) 

Loaded  a set of templates (jsp) from previous version, and loaded
website content. All seems to be working fine, but whenever Magnolia
start I get a number of errors (2 for any of the defined templates) 
as from following stack trace. 

Triple-checked template/dialogs/para definitions and everything seems
ok (and also the site is running fine),but fear problems somewhere
else. 

Anyone any idea? 

Tx 

Luca 

stacktrace follows 

2009-11-19 10:14:16,958 ERROR
info.magnolia.cms.core.DefaultContent             : Exception caught 
javax.jcr.UnsupportedRepositoryOperationException 
       at
org.apache.jackrabbit.core.NodeImpl.getUUID(NodeImpl.java:2965) 
       at
info.magnolia.cms.core.DefaultContent.getUUID(DefaultContent.java:837) 
       at
info.magnolia.cms.util.LazyContentWrapper.<init>(LazyContentWrapper.java:78) 
       at
info.magnolia.cms.util.SystemContentWrapper.<init>(SystemContentWrapper.java:62) 
       at
info.magnolia.content2bean.impl.Content2BeanTransformerImpl.setProperty(Content2BeanTransformerImpl.java:203) 
       at
info.magnolia.content2bean.impl.Content2BeanProcessorImpl.setProperties(Content2BeanProcessorImpl.java:210) 
       at
info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toBean(Content2BeanProcessorImpl.java:101) 
       at
info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toMap(Content2BeanProcessorImpl.java:167) 
       at
info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toBean(Content2BeanProcessorImpl.java:95) 
       at
info.magnolia.content2bean.impl.Content2BeanProcessorImpl.toBean(Content2BeanProcessorImpl.java:69) 
       at
info.magnolia.content2bean.Content2BeanUtil.toBean(Content2BeanUtil.java:151) 
       at
info.magnolia.content2bean.Content2BeanUtil.toBean(Content2BeanUtil.java:137) 
       at
info.magnolia.module.templating.TemplateManager.addTemplatesToCache(TemplateManager.java:160) 
       at
info.magnolia.module.templating.TemplateManager.cacheContent(TemplateManager.java:183) 
       at
info.magnolia.module.templating.TemplateManager.onRegister(TemplateManager.java:81) 
       at
info.magnolia.cms.beans.config.ObservedManager.register(ObservedManager.java:85) 
       at
info.magnolia.module.ModuleLifecycleContextImpl.initEntry(ModuleLifecycleContextImpl.java:93) 
       at
info.magnolia.module.ModuleLifecycleContextImpl.start(ModuleLifecycleContextImpl.java:85) 
       at
info.magnolia.module.ModuleManagerImpl.startModules(ModuleManagerImpl.java:355) 
       at
info.magnolia.module.ui.ModuleManagerWebUI.onStartup(ModuleManagerWebUI.java:80) 
       at
info.magnolia.cms.beans.config.ConfigLoader.load(ConfigLoader.java:108) 
       at info.magnolia.cms.servlets.MgnlServletContextListener
$2.exec(MgnlServletContextListener.java:184) 
       at
info.magnolia.context.MgnlContext.doInSystemContext(MgnlContext.java:377) 
       at
info.magnolia.cms.servlets.MgnlServletContextListener.startServer(MgnlServletContextListener.java:181) 
       at
info.magnolia.cms.servlets.MgnlServletContextListener.contextInitialized(MgnlServletContextListener.java:177) 
       at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3764) 
       at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4216) 
       at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760) 
       at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740) 
       at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544) 
       at
org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:626) 
       at
org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:553) 
       at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:488) 
       at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1150) 
       at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) 
       at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120) 
       at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022) 
       at
org.apache.catalina.core.StandardHost.start(StandardHost.java:736) 
       at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) 
       at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) 
       at
org.apache.catalina.core.StandardService.start(StandardService.java:448) 
       at
org.apache.catalina.core.StandardServer.start(StandardServer.java:700) 
       at
org.apache.catalina.startup.Catalina.start(Catalina.java:552) 
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
       at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 
       at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 
       at java.lang.reflect.Method.invoke(Method.java:585) 
       at
org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) 
       at
org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) 





______________________________________________________________________
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: user-list-unsubscribe@...
----------------------------------------------------------------



----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: user-list-unsubscribe@...
----------------------------------------------------------------