CB

Added support to getTab for output, formatting, and reason. Extended REGEX to capture output="STRING", formatting="STRING", and reason="STRING". Test case as follows (confirmed working). Completely backwards compatible as the additional options are similar to user= and not required.

Without User:
[cb:userfield field="avatar" output="html" formatting="none" reason="list" /]

With User:
[cb:userfield field="avatar" user="#me" output="html" formatting="none" reason="list" /]

Any combination of user, output, formatting, or reason can be used as well. So all 3/4 are not required to be provided. You can simply provide just reason such as follows.

[cb:userfield field="avatar" reason="list" /]

Sorry, named $output as $display, makes more sense to be $output. Rev2 fixes this.

Thanks Kyle.

• added default="....." which displays when field or tab is not showed to user for any reason (access level, no user, and so on).
• added $default to getTab() API as well, to make it consistent with getField().

Probably the regexp could be changed as follows:

instead of:

#\[cb:user(data +field|field +field|tab +tab|position +position)="([a-zA-Z0-9_]+)"(?: +user="([^"/\] ]+)")?(?: +default="((?:[^"]|\\")+)")?(?: +output="([a-zA-Z]+)")?(?: +formatting="([a-zA-Z]+)")?(?: +reason="([a-zA-Z]+)")? */\]#

to something like this:

#\[cb:user(data +field|field +field|tab +tab|position +position)="([a-zA-Z0-9_]+)"(?: +(user|default|output|formatting|reason)="((?:[^"]|\\")+)")* */\]#

or even:

#\[cb:([^ ]+)(?: +(field|tab|position|user|default|output|formatting|reason|[a-zA-Z]+)="((?:[^"]|\\")+)")* */\]#

That would then allow to generalize the parser...and even make it fully extensible.

That is as forethought for related feature #2297