"User is not set" error in recent versions

[hughbris]

"User is not set" error in recent versions

[rhukster]

What does your email config look like (please
redact sensitive information).

Also can you provide an example form or scenario that exhibits this issue so I can try to recreate it. ?

[hughbris]

Thank you.

Also can you provide an example form or scenario that exhibits this issue so I can try to recreate it. ?

There is no form exhibiting this behaviour. Mail is generated from a contact form successfully. Pretty textbook setup.

The error is only present in Grav logs and some CLI commands, at least cache-clear and I think other(s).

Configs

Site A

email.yaml:

from: [email protected]
from_name: A website
to: [email protected]
to_name: Website A
reply_to: [email protected]
reply_to_name: Website email alt
mailer:
  engine: mailjet
content_type: text/html
debug: true # it's a dev install

email-mailjet.yaml:

enabled: true
transport: api
api_key: API_KEY_REDACTED
secret_key: SECRET_KEY_REDACTED

Site B

email.yaml:

from: [email protected]
from_name: "B website"
to: [email protected]
to_name: Website Owner
mailer:
  engine: sendinblue
content_type: text/html
debug: false # is an unlaunched prod site

email-sendinblue.yaml:

enabled: true
transport: api
access_key: ACCESS_KEY_REDACTED

Let me know if I can provide anything else.

[rhukster]

I can't recreate this with your maijet or sendinblue configruation. Can you look in your grav.log and see if there's more detail on where the error is happening?

Thanks.

[hughbris]

Thanks for trying to reproduce. Damn tho :/

bin/grav logviewer is one of the commands that work. I can't see anything in the logs. These are my logging settings just in case there's something I can set to log more: log.handler=file, errors.log=true.

I decided to test the other CLI commands bringing up this error, except server, new-project, sandbox. The only ones that brought up this error were page-system-validator, scheduler, and security.

I tested other CLI commands. bin/gpm and bin/plugin work fine except for bin/plugin email test-email ...

• worked with the local environment flag --env where I have mailtrap setup with SMTP
• failed for the default/prod settings (Mailjet API), with that same error in the issue title
• switched the default config to Mailjet with SMTP, the error did not happen. I got "Problem sending email..." in the debug output but I think that is just a DKIM thing because it was runnign locally. It did seem to bypass the "user not set" error.

Hope that helps. Looks like I will be able to work around this problem easily by reverting to SMTP settings.

Just a wild idea: could this be related to having environment overrides? I use those too. My experience is that these env configs are merged opaquely by Grav by the time any plugin goes to use them.

The other mystery is why only some of my installs experience this. I can look harder for patterns there if need be.

[hughbris]

My pleasure to contribute.

[rhukster]

if you want to PM your account creds on discord, I can test again. but I don't have an active account with them anymore.