So I have a fresh install working of MT5 on a 1and1 server (fixed the Image::Magick issue by switching to GD). I was quite happy until I attempted to post a test comment on one of the child blog posts. When I do it directs me to an error page that says:
An error occurred
Unknown encoding: euc-jp
The comment DOES post, but the error page continuously comes up and it does not forward to the comment validation page.
I have tried creating a new blog with the current settings and it does the same thing.
There is literally no one else that has had this issue on any forum I've searched so I'm really hoping to get some help! Thanks!
Reported on Movable Type 5
I'm not using mt 5 but this link is about your issue: PublishCharset
Thanks for responding
I went ahead and switched it over to Shift_JIS
However, now I'm getting a 500 error whenever i post
It (again) still does post the comment, but i get the 500 error as soon as I hit submit
any ideas?
im now getting the 500 error when posting blog posts as well
ill try some other character sets, but im at a loss here
Your best friend now might be the MT doc search engine: Universal Movable Type reference search
thanks for your help
unfortunately i still cannot find anything that really addresses my current issue
i really do appreciate your response though
okay figured it out
for some reason I had to disable zemanta
dunno why this was but as soon as it was off everything started working correctly
Thanks for letting us know what the problem was. We don't have/use Zemanta, don't intend to.
I should also notate here (for anyone else that is having a similar issue as I was) that I was unable to get Movable Type Professional working on 1&1.
When I had my initial problem with the encoding error, i WAS using MTOS - this was in fact solved by disabling Zemanta.
HOWEVER in the process of attempting to find the problem, I did a fresh install of MT professional (also version 5).
From the start, I received 500 errors both within the console and when executing perl functions on the pages themselves (commenting etc).
This was solved by going back to MTOS.
In short, 1&1 did not like MT Professional 5.03.
MTOS 5.03 works fine when Zemanta is disabled.
Among my customers' editors, very few like zemanta. That is under 5% and thus I normally either take it off or disable it from the movable type installation.
However, the issue with 1&1 is mainly related to the fact that they are not sharing enough resources to handle MT Pro. You would be surprized to see, that depending on the server load, sometimes MT Pro would work. But also, that sometimes, due to the same issue, MTOS won't work :)
The solution is to leave 1&1 and host with a more professional hosting provider which allows more resources to its shared accounts.
Kind Regards,
Mihai Bocsaru
----------------------------------
Daily Movable Type Consultant
Web Development
Movable Type Consulting
Six Apart Partner
http://www.pro-it-service.com/
----------------------------------
Movable Type Demo
http://www.movabletypedemo.org/
----------------------------------
Open Melody Demo
http://www.openmelodydemo.org/
.