{"id":142380,"date":"2005-02-10T07:08:58","date_gmt":"2005-02-10T07:08:58","guid":{"rendered":"https:\/\/wordpress.org\/support\/topic\/fatcow-server-upgrade-and-wordpress\/"},"modified":"2016-08-18T19:32:38","modified_gmt":"2016-08-18T19:32:38","slug":"fatcow-server-upgrade-and-wordpress","status":"closed","type":"topic","link":"https:\/\/wordpress.org\/support\/topic\/fatcow-server-upgrade-and-wordpress\/","title":{"rendered":"Fatcow Server Upgrade and WordPress"},"content":{"rendered":"

If you have an account at Fatcow, you probably know that they are upgrading their servers. There are a few problems I ran into, that probably affect all other users as well. In short:<\/p>\n

— The server’s directory structure has changed. Update your file upload destination directory in the control panel.<\/p>\n

— wp-blog-header.php sets a “Last Modified” header, instead of “Last-Modified”. The new server doesn’t like that. You’ll get “500 Internal Server Error” responses if you try to access your RSS feeds.<\/p>\n

— One problem I haven’t been able to fix yet is with rewrites. The new server forces a browser redirect, which puts all the PHP junk into the address bar.<\/p>\n

For a bit more detail, take a look at my blog under Fatcow Server Upgrade and WordPress<\/a>.<\/p>\n","protected":false},"template":"","class_list":["post-142380","topic","type-topic","status-closed","hentry"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/142380","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic"}],"about":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/types\/topic"}],"version-history":[{"count":0,"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/142380\/revisions"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/media?parent=142380"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}