So I had written a custom snippet called "changePassword" before the "ChangePassword" snippet was added to the Login package. My snippet got whacked by the upgrade :-(
First question: it probably didn’t help that I had put my snippet in the Login folder... but if I had put it somewhere else, would it still have been whacked? Or would the installation have failed with an error?
The rest of my questions are about the ChangePassword snippet. My original snippet had this logic: IF the password has been successfully changed, display a success message (and a link back to the main page). ELSE display the change password form.
I tried recreating this logic but didn’t have great luck. After studying the snippet code I figured out how to reconcile my field names, put in the right placeholders for error messages, etc. I specified a successMessage in the snippet call, but figured out that this doesn’t get set unless I also set reloadOnSuccess=`0`. (Found that a bit odd, but maybe that’s just because there isn’t a doc page for this snippet yet and I don’t fully grok the logic).
I tried to do something like this:
[[+logcp.successMessage:notempty=`[[+logcp.successMessage]]<p><a>Return to Account Management Page</a></p>`]]
But that wasn’t working. If I put [[+logcp.successMessage]] by itself it works okay (displays on success), but I’d like to display that return link only on success. Hmm, I suppose I could try putting it right in the successMessage string, but that doesn’t feel as right to me.
Am I just using the filters wrong? Is there a way I can do this (and hopefully also add back in my original logic, which was to not display the form when there was success).
☆ A M B ☆
