开发者

Odd Umbraco backend behavior after deployment

I've had this before, but can't seem to replicate the steps I did back then. I've got an Umbraco 4.5.2. site which is running on port 8084 in a development-environment. All works well.

When I want to publish the website to the production server, the umbraco-backend seems to want to keep using the port 8084 and therefor my backend (starting at login) is really strange. Can't seem to update any content (or anything else for that matter).

Now, I assume, it has something to do with caching of sorts, but what setting to change (or what to delete)?

This is my login-screen (no red border 开发者_如何学JAVAon erronous login)

Odd Umbraco backend behavior after deployment

And this is my back-end (there is content - i can see content in the front-end - just not visible in the content-tree);

Odd Umbraco backend behavior after deployment

This is my back-end on the development machine (did nothing but crude copy and edited the database connectionstring to match my production database).

Odd Umbraco backend behavior after deployment


How do you change the port number? I am assuming you're putting it into the hostname on the root item in umbraco content tree.

Have you tried republishing the entire site to make sure the published links do not contain the port number?

0

上一篇:

下一篇:

精彩评论

暂无评论...
验证码 换一张
取 消

最新问答

问答排行榜