MTCS has changed quite a bit since I last worked with it. Oddly enough, my one and only post on the subject stirred up the MT-hating Internets. Well I have news for them: pretty much all my complaints have been addressed. MTCS is now MT Pro. For one, it is a heck of a lot cheaper for the 5 user/5000 profile license (as in, 1/3rd the coin) and is a much more robust toolset.
For starters, MTCS did not seem to grow on the same branch (sorry, programming joke). It lacked many, many nice additions MT 4.1 had. The latest and greatest version of MTCS I had installed actually was from the MT 4.02a code base, Even though it said MT 4.1 CP 1.5, PP 1.1.
Now we have feature parity, thank god.
While MTCS did hit a good update to be in line with MT 4.1, I had abandon it. Not because it was unusable, but because the project was (I thought) moving in a different direction.
But here we are, first week of September, and I am back working in MTCS, now MT Pro, sporting a much updated Community Pack 1.6. Why am I back here? Well, that's an easy one. Our partner College Publisher/mtvU told us in March that they would be able to handle all the community features inside their brand new CP5 platform. No, actually, they cannot. I found that out about a week ago when I asked where the community features were in the Polopoly interface.
Therefore, MT Pro is going to handle our Community Blogs and Forums, and MTOS is going to handle our individual blogs. Which is what I started working on six months ago.
Not exactly pleased about the fact that I could have had three more months to have worked on this project.
For starters, MTCS did not seem to grow on the same branch (sorry, programming joke). It lacked many, many nice additions MT 4.1 had. The latest and greatest version of MTCS I had installed actually was from the MT 4.02a code base, Even though it said MT 4.1 CP 1.5, PP 1.1.
Now we have feature parity, thank god.
While MTCS did hit a good update to be in line with MT 4.1, I had abandon it. Not because it was unusable, but because the project was (I thought) moving in a different direction.
But here we are, first week of September, and I am back working in MTCS, now MT Pro, sporting a much updated Community Pack 1.6. Why am I back here? Well, that's an easy one. Our partner College Publisher/mtvU told us in March that they would be able to handle all the community features inside their brand new CP5 platform. No, actually, they cannot. I found that out about a week ago when I asked where the community features were in the Polopoly interface.
Therefore, MT Pro is going to handle our Community Blogs and Forums, and MTOS is going to handle our individual blogs. Which is what I started working on six months ago.
Not exactly pleased about the fact that I could have had three more months to have worked on this project.
Leave a comment