Confirmation redirect path config field not working as expected

Thanks for the post @hannakras. The confirmation redirect feature is passing tests and works for me in my local test system. I'm happy to dig into this further but will need more info. Guessing a different module is interfering. Use my d.org contact form if you want to send me login info to your site or a site dump.

Hey @john.oltman, I was using the same node to test my changes. If I updated the field instance config, then the changes were not displaying in my current node. I tried updating the confirmation message and redirect, neither worked as expected. I exported the config and cleared cache as well. When I create a new node, the confirmation message and redirect changes are reflected. It appears that registration_settings_field_data is storing the confirmation message and redirect in the database. I didn't realize the confirmation message and redirect could be set per node, and what I was affecting were actually the defaults on the content type > registration field settings, so those defaults weren't affecting previously created nodes. Now that I got that figured out, everything works as expected.

Great to hear, thanks for letting me know. Yes, registration settings are "per host entity", or per node in your case, with only the defaults in config. Glad it is working for you.