Hi Luca

I know how that goes.
I take it you've got sample code on how to use PUR to share? That of course would be great. Looking forward to that.

Regards,
Will

On 21.05.2008, at 10:43, Vaudano Luca wrote:

Hi Will,

now I am very busy in a project :-( (the hard life of the programmer
:-) ) But I promise that this evening I will make a tar of all my
source code and tomorrow I will post you.

Ciao,
Luca

On Tue, May 20, 2008 at 10:04 PM, Will Scheidegger
<[email protected]> wrote:
Hi Luca

Sorry for the late reply. I thought I better have a look at PUR before I reply.... and unfortunately I cannot help turning the question arround:

-> What are the features of PUR?

- I searched the web for documentation
- I downloaded the source code and compiled the javadoc
- I looked at the docs of every class

Unfortunately without much success. So again: What are the features of PUR? Could you point me to some documentation on how to integrate these features?

Regards,
Will


On 24.04.2008, at 10:15, Vaudano Luca wrote:

Hi Will,

what is different from the features of the magnolia-PUR-module?
This module makes available a login mask, user validation, retrieve
password paragraph; and saves the user data in the JCR repository.
But I have a question about this module, if I have one author instance
and two public instance, the three JCR repositories after a user
registration could become not align.
By the way, if you are interesting, I made a module starting from
magnolia-PUR-module that saves the user data, using spring - hibernate
frameworks, in a centralized database.

Regards,
Luca

On Thu, Apr 24, 2008 at 7:30 AM, Will Scheidegger
<[email protected]> wrote:

Dear Magnolians

The subject has been discussed here several times, but there has yet to
be
found a good answer. See for instance:


http://www.mail-archive.com/search?q=custom+login&l=user-list%40magnolia.info

We therefore suggest a Magnolia extension that gives us flexible
alternatives when it comes to the login mask. In my opinion such a
"magnolia-module-login" should allow to define rules in the
configuration,
which get Magnolia to display different login masks depending on the URL
that was called, e.g.

- */magnoliaAuthor/.magnolia* -> standard Framemaker Magnolia login
mask

- http://customer_a.com/public/*-en.html -> display the magnolia page /public/cust_a/login-en.html (which of course should contain something
like
a login paragraph)

- http://customer_b.com/public/* -> display the magnolia page
/public/cust_b/login

What do you think:
Would this module be helpful for you too?
Would you need additional/different features?
Would you be interested in helping to develop it?
Has someone already developed something similar?
Are the Magnolia developers by any chance already working on something
similar for the next Magnolia release?

Cheers,
Will

----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------

Reply via email to