Just upgraded to 2.2.13. But now I have the problem that I can't save TVs anymore. No matter what I input into the TV Name field, it always comes back invalid, saying: you have invalid characters in your template variable name.
I tried upgrade over 2.2.12, tried a complete new installation and I have always the same result.
Any insight?
Same problem here. I thought that I may have to do with database collations, Installed fresh installation of 2.2.13 around 5 times with different collations. but it doesn't help. Can't work like this.
Hey Alejandro,
Somehow my solution did not get posted. I was upgrading my local server and with that also the php version upgraded to version 5.5.10. After downgrading to php version 5.4.x everything was working again fine. So it seems to be an issue with PHP version.
It is not very clear what the issue is. I installed newest version on new server, this time using utf general collation, it is working now. Still confused though.
what's the php version on your server?
I'm also being affected by this issue. No version I have access to works -- 5.3, 5.4, or 5.5.
I don't feel that the php version is the issue. It looks more like it is a database character set and collation selection that triggers this problem.
I have a couple of installs, I have a php 5.3.27, it works fine, the db character set is set to utf8_general_ci. I have a second one that has this problem, same php version, the character set is latin_swedish_ci.
Hmm -- I'm wondering what a fix could be. Can one change the character set and be good to go?
I'm wary of doing so, but I'm unsure of whether that wariness is founded or not.
First of all, this will check the entire DB for character set and collation mismatches (along with a lot of other integrity checks):
http://bobsguides.com/sitecheck-promo.html. You can also check yourself with PhpMyAdmin, though you'd have to check the database, all tables, and all fields that contain text.
Second, if there is a mismatch, it can cause a number of problems. See this for a fix:
http://bobsguides.com/convert-db-utf8.html
With me the problem existed on a fresh install with a fresh database using utf8_general_ci. So that can only be if MODX 2.2.13 is changing something on the character encoding in the database during the upgrade install, or it changes the way it character encodes data from the manager front-end and creates a mismatch with the database character set.
