Yes, that was what I was expecting. Comparing the whole box of frogs is messy, and ID would be much simpler. Obviously the software keeps track of post author ID and current user ID, so it's just a question of if those variables can be made available directly in the template.Yup, comparing user ID would be ideal and safer than comparing those strings returned by template var. :/
Getting {postrow.POSTER_ID} in the template is a piece of cake. I have already done that. But, there doesn't appear to be any way of getting {CURRENT_USER_ID} in the template. Obviously I could do a core hack and make it available, but I'd prefer not to.
Statistics: Posted by Gumboots — Sun Aug 18, 2024 9:04 pm