CiviCRM Community Forums (archive)

Hi,

Just installed version 3.1.1 on drupal 6.15. All is well, except when I click on "New Email" under the "Contacts" menu, I get a blank page at the following url:

http://lascelles.us/crm/civicrm/activity/add&atype=3&action=add&reset=1&context=standalone

The same happen for New Activity, but not any other functions. Any help would be greatly appreciated.

Thanks! 

Thanks,

Here is the error log:

[Thu Feb 04 13:51:48 2010] [error] [client 70.254.36.166] PHP Fatal error: Call to undefined function json_encode() in /srv/www/vhosts/lascelles.us/httpdocs/crm/sites/all/modules/civicrm/CRM/Contact/Form/Task/EmailCommon.php on line 172, referer: http://lascelles.us/crm/civicrm/admin/tag&reset=1&action=add

Much appreciated

json support seems hit and miss, even if you have php 5.2 or newer. It seems php is often compiled without out is, such as on my opensuse 11.1 server.

Happily,  I found a decent workaround that worked for me:

1. Go to http://www.boutell.com/scripts/jsonwrapper.html and get the gzipped tarfile as indicated. The instructions on the boutell site were not super clear for newbies, so those below may help guide you.
2. Untar the file (get 7zip program if you need help untarring and extracting the file)
3. From the unzipped file, put the JSON folder and the two files jasonwrapper.php and jasonwrapper_inner.php into a new directory such as json_fix. Make a note of the root path of the jasonwrapper.php file e.g. /srv/www/vhosts/yourdomain.org/httpdocs/crm/json_fix/jsonwrapper.php
4. Add...     require_once '/srv/www/vhosts/yourdomain.org/httpdocs/crm/json_fix/jsonwrapper.php'; (replace with your domain and root path) ...to the top of the following files:
a) crm/sites/all/modules/civicrm/CRM/Contact/Form/Task/EmailCommon.php
b) crm/sites/all/modules/civicrm/CRM/Contact/Page/AJAX.php
c) crm/sites/all/modules/civicrm/CRM/Activity/Form/Activity.php
d) crm/sites/all/modules/civicrm/CRM/Admin/Form/MessageTemplates.php

or any others that give the same problem (as indicated by the error log on your server).

Hope this helps someone else needing a fairly simple, if not completely optimal, fix.

Yes, this is certainly not good practice for any production implementation. Please, nobody consider the hack above a real "solution".