double subcription process

Use this forum for questions regarding adoption and functionality of OpenEMM

Moderator: moderator

marton
Posts: 36
Joined: Wed Aug 09, 2006 2:51 pm

double subcription process

Post by marton »

hi,

i just was updating our openemm 5.0.2 -> 5.1
1.then i was sending out some test-mailings: ok
2.afterwards i was testing our double-subscription form: error was appearing

our double subscription form is running since august 2006 without any problems. now the double subricption form doesn´t work anymore.
we´ve 8 input fields, one is mandatory (email address).

the only interesting error message i could found is the following (@ redirection_stdout.log)

======================================================
2007-06-17 21:01:21,432 - findByKeyColumn: Index: 0, Size: 0
2007-06-17 21:01:21,434 - Using dialect: org.hibernate.dialect.MySQLDialect
2007-06-17 21:01:21,434 - Using dialect: org.hibernate.dialect.MySQLDialect
2007-06-17 21:01:21,434 - Using dialect: org.hibernate.dialect.MySQLDialect
17.06 (21:01:21) RecipientImpl - updateInDB: creating new customer
2007-06-17 21:01:21,434 - updateInDB: creating new customer
2007-06-17 21:01:21,435 - Using dialect: org.hibernate.dialect.MySQLDialect
17.06 (21:01:21) RecipientImpl - new customerID: 85983
17.06 (21:01:21) RecipientImpl - insertNewCust: StatementCallback; bad SQL grammar [INSERT INTO customer_1_tbl (customer_id, gender, mailtype, byear, bmonth, creation_date, country, clicks_nr, email, bday) VALUES (85983, 2, 1, 0, 0, current_timestamp, 'please choose', , 'test@17062007.com', 0)]; nested exception is java.sql.SQLException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' 'test@17062007.com', 0)' at line 1
2007-06-17 21:01:21,437 - insertNewCust: StatementCallback; bad SQL grammar [INSERT INTO customer_1_tbl (customer_id, gender, mailtype, byear, bmonth, creation_date, country, clicks_nr, email, bday) VALUES (85983, 2, 1, 0, 0, current_timestamp, 'please choose', , 'test@17062007.com', 0)]; nested exception is java.sql.SQLException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' 'test@17062007.com', 0)' at line 1

17.06 (21:01:21) OpenSessionInViewFilter - Closing single Hibernate Session in OpenSessionInViewFilter
======================================================

is it necessary to change (downgrade?) the mysql-connector to solve this problem?

thanks in advance for any hint!

cheerio, marton
----
Fedora Core 5
OpenEMM 5.1
Java 1.5.0_07
MySQL v5.0.27
marton
Posts: 36
Joined: Wed Aug 09, 2006 2:51 pm

Post by marton »

hi,

i want to reinstall openemm 5.0.2.
i couldn´t find this version on sourceforge.net

you guys have any idea where i can find this version?

thanks in advance, marton
==============
Fedora Core 5
OpenEMM 5.1
Java 1.5.0_07
MySQL v5.0.27
ar
Posts: 5
Joined: Wed Oct 11, 2006 9:28 am

Post by ar »

hi marton,

it seems like the value for clicks_nr is not passed correctly. After some testing with different settings for this field I could still not reproduce the error. Taken from the error message it might help to set a default value for the clicks_nr field, though. To achive this you can delete the clicks_nr field and add it again with default value 0. This method will delete the existing values, though. To keep the existing values you can use the following procedure:

1. Open a Terminal on the OpenEMM Server.
2. Start the mysql client:
  • mysql -h localhost -u agnitas -p openemm
3. Enter the password: openemm
4. Execute the statement:
  • update customer_field_tbl set default_value = '0' where col_name = 'clicks_nr';
5. The reply from mysql should be:
  • Query OK, 1 row affected (0.00 sec)
  • Rows matched: 1 Changed: 1 Warnings: 0
6. Leave mysql with quit and close the Terminal.

I hope this helps,
ar
marton
Posts: 36
Joined: Wed Aug 09, 2006 2:51 pm

Post by marton »

hi,

thank you very much for your answer.

i just was updating the customer_field_tbl with default_value = '0'...
...now everything is working fine with our double opt in and i´ve got no more exceptions in my logs.


thanks again!
marton
Post Reply