I had posted a support thread over at the EE forums, and they finally tracked the problem down to the Tag module, and suggested that I file a bug report. Since the final conclusion they arrived at was over my head, I’m just going to link to the relevant thread:
I’m getting the same error with Tag 2.5. The extension apparently interferes with related entries in some way, and thus the Playa extension I also need to use… I narrowed down the conflict to the Tag Submit extension by careful disabling/re-enabling of extensions.
The thread talks about commenting out calls to _db_charset_switch in system/modules/tag/mod.tag.php as a short term fix, but I think I’d want to know exactly where to do that before I go mucking about in the Tag Submit extension.
I got a chance to install 2.5.1. today and upgrade to EE 1.6.5… I’m getting the same results as before :(
This is in conjunction with the Playa extension, however. I’ll have to test to see if it creates the same problems with regular related entries and reverse_related_entries.
I’ve upgraded to Tag 2.5.1 today and am getting this problem again as well. I say “again” because Robin Sowell had gone through the mod.tag.php file on my server and commented out the calls to the problematic _db_charset_switch function. Unfortunately, I upgraded to Tag 2.5.1 assuming that the problem would remain gone, and didn’t make a backup of the modified files…
Yup, that seems to have done it. Will that change will be integrated into Tag from now on? I shouldn’t have to worry about upgrading to future versions, right?
Sorry Pie Man, I missed the earlier forum notification for some reason. I just upgraded the site to Tag 2.6 though, and have the same problem—I turn Tag 2.6 off, and all is well with the multi-relationships that Playa sets up. It’s as if there’s some clearing of the relationship cache that happens automatically when you alter a relationship in any entry that doesn’t happen when Tag is present. Playa seems to rely on this cache being cleared. Or so I think.
When I get back to my sites in a few days, I’ll try to see what’s going on in the module code, and I’ll give you a PM with CP access with instructions on how to reproduce the error. Thanks again
OK, I updated to Tag 2.6 and it didn’t help. However, it looks like Brandon Kelly made the “relationship cache” flush itself properly when you add or alter a relationship, in the new update to Playa, the multi-relationships extension I’ve been using. For some reason, the cache would flush itself normally, but when Tag was enabled, it wouldn’t, and the related entry wouldn’t display properly.
But that’s not the case now — so my problem’s solved. (BTW, I would’ve loved to solve the problem with Related Entries, but it wasn’t quite right for the workflow we required). Thanks guys!