Publisher is EE6 compatible, but it does not support the Fluid field. Please do not contact asking when support will be available.

If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.

Ticket: {csm:error} doesn’t seem to work?

Status Resolved
Add-on / Version Custom System Messages
Severity Trivial
EE Version

Garrett Henderson

Apr 26, 2012

Hi Brian. Great addon. Thank you for it.

I use a single template and a series of conditionals to output the proper HTML, much like your example on pastie (which by the way is down, perhaps you could put that somewhere else? I just happen to have an old tab opened with it). Anyway, csm:error doesn’t seem to work:

{if csm:error == true}
error
{if:else}
no error
{/if}

and

{if csm:error == false}
error
{if:else}
no error
{/if}

always outputs: “error.” it always evaluates to true. Am I missing something?

#1

BoldMinded (Brian)

Apr 26, 2012

Hi Garrett, I assume you are using 2.4? What does your settings screen look like? Also, did you try to quote it? e.g. {if “{csm:error}” == FALSE}

#2

Garrett Henderson

Apr 26, 2012

Ah, now see you put the TRUE or FALSE in all caps, and now when I quote it and use TRUE or FALSE it appears to work. The pastie example had “true” and “false” so even when I had tried quoting it, it wasn’t working. I don’t know enough about the inner workings of EE to know why that is. Is TRUE and FALSE some kind of constant that EE recognizes as boolean true or false, similar to how I can use AND or && in a conditional? I’m speculating…

#3

Garrett Henderson

Apr 26, 2012

A quick followup…why is an invalid activation request not considered an error? csm:error evaluates to true in that case.

#4

BoldMinded (Brian)

Apr 26, 2012

Garrett, can you send me an email at litzinger at gmail? I have a new build that might the activation request. Basically EE’s internals default to a show_message() method in many places, not show_user_error(), and only show_error() sends that error response. show_user_error() actually calls show_message() and contains that extra flag to signify what type of message to show, but they opt to go straight to the show_message() method in many places, thus that flag is not present. The build I have includes a work around that may work for you. I’ve had it ready to go for a couple weeks but was holding off on releasing it until I can confirm its the best fix… hopefully you can confirm that 😊

#5

BoldMinded (Brian)

Jun 14, 2012

I think this was resolved via another ticket.

Closing, have not heard a response. Please start a new ticket referencing this one if you’re still having issues.

Login to reply