After upgrading to 5.13, people who were granted access as "commenter" (that is, their comment appeared without my moderation) report that they cannot comment anymore: they receive a message saying
Errore nell'invio del commento
Il tuo commento non è stato salvato per il seguente motivo:
La sesión ha caducado. Por favor, identifíquese de nuevo para comentar.
The first two lines are in Italian, and I wrote them in a template; they say "Error in sending comment. Your comment was not saved for the following reason"
The third line is in Spanish, and means 'Your session has expired. Please sign in again to comment.'
(I think that I got some error message in Spanish since version 2.x. I never understood why, since I installed it in English, but I never bothered to check what happens: usually an Italian person may grasp the meaning of a Spanish sentence)
The commenters tried to log out and log in again; they are actually logged, so it is not a password issue, but the problem remains. The permissions and profile seem also ok, btw.
Is the problem known? Do you have any idea, besides trying to disable the old names and recreate them?
TIA, .mau.
Reported on Movable Type 5
Hi .mau.,
I would assume that you've upgraded all the templates as per the details from the v5.13 release.
The error you are getting is related to the fact that your visitors have the 'mt.js' (which might be called 'mt-site.js') cached from before the upgrade.
What you could do is to either put a notice on your pages that they should erase their cache, or you could set the JavaScript index template to save the output as a new file (say "mt-new.js"), then call this new file name on your site pages and finally rebuild your site to reflect this change.
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/
Hi Mihai,
I just added the new configuration directive AllowFileInclude, as per http://www.movabletype.org/documentation/appendices/config-directives/allowfileinclude.html (and because I got an error and had to check why :-) )
I'll try and see what happens: there should be some other problem, since in rebuilding the blog I got an error
Premature end of script headers: mt.cgi
which means that some template has been corrupted.
Is there something in the apache error logs?
it is usually happen when I put a "print" statement inside the code (for debugging) and forget to specify "print STDERR"...
.mau., I am not guessing or supposing things.
The error that you've reported above is caused by what I've explained you above.
If you want to fix it, then follow my advice ;)
Cheers,
Mihai
Mihai, I am sure that there is a problem with mt.js. But it cannot be the only error present, since I also used a brand new machine, and as I wrote above I also have problems in rebuilding.
This just means that I will have to spend a night to check exactly what's happening and slowly rebuild my templates to find where the errors are. Just this.
If you need any further advice, let me know.