Taxonomy autocomplete produces Invalid multibyte sequences and PDO errors

This is not critical

@Hurukan,

This is not the same bug as #987472: search.module doesn't consistently support multibyte characters. It is the same error message though. That is why the patch from 987472 didn't fix your problem.

I generated 1000 test terms full of random French accent characters, and autocomplete still worked fine for me when adding new nodes and autocompleting.

So, we will need your actual taxonomy terms that are failing. Can you list all the terms here? Or, can you link to a MySQL Database Export of your taxonomy tables? (taxonomy_index, taxonomy_term_data, taxonomy_term_hierarchy and taxonomy_vocabulary)?

Once we have the actual terms that are failing, we should be able to reproduce it and find the problem.

Please don't change the version and priority. Thanks!

Moving to support request unless we can get some global steps to reproduce the issue. Maybe someone can test with the dump from #5 to check if it is instead an environment problem, since @damien_vancouver wasn't able to reproduce it.

Er.

The issue is reported (but not confirmed) in 7.12. An 8.x-dev tag doesn't make sense.

@Hurukan,

thanks for the SQL extract. I loaded your taxonomy tables on my test database and I still wasn't able to reproduce the problem - see attached screenshot of it working for me. I tried autocompleting with every letter, A through Z, and then also as a regular user instead of the admin uid=1 user. Your data looks fine in the tables, so we've at least ruled out that the problem is corrupt data in MySQL.

So.... something to do with your other enabled modules must be causing the problem to occur.

Based on the difficulty we had locating one of these bugs in #987472, I think the easiest way to proceed would be for you to send me a complete database dump to test with. I'll send you an email via your contact form, so you can send that to me directly, rather than post the entire thing on here.

As soon as I can see the error here on my dev server, then I can use XDebug to figure out exactly where the bad data is occurring very quickly. Unfortunately, the error message we get occurs much later than the actual bug, which is why we have to do all this to find the real source of the problem.

If you can't share the database with me, I can explain the troubleshooting steps for you to try yourself, with either XDebug, PHP error logging, or watchdog logging.

Unfortunately, until we can reproduce it, we can't fix it. But we are making progress!

@Hurukan,

I took a look at your database, and autocomplete was broken for me adding articles. PHP errors were showing in the status log. Trying to save with a typed in term got a different error than you, a PDO SQL error, not the error described here.

But in testing, I found something weird on your field_tags Term Reference field which is on the Article content type. I made a new taxonomy, but I was unable to point the field_tags at it, because the Vocabulary dropdown was greyed out. When I tried adding a second Term Reference field to the Article content type, it also had a greyed out dropdown. Whe I deleted field_tags, everything started working.

So, try this, I think it will fix your problem: Just delete the old field_tags and make a new one to use, named the same thing. This will delete any terms you have saved in the database, if you have any you were able to save.

1) backup your database
2) in structure->content types->article, go to the Manage Fields tab. Delete the field_tags (Mots-clés)
3) Create a new field to replace it the same: ADd a new field, field_mots_cles , field type Term Reference, Widget Autcomplete Term Widget (tagging)
4) select Indicateurs as the vocabulary on the next screen, Number of values to unlimited the screen after that, and save.

Now, go and try and add an article, and try the autocomplete and saving it. It should work.

So.. that will fix your problem, but it doesn't explain it or the errors really.

My guess right now is somewhere along the way something got corrupted in your database. If the above fixes your problem, and nobody else reports this bug, then that's probably all it was.

Let me know if the above works for you.

same issue: #393538: Document that check_plain() can issue PHP messages on invalid UTF-8 input