I am trying to set up the blog document type and I am having an issue with the actual blog posts themselves ...
When I create a blog post item then it is nicely shown on the blogs overview page ... but then I click on the 'read more' link then I am ending up on my custom 404 handler page ...
When I look at the blog post item properties tab then I notice that the 'link to document' states : "This document is published but its url would collide with content (unknown)."
Hmmm ... weird huh ... is there somewhere some 'url rewriting' settings which collides with the '404' handler ?
There might be, although I'm curious why this is happening to you since it shouldn't return a 404, unless there's really a collision there.
I'm using Virtual Nodes (developed by yours truly too :) ): This essentially "wipes out" some parts of the url depending on the doctype. In the blog, it wipes the "posts" part. Try removing the <add key="virtualnode".... line from your web.config and see if you get the same result.
Hmmm weird ... the problem did not exist on my 'live' website ... only on my 'localhost' one ...
In fact I now noticed that almost all content nodes have this link to document "This document is published but its url would collide with content (unknown).".
I assume this is due to the 'virtual nodes' system you are using ... ?
As far as I remember, I've used VirtualNodes on localhost without issues. So maybe it's a naming problem, that is, when VirtualNodes is applied, some URL becomes a duplicate of an existing URL?
Blog Posts Issue
Hi,
I am trying to set up the blog document type and I am having an issue with the actual blog posts themselves ...
When I create a blog post item then it is nicely shown on the blogs overview page ... but then I click on the 'read more' link then I am ending up on my custom 404 handler page ...
When I look at the blog post item properties tab then I notice that the 'link to document' states : "This document is published but its url would collide with content (unknown)."
Hmmm ... weird huh ... is there somewhere some 'url rewriting' settings which collides with the '404' handler ?
Thanks,
Steven
There might be, although I'm curious why this is happening to you since it shouldn't return a 404, unless there's really a collision there.
I'm using Virtual Nodes (developed by yours truly too :) ): This essentially "wipes out" some parts of the url depending on the doctype. In the blog, it wipes the "posts" part. Try removing the
<add key="virtualnode"....line from your web.config and see if you get the same result.Hi Sotiris,
Thanks for your swift response ... unfortunately the last part of your reply got 'lost' ? So I am not sure what you want me to 'check' ...
Thanks,
Steven
I edited my response, sorry about that!
Hmmm weird ... the problem did not exist on my 'live' website ... only on my 'localhost' one ...
In fact I now noticed that almost all content nodes have this link to document "This document is published but its url would collide with content (unknown).".
I assume this is due to the 'virtual nodes' system you are using ... ?
Thanks,
Steven
As far as I remember, I've used VirtualNodes on localhost without issues. So maybe it's a naming problem, that is, when VirtualNodes is applied, some URL becomes a duplicate of an existing URL?
Hi Sotiris,
Not sure what happened ...
The issue 'disappeared' once I added the 'localhost' as DNS entry at the root of the site ... but I am sure it worked initially before doing that ...
Kr,
Steven
is working on a reply...