A small problem in the login.tpl that was solved

Author Message

Esben Maaløe

Monday 21 July 2003 9:41:12 am

I have an entry page showing the names of a bunch of designers. These designers are of course objects of a custom class I made....

Now when the user clicks a designer name, he get's a surprise ! He has to register or login to actually view the designer...

My approach is this:

{section show=fetch(user,current_user).is_logged_in}
{* CODE THAT SHOWS ALL THE SAUCY DESIGNER DETAILS*}
{section-else}
{include uri="design:user/login.tpl"}
{/section}

Clever am I not ? :)

Only one problem - The login page thinks that there has been issued a warning

the section: {section show=$User:warning.bad_login}

is shown

How can I deal with this ?

NEWSFLASH:
I nailed it myself - But having written the post I might as well share:

it seems that for some reason $User:warning.bad_login returns something that is evaluated as true - the cure is changing the line to:

{section show=and($User:warning.bad_login) }

(the same applies for the {section-else} )

------
login.tpl, bad_login, warning

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.