Drupal/4.5: CRM.config.resourceBase is Undefined

[Lazlo Bakk]

I can see the source, but the referenced js file begins with the following:

Code: [Select]

<br />
<b>Warning</b>:  Invalid argument supplied for foreach() in <b>/home/biokshu1/public_html/administrator/components/com_civicrm/civicrm/CRM/Contact/BAO/ContactType.php</b> on line <b>142</b><br />
 // http://civicrm.org/licensing
// <script> Generated 08 Nov 2014 07:24:06The JS console in Firefox displays it as a syntax error.

The find contacts page begins with the same error message 15 times:

Code: [Select]

Warning: Invalid argument supplied for foreach() in /home/biokshu1/public_html/administrator/components/com_civicrm/civicrm/CRM/Contact/BAO/ContactType.php on line 142At localhost I don't have these problems, only after migration.

[Coleman Watts]

Ok this sounds like a minor bug in CiviCRM which we can and will address.
However I also think your php.ini settings are incorrect - these error messages should not be output on the page, especially not on a production server. Change your php settings to suppress errors and warnings, and your js problems will go away.

[Lazlo Bakk]

I'm glad to hear this. Please let me know in this topic when the bugfix is ready.
Well, the server is a shared hosting, my client insisted to use this noob hosting. I won't make this mistake again, I have the perfect hosting that runs CiviCRM without any problems on several websites I manage.

[Coleman Watts]

To clarify - this is something you need to address in your php.ini settings. We can fix this one notice, but can't possibly prevent every little notice and warning that php logs - it's up to you to make sure they are going to a log file rather than being output to the screen.

[Lazlo Bakk]

Well, after setting the display_errors value to off and after cleaning the cache, the weird js messages were gone and the arrows of the administration menu were appeared. But the site still have serious js errors as you can see the attached pictures.

[Coleman Watts]

I can see symptoms of errors in those screenshots, but it would be more helpful if you could show the actual errors that are in your browser's console.

[Lazlo Bakk]

Console in Firefox and Chrome shows no errors.