CiviCRM Community Forums (archive)

So I'm getting this on both an attempted upgrade and a completely fresh install and it was working just fine with the previous version.  (I know this is a cross-post. It happened with both an upgrade from J1.6.1 to 1.6.3 AND a fresh install of 1.6.3/4.0.1)

One of my clients started getting a smarty error with one of their event registrations, so I found a post on here where it was recommended that I clean the template_c folder out. I did, and started getting this error which completely crashes the Joomla backend:

Fatal error: preg_replace() [<a href='function.preg-replace'>function.preg-replace</a>]: Failed evaluating code: '{php' . str_repeat(&quot; &quot;, substr_count('{* Check for Status message for the page (stored in session-&gt;getStatus). Status is cleared on retrieval. *}', &quot; &quot;)) .'}' in /home/danetidw/public_html/novemberllc/jointcra/administrator/components/com_civicrm/civicrm/packages/Smarty/Smarty_Compiler.class.php on line 270

I thought it might be a problem with my installation, so I went and did a clean install of Joomla 1.6.3 and CiviCRM 4.0.1. Click on the civicrm menu item in the backend and it again completely crashes the Joomla admin backend with the same error.

It has to be something with CiviCRM as I've tried installing it in three different directories, all fresh installs, deleting everything unused on my server -- I've done everything I can possibly think of that might have been a server setup issue.

As it is, unless its a misconfiguration by my hosting company that I can't fix, the most recent version of Joomla with the CiviCRM component is completely useless.

Maybe a change in the template engine? Was there updated Smarty code added in the last update? I found a (not very) similar issue with another CMS and they tracked it down to an update to Smarty causing the error.

ok -- 60 topic views over on smarty.net and not one response. i don't think they're much interested in helping.  I also tried installing joomla/civicrm through normal methods (download, ftp, self-installer, installer for civi). The install went fine but clicking on "Configuration Checklist" or the Joomla Admin link and it errors out again.

I've tried this four different ways now and it doesn't work. I don't seem to be getting anywhere and my client's donation pages have been down for three days now with no solution or even ideas as to what the issue is.  I'm going to just have to switch to another system.

Thanks Lobo --

Strangely, it was the web host.  They upgraded the php security on my server. PHP 5.2.9 suhosin blocks the eval command so to rectify, your host has to allow a custom php.ini to be installed in each of the directories that CiviCRM is in.

I've attached mine as a txt file, but a2 said the code would probably depend on the provider.

Thanks Lobo --

Strangely, it was the web host.  They upgraded the php security on my server. PHP 5.2.9 suhosin blocks the eval command so to rectify, your host has to allow a custom php.ini to be installed in each of the directories that CiviCRM is in.

I've attached mine as a txt file, but a2 said the code would probably depend on the provider.

I am having this exact problem with CiviCRM 3.4 on Drupal 6 and my client's host is a2 as well.  I've tried using the php.ini you provided but it hasn't worked. I've tried putting it in the civicrm directory and in the directory the civicrm directory is in. Am I not putting this in the right place?

Also, I've looked at suhosin configuration instructions and it looks like you would need a directive like this:

suhosin.executor.disable_eval = false

But I don't see any mention of suhosin. I'm probably missing something because I am in a hurry (trying to launch my clients site asap).  Any more specific information on how this fixed it for you would be greatly appreciated.

I was also experiencing this same issue when upgrading from 3.4.0 to 3.4.1 on Drupal 6.22 on shared hosting provided by A2Hosting.

Somehow, somewhere along the line, my PHP version got switched from 5.3.4 to the default of 5.2.9 without my knowledge. I was able to easily install the php.ini file as suggested above, and discovered the version change and switched it back to 5.3.4. Everything seems hunky-dory now, after several days of pulling my hair out trying to get the upgrade to install and work correctly.

Thank you all for trouble-shooting, figuring out and providing the solution!

Thanks for your addition! I'm still novice enough that I wouldn't have realized that was a potential security risk, and I added your code to my .htaccess file. So happy when we're able to figure out the fix!