kmstirtz
Member
When I View en entry and add a note the note does not show in the View screen. It DOES appear in the MySQL db table (wp_rg_lead_notes). And it does get emailed if I select that option.
This is using WP 2.8.6 on Hostgator. No errors showing in error log.
I have another GF install - same setup also using WP 2.8.6 on Cartika that works fine.
Any ideas?
First thing I would check is are you running any kind of caching plugin? DB-Cache for instance? This can sometimes cache admin pages also which causes changes/updates to not be immediately apparent.
kmstirtz
Member
no - I have never used an cache plugins on the admin side.
The same problem occurs with all forms on this domain and one other I have with HostGator. All forms hosted on the other domain, with Cartika, do not have this problem.
Can you get us a WordPress login to this site via our Contact Us form so we can take a look?
I will be in touch later on Friday with additional details.
We are going to need you to test a query in PHPMyAdmin. What is happening is your MySQL database is not returning the results for the select query that is used to display Notes.
It's highly unusual and nobody else has reported anything remotely similar to this issue.
kmstirtz
Member
Carl - maybe you have this already...but here is an error the tech guys at HG found:
[Fri Jan 15 08:25:44 2010] [error] [client 216.110.94.227] WordPress database error Illegal mix of collations (utf8_unicode_ci,IMPLICIT) and (utf8_general_ci,IMPLICIT) for operation 'ifnull' for query SELECT n.id, n.user_id, n.date_created, n.value, ifnull(u.display_name,n.user_name) as user_name, u.user_email, referer: http://http://amazingserviceu.com/as/wp-admin/admin.php?page=gf_entries
Thanks for your help!
KS
kmstirtz
Member
correction - should be:
[Fri Jan 15 08:25:44 2010] [error] [client 216.110.94.227] WordPress database error Illegal mix of collations (utf8_unicode_ci,IMPLICIT) and (utf8_general_ci,IMPLICIT) for operation 'ifnull' for query SELECT n.id, n.user_id, n.date_created, n.value, ifnull(u.display_name,n.user_name) as user_name, u.user_email, referer: http://amazingserviceu.com/as/wp-admin/admin.php?page=gf_entries
kmstirtz
Member
More complete error from HG (when they tried to enter a note in the View Entries screen):
[Thu Jan 14 07:06:45 2010] [error] [client 76.17.223.200] WordPress database error Illegal mix of collations (utf8_unicode_ci,IMPLICIT) and (utf8_general_ci,IMPLICIT) for operation 'ifnull' for query SELECT n.id, n.user_id, n.date_created, n.value, ifnull(u.display_name,n.user_name) as user_name, u.user_email\r, referer: http://amazingserviceu.com/asu/wp-admin/admin.php?page=gf_entries&view=entry&id=1&lid=2&paged=1
[Thu Jan 14 07:06:45 2010] [error] [client 76.17.223.200] FROM wp_rg_lead_notes n\r, referer: http://amazingserviceu.com/asu/wp-admin/admin.php?page=gf_entries&view=entry&id=1&lid=2&paged=1
[Thu Jan 14 07:06:45 2010] [error] [client 76.17.223.200] LEFT OUTER JOIN wp_users u ON n.user_id = u.id\r, referer: http://amazingserviceu.com/asu/wp-admin/admin.php?page=gf_entries&view=entry&id=1&lid=2&paged=1
[Thu Jan 14 07:06:45 2010] [error] [client 76.17.223.200] WHERE lead_id=2 made by do_action, call_user_func_array, RGForms->all_leads_page, GFEntryDetail->lead_detail_page, RGFormsModel->get_lead_notes, referer: http://amazingserviceu.com/asu/wp-admin/admin.php?page=gf_entries&view=entry&id=1&lid=2&paged=1
It looks like there is a difference in collation between the wp_users.display_name column and wp_rg_lead_notes.user_name column.
This probably was caused by the fact that Gravity Forms only specify the character set (utf8) when creating its tables and your server defaults to something that is different that WordPress' tables.
We will adjust our installation script so that the collation matches WordPress' tables. Meanwhile, you could change the collation on the wp_rg_lead_notes.user_name to match wp_users.display_name.
Assuming wp_users.display_name has the collation "utf8_general_ci" (please double check that), you can run the following command on your database:
ALTER TABLE wp_rg_lead_notes MODIFY
user_name VARCHAR(250)
CHARACTER SET utf8
COLLATE utf8_general_ciLet me know how it goes
kmstirtz
Member
My wp_rg_lead_notes.user_name field has utf8_general_ci as the collation but the wp_users.display_name has utf8_unicode_ci as the collation. So - are you saying I should change the wp_users.display_name field collation to utf8_general_ci ?
BTW - all my WP created tables have utf8_unicode_ci for their collation while, as you know, the rg tables are utf8_general_ci
However...
On my site hosted at Cartika, all the WP tables are utf8_latin_swedish_ci while the plugins, including rg, of course) are utf8_general_ci
Bottom line...
Matching the wp_rg_lead_notes.user_name collation and the wp_users.display_name collation (both using utf8_general_ci) worked - problem solved.
Thanks!
But - is it a problem having different collations in the other fields? (It would seem not but I'm no expert.)
We haven't encountered this issue before so I guess it is possible, although with such a large number of users using Gravity Forms over the 9 months (including beta testing and release versions) i'm sure if it was wider problem that this wouldn't have been the first time that this issue occurred.
We have made a change that will be introduced in the next release of Gravity Forms that forces any new tables to be created using the same collation as the WordPress install it is being activated on. This won't impact existing sites, but will curb the issue in new installs.