I am in the process of migrating a MT3.3 site to an new server and a new domain name.
We have a custom application that is posting to the site over the ATOM interface. I have changed the Site URL and Site Root in Publishing Settings, and the site loads just fine at the new domain.
But, after authenticating on the ATOM interface, MT is returning all the expected feeds with the old domain, not the new domain.
I have tried rebuilding the indexes and the entire site, and neither solved the problem.
Is there a setting somewhere I'm missing?
Do I need to change this by hand?
Thanks!
Reported on Movable Type 3.x
I'm not sure about the ATOM interface, but I'm in the process of converting a site from 4.01 to 4.33 that uses Custom Fields. I could not get the images to convert automatically and so I've been looking at the database to do it manually. What I noticed is that many (most) items are hard coded in the d/b to the domain that was in use at the time the asset was added. It sounds like this is what is happening for you too.
Turns out I was making a pretty dense mistake - whoever setup this site had left two copies of mt-config.cgi, and I had updated the domain settings in one... the wrong one.
After fixing that, it seems pretty clear that MT gets the domain and path information for ATOM (and many other things) from mt-config.cgi. What I also learned - the domain/file path settings in blog=>settings=>publishing are of no use if the domain is wrong in mt-config.