[SOLVED] Strange result for query field

For substitutions to work properly the fields will need to be visible on profile. You can however move them to a tab that is in a not shown on profile position and this would easily hide them from public eye, but still allow their substitutions to work. Alternative is to adjust your substitutions to try and display the userlist view instead of the profile view (default).

That's an annoying limitation, as I have the delimiter field showing.
The construct is that I have a tab holding the address, that contains a street, and a zipcode / city.
I want the user to enter the zipcode, and then I'll provide the city via query.

The suggestion of moving the zip code to a seperate tab, that's hidden in the profile, and then have the user enter street on one tab, and zip on another when they edit the profile, for me to show them neatly, makes it clumsy or even ugly.

How would I make two fields appear side by side on the profile and in the list? Is that what you suggest as the alternative? Not sure how to do that.

How would I make two fields appear side by side on the profile and in the list?

Delimiter field with substitutions.

Is that what you suggest as the alternative?

Alternative is something like the below.

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

This displays based off userlist accessibility, but it's probably going to have the same display restrictions.

So, we're going in circles
I think the restriction is really odd and inconvinient.

Then there's a problem with your configuration. You can't tell it to show a field then hide a field at the same time, that makes no sense. You need to review your setup and reconfigure in a more logical manner. You can also try using CB Conditional to hide the field on profile only with a condition that can't be met so it always hides.

Substitutions are designed to respect configuration and permissions. If it didn't it'd be a security hole.

GRIN, security, hmm, please note that this started with a problem with the display of the fields, and it actually WORKED partly, it DID show the "postnummer by" delimieter until the field postnummer was empty, so please, me thinks the horse is a bit high

I do understand the argument, but you've locked the system to have security on the tab level, and not the field level, and tabs can not be shown combined, ie. 'two tab in one', and fields has to all be on the profile, and some fields can have contextual similarties, but have different security levels.