MODx Parsing bug?

- 183 Posts
mikrobi Reply #1, 13 years, 2 months ago
Hi,

when I use this code in a chunk (form for updating a profile from http://rtfm.modx.com/display/ADDON/Login.UpdateProfile):
```
[[+login.update_success:if=`[[+login.update_success]]`:is=`1`:then=`[[%login.profile_updated? &namespace=`login` &topic=`updateprofile`]]`]]
```
I get the following output in the front (only this and nothing else from the chunk):
```
`:is=`1`:then=`[[%login.profile_updated
```
and MODx stops rendering the rest of the chunk.

When using
```
[[+login.update_success:if=`[[+login.update_success]]`:is=`1`:then=`Hardcoded text without using lexicon`]]
```
everything works fine.

The MODx parser seems to have some problem with this syntax?

Some time ago I’ve posted a bug (which has been rejected) which may be related to this: http://bugs.modx.com/issues/2917

Or am I doing something wrong???

Thanks,
Jakob
Add-On to easily manage your multilingual sites: Babel
- ☆ A M B ☆
- 3,141 Posts
Mark Hamstra Reply #2, 13 years, 2 months ago
Somewhat easier:
```
[[+login.update_success:eq=`1`:then=`blabla`]]
```
Easiest:
```
[[+login.update_success:notempty=`blabla`]]
```
I also had issues calling a snippet with parameters in the output filter, however thought I was just being goofy so didn’t spend much time checking it.

Can you confirm the problem also exists with the above syntax (which is the same, but slightly easier) and if so give us your environment info?
Mark Hamstra • Developer spending his days working on Premium Extras and a MODX Site Dashboard with the ability to remotely upgrade MODX and extras to make the MODX world a little better.

Tweet me @mark_hamstra, check my infrequent blog at markhamstra.com, my slightly more frequent ramblings at MODX.today or see code at Github.