The problem ofa form submission hanging at the “Please Wait” has ben around a while now and multiple updates have not fixed the issue. This was fast becoming a deal breaker for me.
For the non techs out there, this is what is going on. As a non techie this is how I figured it out and understood it.
If you have your mautic installation in a sub directory, ie NOT in a sub domain or on a domain, you will have this issue. So solution number 1 is move your mautic to a domain or sub domain.
If you don’t want to do that then you need to edit some code - a simple cut and paste job. After a form submission Mautic tries to double check something that fails because it is looking for something on the domain on which your Mautic is hosted, but because your matic is in a sub folder the check fails and the form hangs. So we need to change the code so Mautic changes how it does this check it wants to do.
Using FTP or your file manager under your cpanel. Browse to public html, then look for the folder your Mautic is in. Then look for the media folder and then look for a file called mautic-form-src.js and another file called mautic-form.js
Open each file so you can edit the code. use control F to search for event.origin
It will be around 623 and line 38 in the other file.
Look for the code if (event.origin !== MauticDomain) return;
Replace it with var MauticDomainWithoutPath = MauticDomain.match(/https?://[^/]*/); if (event.origin != MauticDomainWithoutPath) return;
make sure this added as one line of code.
Do this in both files.
Delete the cache by looking for the cache folder i your main mautic folder and deleting it. Don’t worry it will be recreated when you use mautic.
This should solve the issue. Test in incognito mode in your browser.
You will need to reapply this fix after every Mautic update until it gets fixed by an update.
Hi bizcrony,
thanks for your response.
I had deleted the cache folder in mautic installation an run mautic again. Same issue.
What do you mean with ´update schema´? Running the upgrade process to 2.13.1 once?
Using mautic 2.13.1 in a subdomain with forms containing fields with radio or check-buttons occur a ´please wait´ message after submitting such form.
Forms without these field characteristic are working.
The please wait screen problem won’t just go away - I have the solution below:
if (event.origin !== MauticDomain) return;
// Replace the above with these two lines in both files
var MauticDomainWithoutPath = MauticDomain.match(/https?://[^/]*/);
if (event.origin != MauticDomainWithoutPath) return;
I tried this solution on version 2.13.1 it did not work. I tried it on version 2.11.1 it did not work. I have tried all the solution I can find on the internet, nothing seems to remove the please wait screen. Mautic is frustrating!!!
I installed Mautic on a direct domain the please wait screen remains, I have installed on a sub domain, same problem
Kelly hello , i can understand the problem of your , it might be issue with internal server error, you can right click on that page and inspect and see console. and then talk to your hosting. they will resolve internal server issue.
bizcrony thanks for your response. I actually saw “Failed to load resource: the server responded with a status of 403 (Forbidden)” error on the console
Following bizcrony advise, I contacted my host provider and the issue was resolved. According to them what needed to be done was to modify the ModSec config and edit the default items per page from 30 to 20.
I have a pristine install of Mautic on a cPanel add-on domain (not sub-domain). There are is no other CMS installed on this virtual host.
When I try to save config changes I get the now-infamous “Please wait…” screen of death.
My javascript console reports:
[Error] Failed to load resource: the server responded with a status of 403 () on
https://xxxxxxxxxx.com/s/config/edit?mauticUserLastActive=1&mauticLastNotificationId=
Mautic Version 2.13.1
Apache Version 2.4.33
ModSecurity disabled
PHP Version 7.1.18
In php.ini I have given mautic an insane amount of memory etc in order to try to overcome this problem: