Please Log in or Create an account to join the conversation.
jakobe75 wrote: ... Although they might lose the ability of custom privacy levels to connection categories...
Please Log in or Create an account to join the conversation.
Substitutions will respect privacy but it depends on what substitution is used. For example [FIELDNAME] and [cb:userdata field="FIELDNAME" /] both ignore privacy while [cb:userfield field="FIELDNAME" /] should. With userdata and userfield it's also possible to specify the "reason" which could be "list", "profile", etc.. as well as "output" among others. Maybe try the below if you want just the value.yes it displays the email address
no it doesnt respect the privacy settings.
oh well.....
If the main email address field has privacy available and it is set to "do not display"
the delimiter overrides this and displays anyways.
it must be a delimiter field limitation.
Might be worth correcting in an upcoming release if possible.
delimiters should have the ability for privacy as well.
until then I will find a workaround.
Nope, never used SuperMessanger sorry.Any advice on how to call SuperMessanger instead of the default CB email system?
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
My favourite cheat-sheet for CB Thanks for updating the page... but, please, could you give some examples for the syntax and final output. That would be a big difference and a great help. Thanks in advance.krileon wrote: ...
[cb:userfield field="email" output="rss" /]
... I've updated my substitution tutorial to provide a comma separated list of reasons, outputs, and formatting.
Please Log in or Create an account to join the conversation.