Symphony.

Thanks mate, I appreciate the flexibility :-)

You simply owe me one pint of beer. :-)

You'll be first on my beer list in Cologne in October!

Thanks. I put this on my To-Do list as well.

• Drink beer (bill: Nick)

@micheal-e You might want to ask for two or three glasses, because beer here in Cologne (we drink Kölsch) usually comes in glasses of 0.2 liters.

And there I was thinking it'd be a litre tankard like the Hofbrauhaus!

Living in Munich it's hard to imagine that "up there" they use those baby glasses. But I heard that the waiters are very fast in serving them, so it might be OK.

Yep, you have to put the beermat on top of your glass, otherwise the waiters will come again and again.

you have to put the beermat on top of your glass, otherwise the waiters will come again and again.

Sounds like Heaven!

I'll gladly volunteer my beermat to be folded up and put underneath a table leg to stop it rocking.

Now that is a good idea! :-)

Hi all,

is there an easy way to add the invalid-class to an outer div (div arround form and error message)?

I am a bit lost.

When should this be triggered? If any of the fields is invalid? In this case you only need to check for the event result. You are using the utility's form fields in your page (so you have set an event variable)? The following should work (but I have not tested it):

<div id="outer-div">
    <xsl:if test="boolean(/data/events/*[name()=$event]/@result='error')">
        <xsl:attribute name="class">
            <xsl:value-of select="$publish:invalid-class"/>
        </xsl:attribute>
    </xsl:if>
    ... (fields etc.)...
</div>

The example uses the classname of Members Forms. Of course you can use whatever classname you prefer.

Hi,

this is what I currently have:

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:exsl="http://exslt.org/common"
    xmlns:members="http://michael-eichelsdoerfer.de/xslt/members"
    extension-element-prefixes="exsl members">

<xsl:import href="members-forms/members.forms.xsl"/>

<xsl:template name="members-form-login">

    <xsl:variable name="event" select="'member-login-info'"/>

<div id="outer">
    <xsl:if test="boolean(/data/events/*[name()=$event]/@result='error')">
        <xsl:attribute name="class">
            <xsl:value-of select="$publish:invalid-class"/>
        </xsl:attribute>
    </xsl:if>

    <xsl:call-template name="members:validate">
        <xsl:with-param name="event" select="$event"/>
    </xsl:call-template>

    <form action="" method="post">
        <xsl:call-template name="members:input-identity">
            <xsl:with-param name="event" select="$event"/>
        </xsl:call-template>
        <xsl:call-template name="members:input-password">
            <xsl:with-param name="event" select="$event"/>
            <xsl:with-param name="mode" select="'login'"/>
        </xsl:call-template>
        <xsl:call-template name="members:input-submit">
            <xsl:with-param name="event" select="$event"/>
            <xsl:with-param name="name" select="'member-action[login]'"/>
        </xsl:call-template>
    </form>
</div>
</xsl:template>

</xsl:stylesheet>

which is not working. Is it because of the event variable? Or should I edit a totaly other area to get the outer div arround the form and validations messages?

ok,

<xsl:value-of select="$publish:invalid-class"/>

was unknown. Thanks!

Sorry, that should have been:

<xsl:value-of select="$members:invalid-class"/>

(I copied code from the wrong place, with a different namespace...)

So it's working now? Great.

Members Forms updated to version 1.0 on 20th of June 2011

Wonderful, works very well and easily extendable. Great educational resource for understanding symphony events as well.

However, I had small difficulties integrating it with ETM. Maybe some tiny example in readme (for newbies) worth writing.

Thanks a lot!

Yes, I could an integration guide to the README. I hope that I' ll find the time. (Probably not now, because I am at the Symposium 2011.)

Ah, so great. I hope someone documenting the event!!

I have a question: login form in side-bar and registration form in content area works together, however, duplicated ids appears, for example id="fields-email".

What is better strategy in this case, can it be done correctly?