Auto Action Field

Hello,
I have a problem with an action field

In the front end, it does not work with the User Login (Registered)

But with the super user login it works in the frontend

In the backend with the superuser login works also.

I've tried the various access levels, but it does not work

version 3.4.0

Trigger: onAfterUserUpdate, onAfterUpdateUser, onAfterUserRegistration


Thanks Stefan

What do you mean it doesn't work with login? You're not using an after login trigger... you've it set to fire after profile update (frontend and backend) and after frontend registration.

the super administrator account works in the frontend but the registered users is not working.

If I [cb_rechnungsadresse] field we change the value stored

But if I leave it blank it shows me always the last value.

IT work as super-admin only

thanks
Stefan

Remove your conditional and see if it works for everyone. Sounds like your conditional isn't matching for registered users. Also ensure CB Auto Actions within CB > Plugin Management is public and published.

I can send you a superuser Login and a registered login and you can Check it???

Superuser Login:
Field value empty -> Text from the condition
Field value "Text" -> ok
Field value empty -> Text from the condition

Registered Login:
Field value "Text" -> ok
Field value "another Text" -> ok
Field value empty -> not Text from the condition, the value "Text"

Can i send you a pn?

It is perhaps difficult to understand what I mean.

It is the field cb_rechnungsadresse when registering with the word "Rechnungsempfänger hier eintragen" are filled.
If this field is later changed it should be saved.
If the field is left blank, the field "Rechnungsempfänger hier eintragen" to be filled

It works with super admin user but not with the registered user.

Stefan

Empty checks for NULL or '', maybe try using an Equal To and specifying no value to see if that'll work. There's no reason for it to work for Admin and not other users unless the field cb_rechnungsadresse you're checking against isn't accessible to the user. Substitutions respect access permissions so if you're trying to check a field they can't even access then it's not going to work properly. Ensure the field is on a published and public tab.