The only way I can get it to work as expected is if I am editing the view in question, Workshop Events. While editing, even looking on another computer that is logged out, it works as expected. Once I close the editing page, the conditional no longer works.
It works as expected on the content template, but not on the View. It works while you are logged into the site. But visit the site when you are logged out and it is no longer working. It is almost like the conditional has some kind of privilege interaction that does not allow it to display correctly when the user is logged out.
Since this is a live site, I did not want to experiment on it too much on it. So I made a local copy of the site and turned everything off with the exception of Toolset. Even WooCommerce. It had no effect. Maybe installing Access and forcing the content to be visible to all users? As I said, it only happens when I am logged out.
In my testing I was not able to replicate the issue.
At this point I wouldn't say it is a bug as yet, however I would like for you to create another copy of this view from scratch on a separate page and see if the same issue remains.
As of my testing on my localhost with the latest versions of toolset I was not able to replicate.
Well, this is good news and bad news. The good news is that Toolset is not broken, the bad news is that I am not sure what would cause this at this point. I will do as you say, Shane. As I said, I have a local copy that I can play around with. I will report back after testing. Thanks as always for your help Shane.
Ok, I figured out. The conditional is working right. I stylized the box using the Block styling features as opposed to writing my own CSS. In this case, the background color declaration is being removed when logged out. The workaround was to rewrite the CSS targetting that element. I still see an issue that might be a bug. Why are the block styles being removed? I think this might need some further investigation from your development team. The good news is that it is an easy fix for someone who knows CSS.
Since our 2nd tier supporters are aware of the issue and i've provided them with a copy of a test site that I have with the issue replicated, there isn't anything much more we can do here.
If there is any other questions on this please let me know. If not then you can go ahead and mark this ticket as resolved.
