I have a brand new, fresh and clean install of MT - which was working perfectly fine last night when I installed it. Now today, suddenly, the Entry Editor window has gone blank - I cannot click in it at all.
Additionally, javascript errors are popping up all over the place. For example, in "Design>Templates" clicking on "Refresh Blog Templates" does nothing. Nor does "Use Publishing Profile".
After trying to select "Refresh Blog Templates", I took a look at the error console in Firefox, and see the following:
Error: uncaught exception: [Exception... "Security error" code: "1000" nsresult: "0x805303e8 (NSERRORDOMSECURITYERR)" location: "http://www.[mydomainname].com/cgi-bin/mt/mt.cgi?_mode=list&type=template&blog_id=1"]
As well as:
Error: updatePlugInAction is not defined Source file: http://www.[mydomainname].com/cgi-bin/mt/mt.cgi?_mode=list&type=template&blog_id=1
Error: doPlugInAction is not defined Source file: http://www.[mydomainname].com/cgi-bin/mt/mt.cgi?_mode=list&type=template&blog_id=1
HELP! I've tried reloading all the js files, checking the Static and CGI Path settings in mt.config to make sure they match the exact URL I access MT from, and deleting all my cookies/cache and refreshing.
Reported on Movable Type 4.2
When you first installed, were you accessing the site from http://www.[mydomainname].com/cgi-bin/mt/mt.cgi? Or from http://[mydomainname].com/cgi-bin/mt/mt.cgi? (Note the "www" difference.) Check mt-config.cgi to be sure you're going to the right URL.
I have always accessed it from: http://www.[mydomainname].com/cgi-bin/mt/mt.cgi
And, yes, - like I mentioned, I checked the mtconfig file, and that is the exact same URL for the Static Path.
I could (temporarily) fix the problem last night by deleting the mt.js file and overwriting it with a new one. But only for a few minutes. Then the problem reverted. Obviously, having to reupload the mt.js file every few minutes or so is not a viable solution to the problem.
There's some process or something that is causing the mt.js file to corrupt...
If something is overwriting mt.js inside the CMS, then you need to take that up with your host. I would check on the file's modification date, to see if something is actually overwriting it. The reason this is important is that the mt.js that is used for the CMS is not overwritten by the CMS. It's possible that a plugin or something else is creating problems.
Could you humor us by posting the values for CGIPath, StaticWebPath and the exact url that you are accessing?
It's not my host. I tried this on two separate hosting accounts, same problem.
I don't have any plugins - it's a fresh, clean install - so that's not the problem either.
CGIPath http://www.[mydomain].com/cgi-bin/mt/ StaticWebPath http://www.[mydomain].com/mt/ StaticFilePath /home/txdomer/public_html/mt/
Access at: http://www.[mydomain].com/cgi-bin/mt/mt.cgi Blog displays at: http://www.[mydomain].com/mt/
(txdomer is my account name at my host - so that's my account's root directory)
Annnnndddd... the line breaks didn't come through properly. Hope that info is still readable!
CGIPath http://www.[mydomain].com/cgi-bin/mt/
StaticWebPath http://www.[mydomain].com/mt/
StaticFilePath /home/txdomer/public_html/mt/
Access MT controls at: http://www.[mydomain].com/cgi-bin/mt/mt.cgi
Blog displays at: http://www.[mydomain].com/mt/
Annnnndddd... the line breaks didn't come through properly. Hope that info is still readable!
CGIPath http://www.[mydomain].com/cgi-bin/mt/
StaticWebPath http://www.[mydomain].com/mt/
StaticFilePath /home/txdomer/public_html/mt/
Access MT controls at: http://www.[mydomain].com/cgi-bin/mt/mt.cgi
Blog displays at: http://www.[mydomain].com/mt/
If this is the value you are using, unless you moved the contents of mt-static into your mt folder, this is your problem:
StaticWebPath http://www.[mydomain].com/mt/
That should read:
StaticWebPath http://www.[mydomain].com/mt/mt-static
Here's mine:
CGIPath http://www.codemonkeyramblings.com/mt/
StaticWebPath http://www.codemonkeyramblings.com/mt/mt-static/
There is no sub mt-static folder in the mt folder. All of the files contained in the mt-static folder from the download are in the mt folder.
For example, mt.js is located at:
http://www.[mydomain].com/mt/mt.js
I just tried this on a pretty fresh install of MTOS--I flattened mt-static and updated mt-config.cgi--and it worked for me. What you are seeing there is a browser security exception. What version of Firefox are you running, and what extensions do you have installed? Firefox is notorious for its heightened security in the last few releases.
Problem is: I get the same errors whether viewing MT from Firefox or Safari (on Mac) or Firefox or IE (on PC). Which is why I'm confused.
Here's what I've done for now:
Went in and disabled the mt.js file in the control panel, so that it does not publish statically with the other files. Completely deleted all of the .js files from the server, and re-upped all the files from the install zip. SO FAR, this appears to be working. For now. Perhaps the problem is that the mt.js file included with the standard templates is wrong (or incomplete), so when any file is published and the mt.js file that came with the install package is overriden with the mt.js file in the MT control panel... it's causing errors.
Of course, this is all likely to be proven wrong when it stops working again 15 minutes from now. But that's what I've been able to figure out.
This is your problem. You're overwriting the JavaScript file for your CMS everytime you rebuild. The two mt.js files are not interchangeable; they serve very different purposes. I'm guessing that you're publishing your blog into the same directory that you installed Movable Type. Publish to a separate directory after a fresh reinstallation of Movable Type and you should be set.
I'm confused.
I installed MT fresh, made no changes to the standard installation or settings. I selected my static directory on install as directed. Why in the world, then, would MT on its own default configuration overwrite necessary .js files? I didn't alter any settings or force it to publish any alternate way. So why is the default to overwrite necessary javascript?
So, in order to override the default, I need to manually go in and change publishing settings to alter where it publishes. So I need to now have three directories? One in the cgi-bin for the cgi scripts and attendant files, one static directory for the other necessary files... and a third directory to publish to? And how (and where) exactly do I go about changing the publishing to? I'm assuming I need to change the paths for each of the template files and also change the archive directories. What else needs to be changed from the default paths? I don't want to overlook something!
I think my confusion is largely colored by my past experiences. I have had MT since the 2.x days, and always published and kept my static files in the same directory. Sorry to be dense.
I'm confused.
I installed MT fresh, made no changes to the standard installation or settings. I selected my static directory on install as directed. Why in the world, then, would MT on its own default configuration overwrite necessary .js files? I didn't alter any settings or force it to publish any alternate way. So why is the default to overwrite necessary javascript?
So, in order to override the default, I need to manually go in and change publishing settings to alter where it publishes. So I need to now have three directories? One in the cgi-bin for the cgi scripts and attendant files, one static directory for the other necessary files... and a third directory to publish to? And how (and where) exactly do I go about changing the publishing to? I'm assuming I need to change the paths for each of the template files and also change the archive directories. What else needs to be changed from the default paths? I don't want to overlook something!
I think my confusion is largely colored by my past experiences. I have had MT since the 2.x days, and always published and kept my static files in the same directory. Sorry to be dense.
This is your problem. You're overwriting the JavaScript file for your CMS everytime you rebuild. The two mt.js files are not interchangeable; they serve very different purposes. I'm guessing that you're publishing your blog into the same directory that you installed Movable Type. Publish to a separate directory after a fresh reinstallation of Movable Type and you should be set.
Problem is: I get the same errors whether viewing MT from Firefox or Safari (on Mac) or Firefox or IE (on PC). Which is why I'm confused.
Here's what I've done for now:
Went in and disabled the mt.js file in the control panel, so that it does not publish statically with the other files. Completely deleted all of the .js files from the server, and re-upped all the files from the install zip. SO FAR, this appears to be working. For now. Perhaps the problem is that the mt.js file included with the standard templates is wrong (or incomplete), so when any file is published and the mt.js file that came with the install package is overriden with the mt.js file in the MT control panel... it's causing errors.
Of course, this is all likely to be proven wrong when it stops working again 15 minutes from now. But that's what I've been able to figure out.
I just tried this on a pretty fresh install of MTOS--I flattened mt-static and updated mt-config.cgi--and it worked for me. What you are seeing there is a browser security exception. What version of Firefox are you running, and what extensions do you have installed? Firefox is notorious for its heightened security in the last few releases.
There is no sub mt-static folder in the mt folder. All of the files contained in the mt-static folder from the download are in the mt folder.
For example, mt.js is located at:
http://www.[mydomain].com/mt/mt.js
If this is the value you are using, unless you moved the contents of mt-static into your mt folder, this is your problem:
StaticWebPath http://www.[mydomain].com/mt/
That should read:
StaticWebPath http://www.[mydomain].com/mt/mt-static
Here's mine:
CGIPath http://www.codemonkeyramblings.com/mt/
StaticWebPath http://www.codemonkeyramblings.com/mt/mt-static/
It's not my host. I tried this on two separate hosting accounts, same problem.
I don't have any plugins - it's a fresh, clean install - so that's not the problem either.
CGIPath http://www.[mydomain].com/cgi-bin/mt/ StaticWebPath http://www.[mydomain].com/mt/ StaticFilePath /home/txdomer/public_html/mt/
Access at: http://www.[mydomain].com/cgi-bin/mt/mt.cgi Blog displays at: http://www.[mydomain].com/mt/
(txdomer is my account name at my host - so that's my account's root directory)
If something is overwriting mt.js inside the CMS, then you need to take that up with your host. I would check on the file's modification date, to see if something is actually overwriting it. The reason this is important is that the mt.js that is used for the CMS is not overwritten by the CMS. It's possible that a plugin or something else is creating problems.
Could you humor us by posting the values for CGIPath, StaticWebPath and the exact url that you are accessing?
I have always accessed it from: http://www.[mydomainname].com/cgi-bin/mt/mt.cgi
And, yes, - like I mentioned, I checked the mtconfig file, and that is the exact same URL for the Static Path.
I could (temporarily) fix the problem last night by deleting the mt.js file and overwriting it with a new one. But only for a few minutes. Then the problem reverted. Obviously, having to reupload the mt.js file every few minutes or so is not a viable solution to the problem.
There's some process or something that is causing the mt.js file to corrupt...
And, because it always needs to be said: thanks to you both for trying to help!
Continuing this at the bottom for more readability.
I just went through the web-based installation for MTOS 4.21, and it never prompted me to give it a static web path, so I'm not sure what the deal is here.
Yeah, this sort of thing is a baaaaad practice since about 4.0 at least. Maybe 3.34; not sure, since I was using WordPress for most of 3.3's existence.
This should set you straight.
CGIPath /home/txdomer/publichtml/mt StaticWebPath /home/txdomer/publichtml/mt/mt-static
Set your blog's site root to:
/home/txdomer/publichtml/ or /home/txdomer/publichtml/blog/
I'm assuming that /home/txdomer/public_html/ is the root directory of your hosted domain.
If you're using FTP, get a good client like CuteFTP, Filezilla or NcFTP and upload the folder structure as-is from a zip or tarball of MTOS 4.21. Don't modify it. Upload it as the "mt" folder, and then just log into http://www.domain.com/mt/ and configure it that way. If you're serious about starting fresh, I'd kill the database, the existing file structure, everything.
If you're coming from 2.X, it's no wonder this is a shock for you, since so much has changed by the time you get to 4.21.
The reason you want mt-static separate is also because it'll make upgrading to future versions of MT a pain in the ass if you have to manually flatten mt-static into /mt/ everytime you upgrade.
Continuing this at the bottom for more readability.
I just went through the web-based installation for MTOS 4.21, and it never prompted me to give it a static web path, so I'm not sure what the deal is here.
Yeah, this sort of thing is a baaaaad practice since about 4.0 at least. Maybe 3.34; not sure, since I was using WordPress for most of 3.3's existence.
This should set you straight.
CGIPath /home/txdomer/publichtml/mt StaticWebPath /home/txdomer/publichtml/mt/mt-static
Set your blog's site root to:
/home/txdomer/publichtml/ or /home/txdomer/publichtml/blog/
I'm assuming that /home/txdomer/public_html/ is the root directory of your hosted domain.
If you're using FTP, get a good client like CuteFTP, Filezilla or NcFTP and upload the folder structure as-is from a zip or tarball of MTOS 4.21. Don't modify it. Upload it as the "mt" folder, and then just log into http://www.domain.com/mt/ and configure it that way. If you're serious about starting fresh, I'd kill the database, the existing file structure, everything.
If you're coming from 2.X, it's no wonder this is a shock for you, since so much has changed by the time you get to 4.21.
The reason you want mt-static separate is also because it'll make upgrading to future versions of MT a pain in the ass if you have to manually flatten mt-static into /mt/ everytime you upgrade.
As an example from my blog
CGIPath http://www.codemonkeyramblings.com/mt/
StaticWebPath http://www.codemonkeyramblings.com/mt/mt-static/
Then my blog's site root is listed as
/home/myusername/public_html/
for my main blog.
I have a themes blog hosted at codemonkeyramblings.com/themes
and the site root for that is
/home/myusername/public_html/themes/
As an example from my blog
CGIPath http://www.codemonkeyramblings.com/mt/
StaticWebPath http://www.codemonkeyramblings.com/mt/mt-static/
Then my blog's site root is listed as
/home/myusername/public_html/
for my main blog.
I have a themes blog hosted at codemonkeyramblings.com/themes
and the site root for that is
/home/myusername/public_html/themes/