AJAX call error and throws parsererror

the solution is to declare $item as new stdClass

if(empty($item)) {
$item = new stdClass(); //in order not to violate E_STRICT standards
$item->title = null;
$item->params = array();
}
in models/profiles.php lines 238 until 241

for J3 and on refactor all your JRequest::getVar to

$jinput = JFactory::getApplication()->input;
<var> = $jinput->post->get(...)

and in order to get the whole $_POST (in profiles->store() ) you'll have to do

$jinput = JFactory::getApplication()->input;
$post = $jinput->getArray($_POST);

As your working on the next version please ensure that you clean up the installer sql.
Your creating:

UNIQUE KEY `profileid_2` (`profileid`,`column`),
KEY `profileid` (`profileid`),
KEY `profileid_3` (`profileid`),
KEY `column` (`column`)

whereas you only need

UNIQUE KEY `profileid` (`profileid`,`column`),
KEY `column` (`column`)

right. the interesting thing is, that the debugger throws a warning for direct calls (see initial comment) to the hexdata function itself. without thinking about it too much, is there a way to @ suppress errors for the ajax call?

After debugging we found that the issue is due to error reporting being on. Are you developing on error_ = off?

in addition, if ajax dataType is changed to html and the controller is set to return
$obj->html
the call works again

any call of load_columns on both joomla 3.15 and 2.5.14 generates a parsererror javascript error. It is definitely the ajax call, as a direct call to the php function

index.php?option=com_hexdata&view=profiles&task=load_columns&table=<tablename>&id=1&<token>=1&abase=1

returns the correct ul