If you test it on your own demo site by signing up using the module on the homepage, the below is displayed. Even using the admin back-end to add users does not send out confirmation/subscription e-mails.

PDOException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '2' for key 'subscriber_uid': INSERT INTO {newsletter_subscriber} (uid, email, firstname, lastname, gender, receive_format, hash, confirmation_timestamp, created) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3, :db_insert_placeholder_4, :db_insert_placeholder_5, :db_insert_placeholder_6, :db_insert_placeholder_7, :db_insert_placeholder_8); Array ( [:db_insert_placeholder_0] => 2 [:db_insert_placeholder_1] => matrix.bob@gmail.com [:db_insert_placeholder_2] => [:db_insert_placeholder_3] => [:db_insert_placeholder_4] => [:db_insert_placeholder_5] => html [:db_insert_placeholder_6] => 6IVEYh-EXqOvH2byGinlCmJpK_1Whe096RKnK57NSFk [:db_insert_placeholder_7] => 1320106008 [:db_insert_placeholder_8] => 1320106008 ) in drupal_write_record() (line 6868 of /home/welinuxg/public_html/rootatwc/d7/includes/common.inc).

Comments

ParisLiakos’s picture

Title: Subscribing gives a PDOException » Find a better way to fill out subscribers uid

I am sorry,i had totally forgot my demonstration site:P
About this bug,yes i ll work on it,i need to find out a more decent way to find the uid of the user subscribing to a newsletter

TahitiPetey’s picture

Sounds good, do you have an approximate timeline for when you think this problem will be resolved?

ParisLiakos’s picture

Doh i totally forgot about this one.it ll be ready tomorrow max

TahitiPetey’s picture

Awesome, sounds good. Does the latest Dev contain the changes?

ParisLiakos’s picture

Status: Active » Fixed

I have commited the fix.Once d.o generates the file you will able to download it and test it.
It ll take just a few hours.Thanks for reporting this and reminding me lol:)
cheers

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.