Something inside me died a bit, but maybe now I can get over ideas shorter than a paragraph.
MS CMS 2001 Error trying to add file
I don’t like to post work stuff, but really there is no support left from MS CMS 2001 and I am sure there must be at least one other person out there that needs help with it.
After some searching we found that the KB944338 patch for Windows 2000 Server caused CMS 2001 to no longer support adding of files to the shared resources or be able to edit templates.
A simple uninstall of this one patch will restore functionality.
Migration Tip for MS CMS 2001 or MCMS 2002
OK, I generally don’t talk work here, but there is so little content on the web for MS CMS 2001 (or MCMS or Microsoft Content Management Server 2001/2002) that I felt I should post this migration tip for those that want to move to another system (it is 8 to 9 years old).
In Site Manager export all you content as a .ROP file. At first this seems like a useless binary file. In reality it is just a .CAB archive. You should select all your resources, channels, folders and templates when you export. The cab will then have your templates in plain text (.AEM), your files loose in the archive and a huge .XML of all of your content. Yay everything packaged up and ready to go.
Good luck with the rest!
ACIDity
Have been reading www.howtocreate.co.uk/acid. Interesting to note that IE 6 was the first browser to ever complete ACID 1 and that IE8 the first IE to pass ACID 2.
What is more interesting are these simple facts:
- Once the majority of current browsers pass the current ACID test a new one is created to challenge the existing browers (eg break)
- IE typically requires 2 versions to get there: IE3toIE4=beatNetscape, IE5toIE6=Acid1, IE7toIE8=ACID2.
- Safari is similar, but iterates more with around 3 versions
- Firefox is higher still around 4 versions (inc mozilla suite)
- Opera itterates to an insane degree. Opera 4 was ACID1 compliant, 9 was ACID2.
However not all is equal, IE used to iterate on a Safari/Firefox timetable, however MS stopped work when it was under investigation. So IE6to7 took AGES.
My predictions:
- IE9 will have some support for CSS3 and HTML. Odd numbered IE’s are typically ‘application’ releases that add support in a rough manner. Even are usually polish releases that make sure it hangs together tightly. IE10 will be the ACID3 release.
- Safari will benefit heavily from Apple’s trail blazing of CSS3 and the contribution from other webkit browsers (Chrome, thousands of mobile browsers)
- Firefox would continue at its own pace, but pressure from Safari and Chrome will keep it honest and in time.
- Opera will iterate like hell, will support ACID3 within a year or Saf/FF, whilst adding features no one will know they will want until they are in the other browsers
