Joomla Extensions Club 20,483 posts

[Mr.Cat Moderator Mr.CatJoin date: December 2016Posts: 270Downloads:24Uploads:69 Thanks: 58 Thanked: 53 times in 50 posts]

#1072539

@thesdhotel

This is build in function of dustjs. You can access value of object by using syntax javascript.

You can see an example about it on dustjs site.

And we can’t use actual field name because it can’t help us to access the data of object.

• This reply was modified 7 years ago by  Mr.Cat.

---

Attachments:

1. 

Wisdom is not a product of schooling but of the lifelong attempt to acquire it.

[thesdhotel Friend thesdhotelJoin date: March 2017Posts: 90Downloads:25Uploads:1 Thanks: 31 Thanked: 22 times in 20 posts]

#1072651

Hello, I see, I made a mistake.

However, the issue that I described does exist. If you try to use dust.js helpers (http://www.dustjs.com/guides/dust-helpers/ – they have been added to Megafilter in the 1.10 update). If you try to use dust.js helpers in your layout template override for the product-item.php, they don’t work correctly when you use them for a custom field.

See screenshot example attached below. (I used this page to test/demo: http://www.dustjs.com/test/test.html?q=helpers)

It works correctly when the key doesn’t have a dot (for example "name"), but when you put a key with dots (for example "attr.ct1.value"), it doesn’t work.

Do you think this is a dust.js bug?

• This reply was modified 7 years ago by  thesdhotel.
• This reply was modified 7 years ago by  thesdhotel.

---

Attachments:

1. 

[Mr.Cat Moderator Mr.CatJoin date: December 2016Posts: 270Downloads:24Uploads:69 Thanks: 58 Thanked: 53 times in 50 posts]

#1072799

@thesdhotel,

You can try this one:

{#attr}
    {#tag}
        {@eq key=value value="3"}
            nice
        {:else}
            wow
        {/eq}
    {/tag}
{/attr}

You have to access object properties step by step.

Wisdom is not a product of schooling but of the lifelong attempt to acquire it.

[thesdhotel Friend thesdhotelJoin date: March 2017Posts: 90Downloads:25Uploads:1 Thanks: 31 Thanked: 22 times in 20 posts]

#1073095

Hey man, Just tried that but it didn’t work.

But I don’t think it’s your fault… Why? Because I tried it with {gt} and {gte} and it works correctly (even by writing the key all at once like "attr.ct1.value"). It only doesn’t work with {eq}.

So I think this is a Dust.js bug? When trying to access a object property inside another object, {eq} doesn’t seem to work, but the others like {gt} and {gte} etc. seem to work.

• This reply was modified 7 years ago by  thesdhotel.

[Mr.Cat Moderator Mr.CatJoin date: December 2016Posts: 270Downloads:24Uploads:69 Thanks: 58 Thanked: 53 times in 50 posts]

#1073253

@thesdhotel,

May be some thing is not consistent. You can report to dustjs team on github. I think you’ll get the good answer 🙂

Wisdom is not a product of schooling but of the lifelong attempt to acquire it.

[thesdhotel Friend thesdhotelJoin date: March 2017Posts: 90Downloads:25Uploads:1 Thanks: 31 Thanked: 22 times in 20 posts]

#1073356

Or maybe not… I see that they’re very inactive…

https://github.com/linkedin/dustjs/issues
https://github.com/linkedin/dustjs-helpers/issues

I’ll try 😀

[thesdhotel Friend thesdhotelJoin date: March 2017Posts: 90Downloads:25Uploads:1 Thanks: 31 Thanked: 22 times in 20 posts]

#1074692

@Mr. Cat
We have an answer…
https://github.com/linkedin/dustjs-helpers/issues/145

In your ctx value is an array. You’re trying to compare the values between a string and an array. Your ctx should be something like this:

{"attr":{"ct1":{"value":"Mick"}}}

and not this:

{"attr":{"ct1":{"value":["Mick"]}}}

So I think it’s something we need to fix in Megafilter? Is it possible for you to fix that if the array only contains one value, then don’t show the [parenthesis]?
If it contains multiple values then it should be an array, but if it doesn’t contain multiple values it should be a single value. Does that make sense?

[Mr.Cat Moderator Mr.CatJoin date: December 2016Posts: 270Downloads:24Uploads:69 Thanks: 58 Thanked: 53 times in 50 posts]

#1074711

@thesdhotel,

You can use this code. It works with single value.

{#attr}
      {#ct1}
      {#value}
          {@eq key=. value="Mick"}
              It should be true
          {:else}
              But it's false
          {/eq}
      {/value}
      {/ct1}
{/attr}

Your idea is possible, but we have to change a lot of code to check array or not. It’s gonna create unaware bugs. 🙁

• This reply was modified 7 years ago by  Mr.Cat.
• This reply was modified 7 years ago by  Mr.Cat.

Wisdom is not a product of schooling but of the lifelong attempt to acquire it.

1 user says Thank You to Mr.Cat for this useful post

1. thesdhotel

[thesdhotel Friend thesdhotelJoin date: March 2017Posts: 90Downloads:25Uploads:1 Thanks: 31 Thanked: 22 times in 20 posts]

#1074724

GENIUS!

It works!

Or even more simplified also works:

    {#attr.ct1.value}
              {@eq key=. value="Mick"}
                      It should be true
              {:else}
                  But it's false
              {/eq}
    {/attr.ct1.value}

Thanks, you’re the man!

• This reply was modified 7 years ago by  thesdhotel.

1 user says Thank You to thesdhotel for this useful post

1. Mr.Cat

[Author]

Posts