I have an install of SugarCRM (version: 5.5.4) that isn't working 100%
I get an error message in some of the contact where the dashlets would be:
Line 3252 in SugarBean.php is related to the "retrieve_parent_fields($type_info)" function, more specifically the lines reads:Code:Warning: require_once() [function.require-once]: Filename cannot be empty in /var/www/crm/data/SugarBean.php on line 3252 Fatal error: require_once() [function.require]: Failed opening required '' (include_path='/var/www/crm/include/..:.:/usr/lib/php5') in /var/www/crm/data/SugarBean.php on line 3
Nothing in sugarcrm.log looked suspicious, not even a single [Fatal] line to show where the problem was.Code:if(empty($templates[$child_info['parent_type']])) { $class = $beanList[$child_info['parent_type']]; require_once($beanFiles[$class]); $templates[$child_info['parent_type']] = new $class(); }
I have modified the code (trying to find out what type of argument passed creates an empty call to "require_once"):
Which make the error go away, but doesn't actually solves the root of the problem. The log line I added produces this output:Code:if(empty($templates[$child_info['parent_type']])) { $class = $beanList[$child_info['parent_type']]; $GLOBALS['log']->debug("custom_out class: ".$class); $GLOBALS['log']->debug("custom_out child_info[parent_type]: ".$child_info['parent_type']); if(!empty($class)) { require_once($beanFiles[$class]); $templates[$child_info['parent_type']] = new $class(); } }
I'm not sure where to look for this "test" type. It's not in any "beanList" or "beanFile" in the files I "grep" up, yet it's mentioned somewhere because it produces the error message...Code:Mon Jan 17 17:16:32 2011 [2280][1][DEBUG] custom_out class: Account Mon Jan 17 17:16:32 2011 [2280][1][DEBUG] custom_out child_info[parent_type]: Accounts Mon Jan 17 17:16:32 2011 [2280][1][DEBUG] custom_out class: Mon Jan 17 17:16:32 2011 [2280][1][DEBUG] custom_out child_info[parent_type]: test
I have very little experience with SugarCRM or PHP. I'm not 100% sure what cause the problem, but nothing was ever modified outside of the Module Builder or the Studio. The code modifications I did to troubleshoot was in a local, VM-based install, a copy of our working installation. (We have valuable data in the production copy and I don't want to touch anything until I am 100% sure I have found the exact problem)
Any suggestions would be welcome...


LinkBack URL
About LinkBacks



Reply With Quote


Bookmarks