If/Else

[Teg]

Someone please guide me what I am doing wrong.

{if $[current_user.custom_field.name] == "House Points" && $[current_user.custom_field.value] != "0"} $[current_user.custom_field.value] {else} <a href="https://hwsoww.boards.net/board/5/sorting-ceremony">Get Sorted</a>{/if}

It' consistently puts the "Get Sorted" link, even though the number in the custom field value is over 1000.

[Kami]

Sept 3, 2023 11:28:27 GMT -8 Teg said:

Someone please guide me what I am doing wrong.

{if $[current_user.custom_field.name] == "House Points" && $[current_user.custom_field.value] != "0"} $[current_user.custom_field.value] {else} <a href="https://hwsoww.boards.net/board/5/sorting-ceremony">Get Sorted</a>{/if}

It' consistently puts the "Get Sorted" link, even though the number in the custom field value is over 1000.

You're using "current_user"; is this intentional? This would pull the custom field values of the account *viewing* the section, as opposed to the account to whom the section belongs.

[Teg]

I figured it out, forgot the for each

but, yes, it is intentional, it should only be for the current user who is viewing the page.

Sept 3, 2023 11:36:22 GMT -8 Kami said:

Sept 3, 2023 11:28:27 GMT -8 Teg said:

Someone please guide me what I am doing wrong.

{if $[current_user.custom_field.name] == "House Points" && $[current_user.custom_field.value] != "0"} $[current_user.custom_field.value] {else} <a href="https://hwsoww.boards.net/board/5/sorting-ceremony">Get Sorted</a>{/if}

It' consistently puts the "Get Sorted" link, even though the number in the custom field value is over 1000.

You're using "current_user"; is this intentional? This would pull the custom field values of the account *viewing* the section, as opposed to the account to whom the section belongs.

[Kami]

Sept 3, 2023 11:40:54 GMT -8 Teg said:

I figured it out, forgot the for each

but, yes, it is intentional, it should only be for the current user who is viewing the page.

Sept 3, 2023 11:36:22 GMT -8 Kami said:

You're using "current_user"; is this intentional? This would pull the custom field values of the account *viewing* the section, as opposed to the account to whom the section belongs.

ahh got it, foreach was gonna be my next question but i had (erroneously it seems) assumed you were only showing a snippet and already had it 😅 glad you got it sorted!

[Teg]

it has been a hot minute since i have done anything with pb, so i forgot lol thank you though.

I am curious, is there a way to write an if/else statement to say the following

If current user group name does not equal group1 group2 group3 or group4, then this happens?

Sept 3, 2023 12:36:06 GMT -8 Kami said:

Sept 3, 2023 11:40:54 GMT -8 Teg said:

I figured it out, forgot the for each

but, yes, it is intentional, it should only be for the current user who is viewing the page.

ahh got it, foreach was gonna be my next question but i had (erroneously it seems) assumed you were only showing a snippet and already had it 😅 glad you got it sorted!

[Kami]

Sept 4, 2023 10:47:01 GMT -8 Teg said:

it has been a hot minute since i have done anything with pb, so i forgot lol thank you though.

I am curious, is there a way to write an if/else statement to say the following

If current user group name does not equal group1 group2 group3 or group4, then this happens?

Sept 3, 2023 12:36:06 GMT -8 Kami said:

ahh got it, foreach was gonna be my next question but i had (erroneously it seems) assumed you were only showing a snippet and already had it 😅 glad you got it sorted!

if [variable] != group1 || [variable] != group2

etc. the double pipe || is an inclusive "or" for "if any of these are true", then execute

[Teg]

Awesome, thank you! I'll try that out and see how I fare I appreciate the guidance. 

Sept 4, 2023 11:33:18 GMT -8 Kami said:

Sept 4, 2023 10:47:01 GMT -8 Teg said:

it has been a hot minute since i have done anything with pb, so i forgot lol thank you though.

I am curious, is there a way to write an if/else statement to say the following

If current user group name does not equal group1 group2 group3 or group4, then this happens?

if [variable] != group1 || [variable] != group2

etc. the double pipe || is an inclusive "or" for "if any of these are true", then execute

[Kami]

Sept 4, 2023 12:08:55 GMT -8 Teg said:

Awesome, thank you! I'll try that out and see how I fare  I appreciate the guidance. 

Sept 4, 2023 11:33:18 GMT -8 Kami said:

if [variable] != group1 || [variable] != group2

etc. the double pipe || is an inclusive "or" for "if any of these are true", then execute

yeah np -- note that you need to wrap the group names in quotes if you use that, or use group ID numbers instead.

[Lynx]

If I may - if your check is to say "the current user cannot be in Group1, Group2, Group3 or Group4 (the user cannot be in any of those groups), then you're going to want to use && (and) in that scenario:


if $[variable] != "Group1" && $[variable] != "Group2" && $[variable] != "Group3" && $[variable] != "Group4"


What gets used (|| or &&) depends on the code that follows the if statement. In most cases, I've found I'm using && if I'm also using != and I'm using || when I'm using ==. So, the question to be answered is:

Is the code that follows the if to apply if the current user cannot be in any of those groups (the user cannot be in Group1, Group2, Group3 nor Group4) or are you only concerned if they are not in just one of those groups (but can be in of the other 3)?

[Kami]

Sept 4, 2023 17:11:47 GMT -8 Lynx said:

If I may - if your check is to say "the current user cannot be in Group1, Group2, Group3 or Group4 (the user cannot be in any of those groups), then you're going to want to use && (and) in that scenario:


if $[variable] != "Group1" && $[variable] != "Group2" && $[variable] != "Group3" && $[variable] != "Group4"


What gets used (|| or &&) depends on the code that follows the if statement. In most cases, I've found I'm using && if I'm also using != and I'm using || when I'm using ==. So, the question to be answered is:

Is the code that follows the if to apply if the current user cannot be in any of those groups (the user cannot be in Group1, Group2, Group3 nor Group4) or are you only concerned if they are not in just one of those groups (but can be in of the other 3)?

I see your logic but my thinking was that I haven't had much luck targeting groups that are not chosen to display on the user's profile. I know it's possible in javascript but in the past i've had to use [or] instead of [and] as the check seems to only work in templates for what is displayed

I could be VERY wrong though, it's been a minute since I tested & I don't have a desktop rn to check.

[Teg]

Now I'm having an issue with:

{foreach $[current_user.custom_field]}
               {if $[current_user.custom_field.name] == "Store"}
               {if $[current_user.custom_field.value] != ""}
           <li>
               <a href="$[current_user.custom_field.value]" title="My Store">My Store</a>
               </li>
               {else}
           <li>
               <a href="#" title="Open A Store">Open A Store</a>
               </li>
               {/if}
               {/if}
               {/foreach}
so the != "" should represent empty but it's not registering that. Is there something I am missing?

Then for whatever reason I cannot get the private messages number total to display using this...
<a href="$[current_user.messages.inbox]" title="Private Messages">Owlry</a> {if $[current_user.messages.new]} <span class="sidebar-notification">$[current_user.new_notification]
           </span> {/if}


[Kami]

Sept 5, 2023 10:17:29 GMT -8 Teg said:

Now I'm having an issue with:

{foreach $[current_user.custom_field]}
               {if $[current_user.custom_field.name] == "Store"}
               {if $[current_user.custom_field.value] != ""}
           <li>
               <a href="$[current_user.custom_field.value]" title="My Store">My Store</a>
               </li>
               {else}
           <li>
               <a href="#" title="Open A Store">Open A Store</a>
               </li>
               {/if}
               {/if}
               {/foreach}
so the != "" should represent empty but it's not registering that. Is there something I am missing?

Unfortunately you cannot target a custom field that has not been filled in as it isn't even available — even if you are trying to target it because it is empty, since lack of entry means the value does not exist which means it cannot be targeted.

The workaround is really messy as well. You would have to define an element that exists outside of the foreach loop with a class name, then set that class between a foreach loop and if the custom field is present, then use CSS to say that class should be hidden.

This way, you have an element that shows UNLESS the field is filled. Does that make sense?

[Teg]

Sept 5, 2023 10:25:31 GMT -8 Kami said:

Sept 5, 2023 10:17:29 GMT -8 Teg said:

Now I'm having an issue with:

{foreach $[current_user.custom_field]}
               {if $[current_user.custom_field.name] == "Store"}
               {if $[current_user.custom_field.value] != ""}
           <li>
               <a href="$[current_user.custom_field.value]" title="My Store">My Store</a>
               </li>
               {else}
           <li>
               <a href="#" title="Open A Store">Open A Store</a>
               </li>
               {/if}
               {/if}
               {/foreach}
so the != "" should represent empty but it's not registering that. Is there something I am missing?

Unfortunately you cannot target a custom field that has not been filled in as it isn't even available — even if you are trying to target it because it is empty, since lack of entry means the value does not exist which means it cannot be targeted.

The workaround is really messy as well. You would have to define an element that exists outside of the foreach loop with a class name, then set that class between a foreach loop and if the custom field is present, then use CSS to say that class should be hidden.

This way, you have an element that shows UNLESS the field is filled. Does that make sense?

Yeah that seems like a bit much for something that should be so simple. It does make sense though. Any idea on the second problem in that same post?

[Kami]

Sept 5, 2023 12:43:06 GMT -8 Teg said:

Sept 5, 2023 10:25:31 GMT -8 Kami said:

Unfortunately you cannot target a custom field that has not been filled in as it isn't even available — even if you are trying to target it because it is empty, since lack of entry means the value does not exist which means it cannot be targeted.

The workaround is really messy as well. You would have to define an element that exists outside of the foreach loop with a class name, then set that class between a foreach loop and if the custom field is present, then use CSS to say that class should be hidden.

This way, you have an element that shows UNLESS the field is filled. Does that make sense?

Yeah that seems like a bit much for something that should be so simple. It does make sense though. Any idea on the second problem in that same post?

Yeah I dont super advise it unless you for sure need to have information displayed when the field is blank.

For the second issue, I am admittedly not the best when it comes to message notifications as I usually swap them out for a numberless indicator. elli might be able to help, but I am not sure how often her schedule will allow. Unfortunately since I don't have a PC at this time, I can't do any investigative work to assist in troubleshooting.

[elli]

Sept 5, 2023 13:40:25 GMT -8 Kami said:

elli might be able to help, but I am not sure how often her schedule will allow. Unfortunately since I don't have a PC at this time, I can't do any investigative work to assist in troubleshooting.

Sept 5, 2023 10:17:29 GMT -8 Teg said:

Then for whatever reason I cannot get the private messages number total to display using this...
<a href="$[current_user.messages.inbox]" title="Private Messages">Owlry</a> {if $[current_user.messages.new]} <span class="sidebar-notification">$[current_user.new_notification]</span> {/if}

It looks like you're just missing the 's' on the end:

$[current_user.new_notifications]