The dump was just for debugging reasons, of course.
Why should it be kirby.user.something? I can call user.id and user.name and other methods as well. When i define another user method i expect it should be user.methodname, or not?
Well, i’m in a user context (see initial posting: user blueprint). A user blueprint is a blueprint which defines the user profiles. In that user blueprint, you can use the query language and the $user-Object is accessible via user. For example, you can do this:
test:
type: info
text: "{{ user.email }}"
This prints the users email.
After defining another user method i’d expected to be able to access it with user.methodName.
Additionally, it doesn’t work with kirby.user.methodName.
Only the standard methods seem to work, like .name, .id and so on, but my own methodName which has been defined in config.php like described in the reference doesn’t seem to be even called. The function is not executed.