Hi!
I'm trying to open "Templates" in my 3.2 version of MT, but get the following error message:
"maketext doesn't know how to say: _SYSTEM_TEMPLATE_SEARCH_TEMPLATE as needed at lib/MT.pm line 855".
Any ideas what can be wrong and how I can fix it?
Regards
Kjell
Full Version: Can't Get Templates!
Weird!
I don't have a _SYSTEM_TEMPLATE_SEARCH_TEMPLATE defined in my lib/MT/L10N/en_us.pm for 3.2, but I do have it for 3.3b1.
Might you have gotten part of the files for the beta mixed in? When did you download the zip file?
Lisa
I don't have a _SYSTEM_TEMPLATE_SEARCH_TEMPLATE defined in my lib/MT/L10N/en_us.pm for 3.2, but I do have it for 3.3b1.
Might you have gotten part of the files for the beta mixed in? When did you download the zip file?
Lisa
I have the same message here. I made an upgrade from 3.2 to 3.31 and all went wrong, so I decided to make another installation of my weblog using the same DB upgraded in the 3.31 installation process.
Any idea?
Any idea?
Are you seeing that error in your 3.31 new installation or the upgraded one that wasn't very happy?
QUOTE (lisa @ Jul 27 2006, 08:54 PM) 
Are you seeing that error in your 3.31 new installation or the upgraded one that wasn't very happy?
I'm having the same problem. The 3.31 upgrade made things horribly slow so I went back to 3.2. Now in 3.2, when I click Templates I get this error:
maketext doesn't know how to say: _SYSTEM_TEMPLATE_SEARCH_TEMPLATE as needed at lib/MT.pm line 855
Any ideas?
Jodi opened a support ticket, so once we figure out the issue, we'll update this thread.
QUOTE (lisa @ Aug 2 2006, 08:27 PM)
Jodi opened a support ticket, so once we figure out the issue, we'll update this thread.
Any resolution to this problem? I just had this happen today. I tried re-uploading the lib and extlib directories in ascii mode, as mentioned in another thread, but I still get an error message: "maketext doesn't know how to say: _SYSTEM_TEMPLATE_SEARCH_TEMPLATE as needed at lib/MT.pm line 855".
I too have tried updating to update 3.31 but because of errors with the plugins i currently had installed (threadedcomments, scode, customfields, etc), i deleted the system and installed the backup i made (3.2) just prior to the update. I'm getting the same error code as described above.
Unfortunately i didn't backup the mysql database also. Could that be where the error's sourcing from?
If anyone has any updates regarding the downgrade or tips on plugin compatibility with the upgrade, please help me out. My blog is sitting dead until this can be resolved.
Unfortunately i didn't backup the mysql database also. Could that be where the error's sourcing from?
If anyone has any updates regarding the downgrade or tips on plugin compatibility with the upgrade, please help me out. My blog is sitting dead until this can be resolved.
I have the same problem as Jodi (I upgraded and then downgraded), and I've had it for a while already.
I also tried to upgrade again. This time to 3.32 and in that version I can access the templates, but whenever I try to rebuild any of the pages or post a new entry, I get a "500 Internal Server Error". I checked the server error log and it said there "error: file has no execute permission:" on mt.cgi and mt-comments.cgi files. I've checked it several times and both these files and mt-tb.cgi have permissions set to 755.
I don't get it.
I also tried to upgrade again. This time to 3.32 and in that version I can access the templates, but whenever I try to rebuild any of the pages or post a new entry, I get a "500 Internal Server Error". I checked the server error log and it said there "error: file has no execute permission:" on mt.cgi and mt-comments.cgi files. I've checked it several times and both these files and mt-tb.cgi have permissions set to 755.
I don't get it.
Jodi ended up reinstalling 3.3 and that got things working again.
Do you have a full backup for your database? Did you restore that before you went back to the 3.2 code?
Do you have a full backup for your database? Did you restore that before you went back to the 3.2 code?
I had no backup of my database before the first upgrade (I wasn't familiar with the service provider's backup-policy and thought they had it). I have a full backup now, but that won't help me anymore, will it? It's "corrupted" already.
With 3.32 I could access the templates, but could save and rebuild. Nor post entries, comments or trackbacks due to an "error: file has no execute permission". Could the problem be on the service provider's side and if so, what might cause it?
With 3.32 I could access the templates, but could save and rebuild. Nor post entries, comments or trackbacks due to an "error: file has no execute permission". Could the problem be on the service provider's side and if so, what might cause it?
You're going to have to stick with 3.32 in that case.
That's an odd error. It may be that your permissions were not right (all .cgi files should be set to 755). Does your webhost provide access to the web server error logs? If so, they may have more information about the errors you're seeing.
That's an odd error. It may be that your permissions were not right (all .cgi files should be set to 755). Does your webhost provide access to the web server error logs? If so, they may have more information about the errors you're seeing.
All .cgi files have been uploaded in ASCII mode and permissions have been set 755. Nevertheless I get the same error from the server and a 500 Internal Server Error upon posting new entries, saving old ones, rebuilding pages etc.. basically on all attempts to modify the HTML-pages.
The error message (no execute permission) was copied from the server error log. The log entry consists of the time of the error, the error message and indicates the file that generated the error. So no more information can be found there. I'll see if I can contact the server admin and get his comment on the error.
I was kinda hoping I wouldn't be the only/first one with that issue. Looks like a bad case of PEBCAK..
The error message (no execute permission) was copied from the server error log. The log entry consists of the time of the error, the error message and indicates the file that generated the error. So no more information can be found there. I'll see if I can contact the server admin and get his comment on the error.
I was kinda hoping I wouldn't be the only/first one with that issue. Looks like a bad case of PEBCAK..
For anyone coming to this thread looking for an answer here it is:
MT is completely unforgiving about system templates it doesn't have a translated name of. (This is a symptom of the localization libraries it uses that MT doesn't handle as gracefully as it probably should.) I learned this the hard way when I placed the default Tags.App results template under system. The first person that deactivated the plugin got a message like this.
The _SYSTEM_TEMPLATE_SEARCH_TEMPLATE error message seems to indicate that someone perhaps upgraded to 3.3 and then went back or didn't complete it. I had to help someone through this exact error message when they upgraded and tried to go back. Surprisingly this error was the first sign of trouble. I would have expected a more serious error sooner. Reading through the messages here that seems to be the case. The only safe way to go back is to restore the database from the backup you made before upgrading and recreating any data that may have been entered since the time of the backup.
If you are still running MT 3.2 (you shouldn't but...), In order to fix this problem you're going to have to go into the MT templates data table and find all occurrences of type = "search_template" and either switch the type to "custom" or delete them all together. That error message should ago away then. If you have upgraded to MT 3.3 and have this then somehow all of your MT files weren't updated that you have an outdated translation table in use.
Hope that helps put this one to rest.
MT is completely unforgiving about system templates it doesn't have a translated name of. (This is a symptom of the localization libraries it uses that MT doesn't handle as gracefully as it probably should.) I learned this the hard way when I placed the default Tags.App results template under system. The first person that deactivated the plugin got a message like this.
The _SYSTEM_TEMPLATE_SEARCH_TEMPLATE error message seems to indicate that someone perhaps upgraded to 3.3 and then went back or didn't complete it. I had to help someone through this exact error message when they upgraded and tried to go back. Surprisingly this error was the first sign of trouble. I would have expected a more serious error sooner. Reading through the messages here that seems to be the case. The only safe way to go back is to restore the database from the backup you made before upgrading and recreating any data that may have been entered since the time of the backup.
If you are still running MT 3.2 (you shouldn't but...), In order to fix this problem you're going to have to go into the MT templates data table and find all occurrences of type = "search_template" and either switch the type to "custom" or delete them all together. That error message should ago away then. If you have upgraded to MT 3.3 and have this then somehow all of your MT files weren't updated that you have an outdated translation table in use.
Hope that helps put this one to rest.
QUOTE (tima @ Mar 11 2007, 02:45 PM)
For anyone coming to this thread looking for an answer here it is:
MT is completely unforgiving about system templates it doesn't have a translated name of. (This is a symptom of the localization libraries it uses that MT doesn't handle as gracefully as it probably should.) I learned this the hard way when I placed the default Tags.App results template under system. The first person that deactivated the plugin got a message like this.
The _SYSTEM_TEMPLATE_SEARCH_TEMPLATE error message seems to indicate that someone perhaps upgraded to 3.3 and then went back or didn't complete it. I had to help someone through this exact error message when they upgraded and tried to go back. Surprisingly this error was the first sign of trouble. I would have expected a more serious error sooner. Reading through the messages here that seems to be the case. The only safe way to go back is to restore the database from the backup you made before upgrading and recreating any data that may have been entered since the time of the backup.
If you are still running MT 3.2 (you shouldn't but...), In order to fix this problem you're going to have to go into the MT templates data table and find all occurrences of type = "search_template" and either switch the type to "custom" or delete them all together. That error message should ago away then. If you have upgraded to MT 3.3 and have this then somehow all of your MT files weren't updated that you have an outdated translation table in use.
Hope that helps put this one to rest.
MT is completely unforgiving about system templates it doesn't have a translated name of. (This is a symptom of the localization libraries it uses that MT doesn't handle as gracefully as it probably should.) I learned this the hard way when I placed the default Tags.App results template under system. The first person that deactivated the plugin got a message like this.
The _SYSTEM_TEMPLATE_SEARCH_TEMPLATE error message seems to indicate that someone perhaps upgraded to 3.3 and then went back or didn't complete it. I had to help someone through this exact error message when they upgraded and tried to go back. Surprisingly this error was the first sign of trouble. I would have expected a more serious error sooner. Reading through the messages here that seems to be the case. The only safe way to go back is to restore the database from the backup you made before upgrading and recreating any data that may have been entered since the time of the backup.
If you are still running MT 3.2 (you shouldn't but...), In order to fix this problem you're going to have to go into the MT templates data table and find all occurrences of type = "search_template" and either switch the type to "custom" or delete them all together. That error message should ago away then. If you have upgraded to MT 3.3 and have this then somehow all of your MT files weren't updated that you have an outdated translation table in use.
Hope that helps put this one to rest.
Sorry this just happened to me and I didn't even try to upgrade, one day I tried going to my templates and I got the same message. Where is the MT templates data table? I can't seem to find it. Thanks appreciate any assistance.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.