Send email to user upon registration

Hi,

I am struggling heavily with this on Drupal 10, Registration 3.0.1 and Rules 8.x-3.0-alpha8.

Broadcasting e-mail to registrants works.

When trying to enable default Confirmation email (Structure > Registration Types > My type > check Enable confirmation email. The result is "The website encountered an unexpected error. Please try again later."

Going with Rules... well nothing works. Configuration > Workflows > Rules > Add reaction rule. Events: After saving a new registration entity, Action: Send e-mail. Nothing happens even with hardcoded values, not using any wildcards.

Thanks @pawleeq, if you are able to post a stack trace of that error message from the logs please do. I realize this issue is mostly about Rules, but I would guess that if you uninstall Rules the confirmation setup page on the Registration Type would work - guessing something in Rules breaks when doing that setup. That said, might be wrong on that, a trace would help.

Ok, so i uninstalled Rules and flushed the caches. Confirmation email setup failed again and here is what comes out from the log:

Type php
Date Thursday, October 12, 2023 - 21:45
User pawleeq
Location https://nove.roubenkyasruby.cz/admin/structure/registration-types/reistr...
Referrer https://nove.roubenkyasruby.cz/admin/structure/registration-types/reistr...
Message TypeError: Cannot access offset of type string on string in Drupal\Component\Utility\NestedArray::setValue() (line 155 of /nove.roubenkyasruby.cz/core/lib/Drupal/Component/Utility/NestedArray.php).
Severity Error

Hope that helps.

So it isn't Rules. The confirmation feature is passing tests, so it may be a different module interfering or perhaps something in the registration module that has not been encountered before. I would like to assist further, if possible please post a database dump and web files dump and send a link to those to my Contact page on Drupal.org. I could then download those and debug the issue on my local test system. There is not enough in the trace to pinpoint the issue. Thank you!

@pawleeq would you be able to create a new issue with the error message and we can pick this up in that thread. Since this one is closed and refers to creating the feature which is complete.