AJAX call error and throws parsererror
- Daniel
 - Offline
 - Administrator
 - 
            
         
            
        
                01 Mar 2014 12:47                #178
        by Daniel
    
    
            
Thanks
Daniel
    
            
            
            
            
            
                                
    
                                                
    
        Replied by Daniel on topic AJAX call error and throws parsererror            
    
        HexData 1.1 has got the fix    
            Thanks
Daniel
Please Log in to join the conversation.
- Eli Aschkenasy
 - Topic Author
 - Offline
 - New Member
 - 
            
         
        Less
        More
        
            
    
        - Posts: 7
 
            
        
                25 Sep 2013 19:32                #36
        by Eli Aschkenasy
    
    
            
            
            
            
            
                                
    
                                                
    
        Replied by Eli Aschkenasy on topic 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
    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
Please Log in to join the conversation.
- Eli Aschkenasy
 - Topic Author
 - Offline
 - New Member
 - 
            
         
        Less
        More
        
            
    
        - Posts: 7
 
            
        
                25 Sep 2013 17:45                #35
        by Eli Aschkenasy
    
    
            
            
            
            
            
                                
    
                                                
    
        Replied by Eli Aschkenasy on topic AJAX call error and throws parsererror            
    
        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);
    $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);
Please Log in to join the conversation.
- Daniel
 - Offline
 - Administrator
 - 
            
         
            
        
                25 Sep 2013 16:22                #34
        by Daniel
    
    
            
Thanks
Daniel
    
            
            
            
            
            
                                
    
                                                
    
        Replied by Daniel on topic AJAX call error and throws parsererror            
    
        Really thanks you for your suggestion. In the next version Database structure is all changed.    
            Thanks
Daniel
Please Log in to join the conversation.
- Eli Aschkenasy
 - Topic Author
 - Offline
 - New Member
 - 
            
         
        Less
        More
        
            
    
        - Posts: 7
 
            
        
                25 Sep 2013 16:20                #33
        by Eli Aschkenasy
    
    
            
            
            
            
            
                                
    
                                                
    
        Replied by Eli Aschkenasy on topic AJAX call error and throws parsererror            
    
        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`)
    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`)
Please Log in to join the conversation.
- Daniel
 - Offline
 - Administrator
 - 
            
         
            
        
                25 Sep 2013 05:58                #32
        by Daniel
    
    
            
Thanks
Daniel
    
            
            
            
            
            
                                
    
                                                
    
        Replied by Daniel on topic AJAX call error and throws parsererror            
    
        Hi,
For now while using HexData you'll have to keep the debugger off. However We are working on the next version of HexData. We'll take care of it in the next release.
Thanks
            For now while using HexData you'll have to keep the debugger off. However We are working on the next version of HexData. We'll take care of it in the next release.
Thanks
Thanks
Daniel
Please Log in to join the conversation.
- Eli Aschkenasy
 - Topic Author
 - Offline
 - New Member
 - 
            
         
        Less
        More
        
            
    
        - Posts: 7
 
            
        
                24 Sep 2013 16:36                #31
        by Eli Aschkenasy
    
    
            
            
            
            
            
                                
    
                                                
    
        Replied by Eli Aschkenasy on topic AJAX call error and throws parsererror            
    
        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?    
    Please Log in to join the conversation.
- Daniel
 - Offline
 - Administrator
 - 
            
         
            
        
                24 Sep 2013 15:38                #30
        by Daniel
    
    
            
Thanks
Daniel
    
            
            
            
            
            
                                
    
                                                
    
        Replied by Daniel on topic AJAX call error and throws parsererror            
    
        JSON Ajax calls in HexData works only when none of the extensions is throwing any error or warning message. In your case any of the plugin is throwing any error which needs to be corrected. And Yes if you disable the error reporting it'll work fine.
Thanks
            Thanks
Thanks
Daniel
Please Log in to join the conversation.
- Eli Aschkenasy
 - Topic Author
 - Offline
 - New Member
 - 
            
         
        Less
        More
        
            
    
        - Posts: 7
 
            
        
                24 Sep 2013 15:33                #29
        by Eli Aschkenasy
    
    
            
            
            
            
            
                                
    
                                                
    
        Replied by Eli Aschkenasy on topic AJAX call error and throws parsererror            
    
        After debugging we found that the issue is due to error reporting being on. Are you developing on error_ = off?    
    Please Log in to join the conversation.
- Daniel
 - Offline
 - Administrator
 - 
            
         
            
        
                24 Sep 2013 05:19         -  24 Sep 2013 05:22        #28
        by Daniel
    
    
            
Thanks
Daniel
    
    
            
            
            
            
                                
    
                                                
    
        Replied by Daniel on topic AJAX call error and throws parsererror            
    
        Hi,
Please send us your Backend login and FTP details at support@hexsystechnologies.com, We'll look into it. It seems to be a conflict specific to your site. We'll try to resolve it asap.
Thanks
Danish Babu
            Please send us your Backend login and FTP details at support@hexsystechnologies.com, We'll look into it. It seems to be a conflict specific to your site. We'll try to resolve it asap.
Thanks
Danish Babu
Thanks
Daniel
        Last edit: 24 Sep 2013 05:22  by Daniel.            
            Please Log in to join the conversation.
- Eli Aschkenasy
 - Topic Author
 - Offline
 - New Member
 - 
            
         
        Less
        More
        
            
    
        - Posts: 7
 
            
        
                23 Sep 2013 23:27                #27
        by Eli Aschkenasy
    
    
            
            
            
            
            
                                
    
                                                
    
        Replied by Eli Aschkenasy on topic AJAX call error and throws parsererror            
    
        in addition, if ajax dataType is changed to html and the controller is set to return
$obj->html
the call works again
    $obj->html
the call works again
Please Log in to join the conversation.
- Eli Aschkenasy
 - Topic Author
 - Offline
 - New Member
 - 
            
         
        Less
        More
        
            
    
        - Posts: 7
 
            
        
                23 Sep 2013 21:37                #26
        by Eli Aschkenasy
    
    
            
            
            
            
            
                                
    
                                                
    
        AJAX call error and throws parsererror was created by Eli Aschkenasy            
    
        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
    index.php?option=com_hexdata&view=profiles&task=load_columns&table=<tablename>&id=1&<token>=1&abase=1
returns the correct ul
Please Log in to join the conversation.