Just did a deploy of a 4.7.1 in a clean folder. It worked fine in the testing environment and I am able to access the backend and publish all pages on the production server.
But when I access the site I only get a blank page saying:
Hi, I have the same error, but only for one page and it is set up a redirect via property. The rediret is not triggered, page should be there, because it is a content-node and published.
But I always get this strange error "Object moved to here.". The link here points to the same page
Don't know where the message is coming from. Where did you change your codee @Fengelz?
Seems to be solved, after republishing the page. BUT it was only possible, because my collegue didn't have the website in cache - for him the content page could be published WITH updating the cache. I did the same with no effect.
Object moved to here.
Just did a deploy of a 4.7.1 in a clean folder. It worked fine in the testing environment and I am able to access the backend and publish all pages on the production server.
But when I access the site I only get a blank page saying:
Object moved to here.
here being the link to the page itself. It doesnt matter if I enter a valid url like /home or /ewtwetwetewt. All I get is the above message.
Anybody have any idea what could cause this?
Best regards
- Sune
Ok found the error:
var prop = CurrentNode.GetProperty("externalRedirect");
if (prop != null && String.IsNullOrEmpty(prop.Value)) {
Response.BufferOutput = true;
Response.Redirect(prop.Value);
}
Stupid me.
- Sune
Hi, I have the same error, but only for one page and it is set up a redirect via property. The rediret is not triggered, page should be there, because it is a content-node and published. But I always get this strange error "Object moved to here.". The link here points to the same page
Don't know where the message is coming from. Where did you change your codee @Fengelz?
The page, which should be the redirected path, has this error: Oops: this document is published but is not in the cache
I am using Umbraco version 7.3.0
Seems to be solved, after republishing the page. BUT it was only possible, because my collegue didn't have the website in cache - for him the content page could be published WITH updating the cache. I did the same with no effect.
VERY STRANGE!
is working on a reply...