|
Home > Archive > Microsoft Content Management Server > August 2004 > Posting.URL = 404 Error, Posting.URLInner = ok
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Posting.URL = 404 Error, Posting.URLInner = ok
|
|
| Mark Reddick 2004-08-13, 5:51 pm |
| We are in the middle of upgrading our CMS 2001 framed site to a CMS 2002
non-framed site. I'm doing the conversion on a development machine right
now. Everything seems to be going great but today I just noticed something.
I have a template that shows "what's new" on the site. It lists all the new
posting for the past 3 days. I'm generating the links on this page using the
posting.Url property. I could have sworn this was working but today I
noticed that when I click one of these links, I get a "The page cannot be
found - HTTP Error 404 - File or directory not found" page. The URL it is
trying to go to is one of the nicely formatted ones, such as:
http://serverName/Yourtown/Informat...ams/Lap+Top.htm
This looks like a valid posting to me.
Out of curiousity, I changed the code to use the posting.UrlInner property
instead. The links work when I do this. I end up with the ugly links such
as:
http://serverName/NR/exeres/C4D95AF...E,frameless.htm
I'm unclear to what exactly the difference between the .URL and .URLINNER
properties are. We aren't using frames and we aren't using any rendering
scripts.
So, I guess my question is: Should the .URL property work for me? I'm
thinking it should and thus makes me think that there is some kind of
problem with my setup. I don't really want to go on with a possible problem
that may bite us in the butt down the road. If for some reason it makes
sense that this doesn't work, I'll just then known to use the URLINNER
property knowing there isn't an underlying problem.
Thanks,
Mark
| |
| Mark Reddick 2004-08-13, 5:51 pm |
| Hmm..I think I may have just figured it out. But, if anyone knows for sure,
please post so I'm sure.
I checked my channel properties and there is still values for the
"Navigation URL" property even though this is no longer used. It has a value
in there that was our navigation page before with our framed CMS 2001 site.
I tried to see if I can write a script to clear these values out but I
cannot find a property on the Posting object that contains this value. Does
anyone know if I can get at this value using a script (Publishing API)? We
have a ton of channels and it would be so much easier to be able to just run
a script than to manually go through each one to remove these values.
Thanks,
Mark
| |
| Stefan [MSFT] 2004-08-13, 5:51 pm |
| Hi Mark,
this property is deprecated and only there for compatibility with CMS 2001.
The only property exposed is the outerscript property but this is for the
channel rendering scripts - so I assume the navigation template it is not
exposed in the API.
You would have to clean it manually.
Cheers,
Stefan.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
MCMS FAQ:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...t+S
erver
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------
"Mark Reddick" <mark_reddick@NOSPAMlpsg.com> wrote in message
news:OzMu$pXgEHA.3728@TK2MSFTNGP10.phx.gbl...
> Hmm..I think I may have just figured it out. But, if anyone knows for
sure,
> please post so I'm sure.
>
> I checked my channel properties and there is still values for the
> "Navigation URL" property even though this is no longer used. It has a
value
> in there that was our navigation page before with our framed CMS 2001
site.
> I tried to see if I can write a script to clear these values out but I
> cannot find a property on the Posting object that contains this value.
Does
> anyone know if I can get at this value using a script (Publishing API)? We
> have a ton of channels and it would be so much easier to be able to just
run
> a script than to manually go through each one to remove these values.
>
> Thanks,
> Mark
>
>
|
|
|
|
|