Unexpected error en registration process about webissues

[mimecorg]

When an error like this occurs, you should be able to see the detailed information in the event log (Tools > Event Log).

[sergiokessler]

Ok, I found it, thanks !

Unhandled PHPMailer\PHPMailer\Exception: Error SMTP ...

Maybe I misconfigured the mail settings, but the problem is that accounts created remains in an inconsistent state...
So, I think this is a bug...

(you don't see any in User Accounts but trying to re-register fail with 'username already exist')

[sergiokessler]

ok, delete * from register_requests cleaned up things...

[sergiokessler]

Now, there is 2 additional problems:

Mail setings:

1. this doesn't produce any log at all

2. the PHPMailer included is old, very old...

[mimecorg]

Yes, you're right, the error should be logged when email settings are tested, I will fix that. PHPMailer is from December 2019, so it's not super old, but I will update it in the next release of WebIssues.

Requests that are not activated are automatically removed from the register_requests table by the cron job. It's not perfect, but even if the email is sent, there is no guarantee that it reaches the recipient.

[sergiokessler]

ok, thanks!

IMO the register_requests records should not be stored at all if there is an error in the process...
(like that "unexpected error")

do you have an estimate when the next release is coming ?

[mimecorg]

I took a while, but I finally released version 2.0.3 with updated PHPMailer and improved SMTP logging and diagnosing.

[gh658804]

In a somewhat related issue, i had the webissues database taken offline and i received the same error. This error is too general. It would be nice if it could be analyzed a bit. Perhaps something like "Unexpected error in * subsystem", where * could be Mail, Database or whatever else could exist. At least then you could narrow it down and immediately know where to look without checking any logs.

BTW, "Tools > Event Log" as said in your first reply was not helpful for me. Perhaps the message could also have more specific directions on where to go to find a more detailed description of the error.