"An Ajax error has occurred"

[Rykono]

Right after i start typing in the text box i get an error from osTicket, stating "An Ajax error has occurred.". Tinymce is working except for autosave feature. I have played with turning off and on both autosave feature and restore feature. Still get the error on any combination.

I double checked that the install files are where they should be. Pretty positive i have followed the directions exactly as written. I apologize if this is not posted correctly.

Server Information

osTicket Version | v1.10.1 (9ae093d) —  Up to date Web Server Software | Apache MySQL Version | 5.6.36 PHP Version | 5.6.31

O = in use

gdlib | O - Used for image manipulation and PDF printing imap | O - Used for email fetching xml | O - XML API xml-dom | O - Used for HTML email processing json | O - Improves performance creating and processing JSON mbstring | O - Highly recommended for non western european language content phar | O - Highly recommended for plugins and language packs intl | O - Highly recommended for non western european language content fileinfo | O - Used to detect file types for uploads APCu | X - Improves overall performance Zend Opcache | X - Improves overall performance

cgi.fix_pathinfo | "1" is recommended if AJAX is not working date.timezone | UTC

[Rykono]

Sorry just occured to me to check developer tools.

Upon ticket load,

"Failed to load resource: the server responded with a status of 418 (I'm a teapot) /osTicket/scp/ajax.php/lock/ticket/739

[Rykono]

Last update sorry for spam.

	(anonymous)	@	VM4145:1
	send	@	jquery-1.11.2.min.js?9ae093d:4
	ajax	@	jquery-1.11.2.min.js?9ae093d:4
	acquire	@	ticket.js?9ae093d:58
	(anonymous)	@	ticket.js?9ae093d:247
	each	@	jquery-1.11.2.min.js?9ae093d:2
	each	@	jquery-1.11.2.min.js?9ae093d:2
	$.fn.exclusive	@	ticket.js?9ae093d:242
	(anonymous)	@	tinymce-osticket.min.js:1
	i	@	tinymce.min.js:10
	fire	@	tinymce.min.js:10
	g	@	tinymce.min.js:10
	m	@	tinymce.min.js:2
	y	@	tinymce.min.js:2

[mckaygerhard]

there's some problems with the minified js version and the location request from server root.. i'm remenber some of this problems are related to tinymce plugins.. do you have some features that implies a apyd plugin?

[wgalafassijr]

I have the same issue. Some fix?

[mckaygerhard]

i not working on this due the lack of support from very obtuse developers of osticket.. as i said, there's a problem retrieve the paths from server, we nee to workaround with usage of the $_SEVER variables in the code from the CGI scrip info var

[wgalafassijr]

sorry but i don't understand because i'm not a developer. there's a way to fix this ? can you clarify please? Regards

[mckaygerhard]

@wgalafassijr the problem, the problem is that the developer of this plugin has deprecated and abandoned the development, maybe due that reason:

-> those who develop osticket are despotes and only serve those who suit them, there are reported problems with more than 5 years old and with simple solutions and even being so simple they are not fixed ..

How does that affect me ?, easy, every time a change is proposed or how to do something, the answer is null or contemptuous, citing that you have to be a developer or read a lot .. obviously if in our case we can not because we are busy and we comply with reporting and propose the improvement due

I try to ask for many thigs but the furms are very confused and there's no table description or database ditionary, no info about development artifact and only thousand of lines of code very complex to understand..

i try to understand the plugin system but i need time also for my live and for my own projest..so i cannot spend so many time to try to fix this..

if you try to made something post somethig similar in osticket forums and issues.. you will noted a lot of issues many many... i must fork my own osticket brand and backport all of the fixed around the code, are at gitlab not github i not use mocosft guindows..

[Bartt94]

I have the same mistake can you help us please.

[mckaygerhard]

@Bartt94 you can help by making many reclams as possible at the osticket repository.. They are the major responsible for the end of all development, due constants changes and poor support (unless paid of course)