Just a word of advice from those that have done it, have you seen any major side effects after disabling the AjaxUI? I’m afraid it will cause a lot of problems.
Unfortunately any sort of complex modification of the very top navigation header becomes very hard with this thing enabled, so I’m thinking of just disabling it altogether
I wouldn’t recommend disabling it, it’s been there for so long, and nobody is really testing SuiteCRM without AJAX… you wander off into uncharted territory.
I admit I am not very knowledgeable in this, but I believe you don’t need to turn off AJAX in order to use non-AJAX links. They can co-exist. So if you need custom stuff and don’t want to use AJAX, you just add non-AJAX links there, right?
Thank you for the reply. I’ll keep it in mind.
Problem is that with ajaxui enabled I can’t customize the header properly. It doesn’t read cookies and $_REQUEST in _headerModuleList.tpl and unfortunately it’s stalling the whole project, probably due to my lack of knowledge of JS, so I have no choice but to sail into the uncharted territory 
What exactly are you trying to do in _headerModuleList.tpl?
If you work on the file that includes it you will probably have a better chance. That one is just a tpl, a Template. There is another PHP file loading it and constructing a page from it. That’s probably the best place to add JS stuff.
Hi
Thank you. More specifically I try to read the $_COOKIE that is set and also the value of $_REQUEST, it’s being invoked by the displayheader() function in sugarView class, but the problem is that it always displays the module as “home” no matter what page we’re on and I’m not able to read the $_COOKIE values. I’m sure it’s simple stuff for anyone that knows JS, I’m just very bad at it.
Guess I’ll be the guinea pig and if ever anything goes terribly wrong with AjaxUI disabled, I’ll report it here 
