Check usergroup of thread starters in threadbit

[addamroy]

Originally Posted by LifesGreatestGift

post me the conditional you are using exactly as is. or just post the contents of threadbit template in code tags.

I pasted the conditional exactly as you put it. Here's how I was using it

<!-- test usergroup check -->
<vb:if condition="is_member_of($bbuserinfo, 6)">
<vb:if condition="in_array(6, $group)">
style=""
</vb:if>
</vb:if>
<!-- test usergroup check -->

I'm testing this with usergroup 6 until I get it working then I would remove the first conditional, and then edit the second one accordingly.

I get the error when I try to save that.

If I do just this, it saves ok.

<!-- test usergroup check -->
<vb:if condition="is_member_of($bbuserinfo, 6)">
style=""
</vb:if>
<!-- test usergroup check -->

[LifesGreatestGift]

maybe try this, not sure why it would matter.

<vb:if condition="in_array('6', $group)">STUFF</vb:if>

and to be honest, it may be a bug in your vB version that was fixed in a later release.

[addamroy]

Hmm, you had it working in 4.1.12?

I'm running patch level 2 now, but there is a patch level 3 available that I haven't updated the forum with yet.

[LifesGreatestGift]

it works flawlessly in vb 4.2.0 pl3

[addamroy]

hmm.

Well thanks for all the help guys it's always awesome when everyone comes together like that. This thread will be here for 4.2.x users anyway lifesgreatest that's pretty awesome that you provided the plug-in to accomplish this.

Unfortunately my forum is so heavily customized and with various mods I'm always nervous about semi-major updates. ie 4.0 to 4.1 or 4.1 to 4.2 etc. Stuff breaks and I end up running around like a chicken with my head cut off on my test forum trying to make everything work again. lol, you know how it is.

If I ever figure out why it's working in 4.2 and not 4.1 I'll come back and let you guys know.

[addamroy]

lifesgreatest, if the reason it's not working in 4.1.12 is because of a bug, what file or files would you assume be causing this problem?

I might be able to submit a support ticket and get vbstaff to confirm it is in fact a bug.