CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMail (Moderator: Piotr Szotkowski) »
  • Truncations in database tables (_mailing_event_queue, etc). What gives, eh?
Pages: [1]

Author Topic: Truncations in database tables (_mailing_event_queue, etc). What gives, eh?  (Read 1210 times)

tjcook

  • Guest
Truncations in database tables (_mailing_event_queue, etc). What gives, eh?
November 07, 2008, 08:13:47 pm
I sent a test mailing for Mailing A to Recipient A, then sent a full mailing of Mailing B thereafter.  Recipient A got the test mailing, and when she clicked on links (which were tracked), they went to pages for Mailing B. Anybody have advice for this mystery?

In short, Mailing A's tracked urls were somehow pointing to URLs assigned to Mailing B. The mailings were completely unrelated, and I'm afraid that if I now send out Mailing B, all links will be broken for Mailing A, which was sent to 5000+ people.

As another way of explaining:
I found a previous email in which the URLs DID work, and compared the tracking URLs of that email to the one that didn’t work. What I found is that some rows are missing from both of these tables above. In the case of mailing_trackable_url, all rows previous to id=190 are non-existent, then pockets of rows are gone (286-295, 302-320...).

The failing URLs are not finding one of the variables issued in the string and therefore are redirecting to the main page because that’s what the script tells them to do.

Specs:
CiviCRM 2.0.5.

I will post this to issues.civicrm.org if it appears somehow that this is a bug and not some weirdness in our config. Thanks all.

Piotr Szotkowski

  • Moderator
  • I live on this forum
  • *****
  • Posts: 1497
  • Karma: 57
Re: Truncations in database tables (_mailing_event_queue, etc). What gives, eh?
November 12, 2008, 04:14:35 am
Quote from: tjcook on November 07, 2008, 08:13:47 pm
I found a previous email in which the URLs DID work, and compared the tracking URLs of that email to the one that didn’t work. What I found is that some rows are missing from both of these tables above. In the case of mailing_trackable_url, all rows previous to id=190 are non-existent, then pockets of rows are gone (286-295, 302-320...).

The failing URLs are not finding one of the variables issued in the string and therefore are redirecting to the main page because that’s what the script tells them to do.
hanks all.

This is definitely the right track. If you could check whether this happens again (I’m aware that you’re anxious to do it on your production database, so maybe on a copy?) it would be most helpful.
If you found the above helpful, please consider helping us in return – you can even steer CiviCRM’s future and help us extend CiviCRM in ways useful to you.

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviMail (Moderator: Piotr Szotkowski) »
  • Truncations in database tables (_mailing_event_queue, etc). What gives, eh?

This forum was archived on 2017-11-26.