In my experience, lately these messages about AjaxUI are not really Ajax errors, and I never needed to disable AjaxUI to get anything working with SuiteCRM .
I think that was more of an old thing from SugarCRM days, although I admit even today you might sometimes work around some issue by disabling it, but it really shouldn’t be necessary.
I got this same error by sorting on a subpanel column which break the query on that subpanel. Thus I could not go back to change the sorting or rest to default so that SuiteCRM can no longer sort on that column but that didn’t worked. So i provided some dummy values in the Query Result set in order to bypass the error and display the full module view and then clicked on the Name column of subpanel to change the Sorting Preference.
Is there any way where user can change the sorting preferences on Subpanels or reset it to their defaults?
index.php?action=index&module=Module&searchFormTab=advanced_search&query=true&clear_query=true is for the Module but not for underlying subpanels.
But if you know of a specific list of “steps to reproduce” that bug, I would definitely open an issue on Github for it. It shouldn’t be too hard to make it fail more gracefully - if it can’t sort, just drop the filter automatically instead of breaking the UI for the user…