[SOLVED] [#6317] Substitutions question

I have the following substitution:
(The \ are there because its inside some php)

Its being used in an article in combination with some php. $youth_id is the userid of the profile being viewed.

When the owner of the profile views the article the field appears as it should.

When an admin views the article it is not shown (the admin can see the field on the profile).

I have found what seems to be causing the problem. cb_vocational_professional_skills is hidden/shown using cb conditional. When i disable the condition the admin can view the field on the article.

So for some reason the condition is causing the field to be hidden on the article for admin even though the field is shown on the profile. Any ideas why?

I have tested this using the following cb conditional versions:
4.0.7+build.2016.07.09.00.28.00.ec65dbf5d
4.0.7+build.2016.11.29.00.30.50.47936091e


Joomla! Version 3.6.2 Stable [ Noether ] 4-August-2016 23:41 GMT
PHP Version 5.6.24
mysql version 5.6.32-78.1
community builder version 2.0.15+build.2016.09.18.15.00.02.b2e3df5e1

CB Conditional acts on the trigger onAfterFieldsFetch to remove fields from the fields array directly. The problem is getFields calls _getTabFieldsDb which fires onAfterFieldsFetch with the viewing user object and not the user object attempting to be displayed. I'm unsure if I'll be able to workaround this, but have added a bug ticket to see if it's possible in a later CB Conditional release.

forge.joomlapolis.com/issues/6317

Unfortunately I've no workaround to suggest at this time, sorry.

It might be worth pointing out that the vast majority of fields on the article, many of which are also hidden/shown using cb conditional, were not affected by this problem and can be seen by both profile owner and admin

Also i added the below code to the few fields that were not appearing for admins and they are now appearing. Is there any reason why i wouldn't want to add this:

New CB Conditional build should be out later today that fixes this issue. The problem is the conditions in this case are being applied to the viewing user instead of the user being displayed. So if you're trying to display a conditioned field from a user other than your self with substitutions it conditions against you and not that user. I was able to implement a fix for this case so that can't happen anymore. You shouldn't need to make any changes to your substitutions or conditions and will just need to update when build is available.

thanks. ill give it a try when its out

looks like it fixed the problem. thanks