Login documentation/examples

I'm running through the docs for the Login snippet, testing prior to using in a new site.

There are a fair few items which, although included in the docs, are very cryptic and not self-explanatory. For example, can anyone explain to me what the following means:

logoutMsg - Optional label message for logout action. If blank, will default to lexicon string for Logout.

(from http://rtfm.modx.com/extras/revo/login/login.login)

I have added "&logoutMsg=`Goodbye!`" to my snippet call, but don't see this text when I logout. This seems to be the only mention of this property in the docs and I can't find any examples of it use.

Thanks.

From the wording "optional label message for logout action" I would think that this would mean the text of the logout link.

Thanks sottwell for my fastest response by far!

Yes, that would sound like a reasonable assumption, but I have my logout link set up as described in the docs:

<a href="[[~6? &service=`logout`]]" title="Logout">Logout</a>

&logoutMsg doesn't change that.

I'm sure I'm just being daft or unimaginitive, but then I'm exactly what the docs are for...

If you visit the page that has the Login snippet on it while you're logged in, and you didn't override the &logoutTpl, then that should show you give you the "Goodbye!" message as logout link in your example.

Here's the relevant part of the default logout tpl

So you could use the [[+actionMsg]] placeholder in your tpl as well, and it would change according to your snippet's property.

It's always a good idea to use the default tpl as your custom tpl's code, make sure it works, then start modifying your custom tpl.

Mark, thanks for that, you were right. Sottwell, thanks for the tip.

As I was just saying to Bob Ray on a related thread about Login, my angst was caused in part by Chrome apparently not clearing out its cache (even with the Cache Killer addon enabled), so I was getting a stream of 'wrong' behaviour. Firefox seemed better, but didn't convince me completely. I ended up not getting the expected behaviour till I went home from work and opened the page on different computer!