CB Auto Actions

var4 of onBeforeDisplayUsersList is $allFields, which is an array. It's not going to output anything. It'd be a bit more helpful if you can provide what you're trying to accomplish so I can better suggest a usage.

Actually I was hoping I´d have the same options like when coding a plugin.
The usage would be to read out the fields and substitute a field by another one.

Actually I was hoping I´d have the same options like when coding a plugin.

That's not going to happen. There's a huge difference between using a trigger and using a fieldtype plugin. If you need a new fieldtype you'll need to develop a new fieldtype plugin.

The usage would be to read out the fields and substitute a field by another one.

You want to replace 1 fields value with another fields value? You could try using the before/after fieldrow trigger, but I still doubt it's going to provide exactly what you want. You're better off using a delimiter field and having IF substitution conditions in it to determine different output.

krileon wrote: You could try using the before/after fieldrow trigger

Where is this trigger? I could not locate it here: www.joomlapolis.com/support/tutorials/120-api-usage/18358-using-cb-triggers

Where is this trigger? I could not locate it here: www.joomlapolis.com/support/tutorials/12...58-using-cb-triggers

It's not document, because it's advised not to use it. It triggers on every single fields output. So using it could cause some very damaging results unless you know how to properly use it. It's primarily for plugin usage.

onBeforegetFieldRow
onAftergetFieldRow

I suggest you just use a delimiter field with IF substitutions. Again, be extremely careful with the above two triggers as it is very possible to wipe out the display of every field using them.

krileon wrote: It's not document, because it's advised not to use it. It triggers on every single fields output. So using it could cause some very damaging results unless you know how to properly use it. It's primarily for plugin usage.

Don´t you think this sounds contradictionary? I should not use it unless I know how to use it but you do not provide any documentation on how to use it. Weird.

krileon wrote: I suggest you just use a delimiter field with IF substitutions. Again, be extremely careful with the above two triggers as it is very possible to wipe out the display of every field using them.

Well there are some weird things happening when I try to follow this advice. For this delimiter field you have suggested, I dont´t want the user to be able to search for it. Well basically this delimiter field should only show up in the userlist view. While the field the delimiter field relies on should appear on profile and on the search form.
When I try to build this using the conditional plugin I am experiencing weird things:

1. When I set "Show on profile" to yes in the field parameters and hide within the coditionals parameters, only the field value gets hidden while the field name will show up in the user list. This is weird. I would expect the setting "Show on profile" to effect only the setting for profile view and not for user list view. When I set "Show on profile" to no then the field will not show up in the user list. However this is not an option in my case as the field must be visible on profile.

2. When I use the IF statement in the delimiter field to validate a specific value from another field it seems that it will only return a result when the other field is visible. When I set the condition for the field to check on to "hide" and try to validate the value, then nothing gets returned. I would have expected the IF-statement to check on real value and not on visiblitiy. Or is there a way to tell the IF-statement to disregard the visibility state of the field?