|
|
We have some other,
Some for show it in all condition : need hacking code, but can happen after session close for example |
|
|
|
Sample test here too
Have same alert with 403 (but for 403 need hack PHP code) |
|
|
|
OK, so this is when an ajax call fails, right? |
|
|
|
OK, so this is when an ajax call fails, right?
Yes, i think. I don't know when this error was added, but we have it on some ajax call.
/master$ grep -ri "please reload the page" *
assets/scripts/admin/failedEmail.js: alert('An error occured while trying to save, please reload the page Code:1658139259132\n' +
assets/scripts/admin/statistics.js: alert("An error occured! Please reload the page!");
assets/scripts/statistics_user.js: alert ("An error occured! Please reload the page!");
assets/packages/permissionroles/js/permissionroles.js: window.LS.ajaxAlerts('An error occured while trying to save, please reload the page Code:1571314170100', 'danger', {showCloseButton: true});
assets/packages/usermanagement/js/usermanagement.js: alert('An error occured while trying to save, please reload the page Code:1571926261195'); |
|
|
|
On some systems I work with, the ajaxSetup for handling errors is being done automatic and general-wise, so if the ajax fails with 403 or 500 std error messages can be show. |
|
|
|
I think we have 2 ajax error systezm return …
We must not create one again or it must be the last one … then we need to remove all other … |
|
