Dec 17th, 2011, 12:33 PM
Hi Kirpi,
Thanks for the post! And sorry you're having trouble. Yes, I logged that as a bug a long while back, but it's such a fringe case I seem to have focused on other things.
To be perfectly honest, if I were to "fix" it, I'd just update the installation script to detect for this, then prevent the installation from continuing. Obviously that's not a fix, but at least it'll be clear what's going on and not throw that awful error you saw.
At this stage, other than updating your database the only fix *is* to hack the code, to remove all references. This is kind of crumby because you'd run into trouble whenever you upgrade, plus most modules may well need to be edited as well. And in the case of the premium modules, you may find you can't install them at all (because the installation code is obfuscated).
Any chance your hosting provider would be willing to add that charset? You could tell them it's *very* standard now.
Sorry I couldn't be more help.
- Ben
Thanks for the post! And sorry you're having trouble. Yes, I logged that as a bug a long while back, but it's such a fringe case I seem to have focused on other things.
To be perfectly honest, if I were to "fix" it, I'd just update the installation script to detect for this, then prevent the installation from continuing. Obviously that's not a fix, but at least it'll be clear what's going on and not throw that awful error you saw.
At this stage, other than updating your database the only fix *is* to hack the code, to remove all references. This is kind of crumby because you'd run into trouble whenever you upgrade, plus most modules may well need to be edited as well. And in the case of the premium modules, you may find you can't install them at all (because the installation code is obfuscated).
Any chance your hosting provider would be willing to add that charset? You could tell them it's *very* standard now.
Sorry I couldn't be more help.
- Ben