Like button state (solved)

Hi Pawel,

your issue sounds like you didn't implement the user filter correctly. That could be a reason for the like behaving "globally". I don't see any user connection in the screenshots you've sent...

I have an addon in content record which determines if this content was already liked ( voted in my case) by current user. I have also the custom variable vote_state which switch the variant of vote icon from default to active based on the _voted addon status. The problem is that variable is outside the list of record and works globally on every member based on last iteration of loop (at least i think that is the case)

I see, that makes sense

Yeah, not exactly because it is not working correctly... But I'm not sure how to do it correctly so vote icon in every instance of content is changing independently based on _voted status.

Hello Pawel!

Did you try to include "user_id" as an input, and an "If" statement to distinguish between the users that have voted –and not voted– for each item?

Hi Leonor!
Thanks for reply.

Distinguishing is not a problem, I have an addon which determines if the auth user already voted or not. The problem is that I have a variable which is controlling the state of vote icon (active/default) and I don't know how to make this variable independent for every instance of the list. 

state variable is outside the content, getting the value from the last iteration of the loop and affecting the list as a whole.

Issue is solved. My mistake was that I was not aware at the time how I can create for an instance. For me it was cont.vote_state (where cont is the instance of list content)

thanks for this. I am assuming we can use this for a scenario where a user wants to "favorite" and save to their saved lists? Thanks

Yes It can be used that way