CiviCRM Community Forums (archive)

Hello,

I don't know if the translation 3. Mailing Content is right. I use an installation with german translation.

Yesterday planning ans sending a test mail worked fine.
To day I tried to delete a group an got a very ugly error. After Error 500 of the webserver popped up, I tried to reenter the page and got the error message:

----------
Error
The website encountered an unexpected error. Please try again later.
Error message
PDOException: SQLSTATE[HY000] [2002] Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2) in lock_may_be_available() (line 165 of /var/www/virtual/myhost.tld/htdocs/includes/lock.inc).
----------

I had to restart the server, because this message was shown in every website hosted on this server.

After restart, everything worked fine and I tried to go on testing the mailing function. So I reopened the old mailing, changed things in its content and tried to go beyond step 3. But from now on, saving of content is impossible, even with new mailings.
When clicking on 'next' or 'save mailing' a page occures (my german to english translation):

----------
Sorry. A  non-correctable error occurred.
An unexpected error occurred. Please post a detailed description of this error and it's sequence in the appropriate CiviCRM forum: http://forum.civicrm.org/

Back to Frontpage.
----------

This message takes up the whole screen and isn't part of the theme.

Does anybody know what this could be?

My environement:
Drupal 7 with CiviCRM 4.0 in two different databases
mysql  Ver 14.12 Distrib 5.0.51a, for debian lenny
PHP 5.2.6-1+lenny10 with Suhosin-Patch 0.9.6.2 (cli)
Apache/2.2.9 (Debian)

Merci Xavier,

her comes the log

--------------------
backTrace

/var/www/virtual/myhost.tld/htdocs/sites/all/modules/civicrm/CRM/Core/Error.php, backtrace, 291
/var/www/virtual/myhost.tld/htdocs/sites/all/modules/civicrm/CRM/Core/DAO.php, fatal, 710
/var/www/virtual/myhost.tld/htdocs/sites/all/modules/civicrm/CRM/Contact/BAO/Contact/Utils.php, getFieldValue, 143
/var/www/virtual/myhost.tld/htdocs/sites/all/modules/civicrm/CRM/Utils/Token.php, generateChecksum, 570
/var/www/virtual/myhost.tld/htdocs/sites/all/modules/civicrm/CRM/Utils/Token.php(543) : regexp code, getContactTokenReplacement, 1
/var/www/virtual/myhost.tld/htdocs/sites/all/modules/civicrm/CRM/Utils/Token.php, preg_replace, 543
/var/www/virtual/myhost.tld/htdocs/sites/all/modules/civicrm/CRM/Mailing/Form/Upload.php, replaceContactTokens, 579
, formRule,
/var/www/virtual/myhost.tld/htdocs/sites/all/modules/civicrm/packages/HTML/QuickForm.php, call_user_func, 1597
/var/www/virtual/myhost.tld/htdocs/sites/all/modules/civicrm/CRM/Core/Form.php, validate, 293
/var/www/virtual/myhost.tld/htdocs/sites/all/modules/civicrm/CRM/Core/QuickForm/Action/Upload.php, validate, 137
/var/www/virtual/myhost.tld/htdocs/sites/all/modules/civicrm/CRM/Core/QuickForm/Action/Upload.php, realPerform, 130
/var/www/virtual/myhost.tld/htdocs/sites/all/modules/civicrm/packages/HTML/QuickForm/Controller.php, perform, 203
/var/www/virtual/myhost.tld/htdocs/sites/all/modules/civicrm/packages/HTML/QuickForm/Page.php, handle, 103
/var/www/virtual/myhost.tld/htdocs/sites/all/modules/civicrm/CRM/Core/Controller.php, handle, 284
/var/www/virtual/myhost.tld/htdocs/sites/all/modules/civicrm/CRM/Core/Invoke.php, run, 224
/var/www/virtual/myhost.tld/htdocs/sites/all/modules/civicrm/drupal/civicrm.module, invoke, 385
, civicrm_invoke,
/var/www/virtual/myhost.tld/htdocs/includes/menu.inc, call_user_func_array, 501
/var/www/virtual/myhost.tld/htdocs/index.php, menu_execute_active_handler, 22
--------------------


And finally I found out what caused the problem.
With line #4 of the log (.../modules/civicrm/CRM/Utils/Token.php, generateChecksum), my guess was the newly included token {contact.checksum} caused it. I removed it from the footer and in the end I was able to save the mailing.

But what is the real cause of this issue? Something missing or an issue of the checksum generator?

what version r u on? I think this has been fixed for 4.0.1 (pretty sure it has been fixed in svn), but i think the fix was shipped with 3.4.1 / 4.0.1

lobo