Getting Media Manager to work on Windows
I have had several users report problems with Media Manager on Windows. My apologize, I don't typically test on Windows (obviously), so you guys are debugging the platform for me. In any event, I have pointed people to the following Movable Type Knowledge Base article with great success.
This particular KB article describes a situation when all other plugins work, and MT works, but when you access Media Manager, you get nothing.
If this does not solve your particular problem, please let me know.
Comments
I'm currently running a WP site at seanw.com, but at http://dev.seanw.com/ I'm checking out MT. I've used it in the past, but that was on a Linux system... this is Windows. It's been no real joy getting things working, let me tell you. :)
So, I've done the fix that you linked to, but I'm still seeing issues (CGI Error: The specified CGI application misbehaved by not returning a complete set of HTTP headers.). Has anyone gotten this to work on a Windows system yet?
Can't wait to try this out... looks great! -Sean
Posted by: Sean Williams | October 17, 2005 11:33 AM
I'm having the same issue with this plugin on Windows. The KBase article references solved my initial issue with MT itself giving that error message.... but nothing I have tried seems to fix the issue with the plugin.
Posted by: pmppk | October 17, 2005 5:53 PM
GOT IT WORKING!!
IIS on Windows does not support STDERR, so when the plugin tries to output debug messages to the error log windows outputs them to STDOUT instead. These messgaes precede the HTTP headers generated by the plugins, causing IIS to think the CGI did not provide any headers at all.
The way to fix this problem is to edit ALL of the .pm files in ./plugins/MediaManager/lib/MediaManager and make sure to set $DEBUG = 0;
Posted by: pmppk | October 19, 2005 6:56 PM
Excellent! Great find... This worked for me as well. The only other thing I had to do for the install to work was to manually set the path to my schema file (c:\inetpub\yada yada). Otherwise, running like a champ now!
Posted by: Sean Williams | October 20, 2005 5:05 AM
Ah yeah, forgot to mention that I needed to manually set that path as well. Glad I could help.
Posted by: pmppk | October 20, 2005 1:43 PM
Ok, another problem found now that I've had a chance to try things out. Hopefully I'm just missing some config setting somewhere, but I can't seem to find it if so.
Basically, all the URLs are messed up. It's almost like a "base URL" or something is not set right. When I go to the MediaManager page, then choose "Add an item to your queue" it sends me to /mt/plugins/MediaManager/%5Cmt%5Cplugins%5CMediaManager%5Cmmanager.cgi?_mode=search&blogid=1
The %5C is a forward slash, so it is essentially sending me here: /mt/plugins/MediaManager/\mt\plugins\MediaManager\mmanager.cgi?_mode=search&blogid=1
See how it's adding the path to the URL? Is there a setting somewhere I'm missing?
Thanks! -Sean
Posted by: Sean Williams | October 21, 2005 7:07 PM
I was able to successful manually edit the install.pm file to direct to the schema file. And successfully installed media manager. I changed line 101, and it worked great. But now I have the exact problem that Sean Williams has.
"all the URLs are messed up. It's almost like a "base URL" or something is not set right. When I go to the MediaManager page, then choose "Add an item to your queue" it sends me to /mt/plugins/MediaManager/%5Cmt%5Cplugins%5CMediaManager%5Cmmanager.cgi?_mode=search&blogid=1
The %5C is a forward slash, so it is essentially sending me here: /mt/plugins/MediaManager/\mt\plugins\MediaManager\mmanager.cgi?_mode=search&blogid=1"
Has there been a way to fix this yet?
Posted by: mollycase | November 25, 2005 2:59 PM
Hey byrne,
Any fixes for the above issue yet?
Posted by: mollycase | December 17, 2005 9:28 PM