I had assumed this was another Divi problem but it happens in Astra too
I have reverted things back but so far I have tried:
Changing themes back to Astra
Disabling all non-toolset plugins
Removing custom functions.php
Enabling/Disabling Ajax for form submission (shows an error if ajax is on)
Removing my custom form and generating new from content
Scoured your site & docs
I get that it could be an ajax conflict but at a dead loss for whats going on
No matter what I try you have to double click the reply message (which I have renamed to respond to quote)
Any help or pointing me in the right direction with this would be very very appreciated , thank you!
When logged in, can be seen at:
hidden link
type and message & submit.. then submit again after the page reloads
Hi, my tests seem to indicate that it is Divi related. I downloaded a clone of your site and deactivated all plugins except Toolset and activated Astra. I left the Layouts plugin inactive. Then when I submitted the Form I was correctly redirected to the My Messages page. If you approve, I will run that test on your site. I think we were just stepping on each others edits in wp-admin now.
Thanks, I saw you were working so I backed off for now. You have my permission to try that. But I believe I already did. You are smarter though so you have full consent to do anything on here that you think will work. I have created a fresh backup right now and I won't touch anything until you let me know
I noticed it was the end of your day so I ended up trying what you did. I can confirm that it did work when Astra was active instead of DIVI, I did not need to disable any plugins. Quite a lot has gone into the custom child theme of divi being used. Do you know if there would be any workarounds ? The only thing I can think of is an ugly hack using multiple themes but probably far from ideal
I'm not aware of any workarounds offhand, this is the first time I've noticed this issue. I will submit this ticket to my 2nd tier team for additional investigation.
Hello, our developers are reviewing some older tickets and have been unable to reproduce this issue in a clone of your site. They seem to think there were some modifications made to core files, like adding cache functions. Is this issue still relevant for you? If so, we can try again by creating a new clone of the site.
