Thanks for the feedback, this is on the to-do list for the next update.
In fact, it sounds like a general issue with errors when custom redirect is enabled. So while I appreciate the feedback, there is no need to post further regarding error/redirect issues. They all will be tested and resolved in the next update. Thanks.
Just to follow up with this, I have added a new template tag that can be used to display errors when the “Redirect URL” setting is enabled. So that issue is resolved as of USP version 20160815.
For the RTE field not showing errors, I am seeing that the PHP-generated error is working normally. So when the form is submitted and the RTE field is empty, the following error will be displayed to the user:
“Error: Post content required”
So error messages are displayed for the user when RTE is enabled.
However, for the client-side/JavaScript error messages: those are added via the Parsley script. In order for a field to work with Parsley, a data-required attribute must be added, as can be seen for most of the form fields. Unfortunately, for WP RTE field, adding a data attribute is not possible because the field itself provides no way to do so, AND to make things worse the RTE field is included via iframe, so not possible as far as I know to modify with JavaScript. I am open to suggestions, if anyone knows a way.
Summary: redirect issue is resolved, RTE errors work via PHP, RTE client-side errors not possible due to how WP displays the field (via iframe).
