I have my website at livingdot.com, so they handle MT upgrades for me (which is very nice, I must say). Currently running 3.2 without a problem, upgraded from 3.0.
This current issue started when I installed MTAmazon32 and Media Manager, and began to try to sort out why I couldn't get it to work. In various places I read that I should be sure that my config file was up-to-date. For example, on a best practices page called (appropriate enough) upgrading config file this paragraph:
QUOTE
The config file (mt-config.cgi) has come a long way in the past three years and is upgraded and tweaked in nearly every release. New directives have been added, some removed and documentation inside the config file is specifically tailored to the latest version which you are now running.
Reading through that page, I find myself more confused that i was to start with. So some basic questions:
1. From this article I gather than even if my config file is out of date, 3.2 may be working for me, albeit in a diminished capacity (for example, this may be part of the reason I can't get Media Manager to work). How do I know which config file version I've got, and what it is (or isn't) doing?
2. Assume for a moment I figure out that I don't have the most recent config file, and need to upgrade. Where do I find a copy of the most recent mt-config.cgi file?
3. How do I integrate the parts of the config file I've got now (which clearly work) with the newer parts of the revised, improved, gotta have it config file? That is, is there a version of this document: configuring the system that addresses the transition from one config file to another?
4. Can I pay somebody to (a) figure all this out for me; (b) fix it; © make media manager work? Or should I just forget the whole thing and hobble down the road with my possibly outdated but up to now adequate config file. Or is there a solution that falls between these two extremes?
