Collation problems
Posted: 16 Oct 2015, 17:15
Solutedns has a problem when mysql collation is case insensitive because for him the following domains will look the same (with mysql collation utf8_general_ci):
1-aeíóù.com
2-aeioù.com
3-aeiou.com
So when you activate solutedns for domain number 3, it will activate it for domain number one.
In the first place Solutedns shouldn't even go by the domain name but instead by the domain ID which would solve this problem, but if you have to keep looking up by domain name at least you could force the collation
Another solution is to change WHMCS database to use collation utf8_bin, but this can have other side effects I guess.
But I repeat, it would be much safer if all solutedns code was using IDs instead of domain names when activating domain or accessing it through client area.
1-aeíóù.com
2-aeioù.com
3-aeiou.com
So when you activate solutedns for domain number 3, it will activate it for domain number one.
In the first place Solutedns shouldn't even go by the domain name but instead by the domain ID which would solve this problem, but if you have to keep looking up by domain name at least you could force the collation
Another solution is to change WHMCS database to use collation utf8_bin, but this can have other side effects I guess.
But I repeat, it would be much safer if all solutedns code was using IDs instead of domain names when activating domain or accessing it through client area.