<..> >> because the default pub changed and I couldn't figure out what to copy >> from it to our new pubs that were originally based on it. Am I going to have the same problem in 1.2.3?
> it should be a smooth ride. the only thing you have to do to my knowledge is to replace all occurences of text-utf8 serializers with text and xhtml-iso-8859-1 with xhtml in your publication sitemaps Thanks for the tip ;) I checked my sitemaps and saw no such occurences. Then I backed up my 1.2.2 installation, moved 1.2.2 aside and dropped a fresh built 1.2.3 in place. I copied my 1.2.2 publications into the 1.2.3 pubs directory and fired the system up - everything is there and everything works. Nice. Then, just for fun I backed up 1.2.3, put 1.2.2 back in place, and then simply copied the fresh 1.2.3 build over 1.2.2, that did NOT work. So I put the working copy of 1.2.3 back in place and things are good. To review: I was able to copy 1.2.2 publications into a fresh 1.2.3 install and everything worked. Unpacking the 1.2.3 build directly over the 1.2.2 installation did not work. - Steve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
