nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Custom Menu link to support.interwoven.com

clogan

I have TS6.1 sp1 and have been trying to create a custom link to https://support.interwoven.com from one of my menus.

Here is a snippet from my ui_custom.xml file:

<iwov-ui>
<action-list ...>
<menu ...>

....

<link id="rd.rdadmin.tssupport.site.link"
label="Interwoven Support Site"
description="Link to Interwoven Support Site"
url="https://support.interwoven.com"
target="_blank">
</link>

....

</menu>
</actionlist>
</iwov>

The link appears, but when I click on it, I get a new window with a "HTTP 405 - Resource not allowed error" with the correct url in the window address field. I can take the same URL from the window with the error and paste into a new window to get the site to come up correctly.

I think it is funny that I can't link to the Interwoven support site from within Teamsite.

Does anyone know what I am doing wrong?

Thanks.

-Craig

Find more posts tagged with

Comments

gzevin

try it with just http, not https... Just thinking load.. have not tried myself

Greg Zevin, Ph.D. Comp. Sc.
Independent Interwoven Consultant/Architect
Sydney, AU

clogan

That is actually how I first tried it. I am thinking it might have to do with support.interwoven.com not allowing other sites to post to it or something like that.

Migrateduser

Hi Craig,

You might want to try using https://support.interwoven.com/supportlogin2.asp and see if that works. Teamsite could possibly be confused with a redirect we incorporate into the support site.

Hope that helps!
-Frank
Interwoven Support Site Administrator

Migrateduser

That seems strange, though... I was able to implement a similar link to the DevNet. Although the redirect you have for DevNet is different than that for the Support site (maybe the only difference is that one is written before headers are written out and the other, afterwards), why would the redirect throw a 405?

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K

Migrateduser

I agree it is strange. The link itself should work from what I'm seeing. A redirect and the SSL are the only mitigating factors I can see as possible causes from the support site side. Otherwise it's standard ASP.

-Frank

clogan

Linking to https://support.interwoven.com/supportlogin2.asp did the trick.

Thanks.

Migrateduser

Ok, so linking to support2.asp apparently did the trick.

Out of pure curiousity, why would the former not work? Does it have to do with the possible redirect before the headers are written (just an assumtion, of course I don't know what is generating the redirect)?

Dave

Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K

Migrateduser

Hi Dave,

I think that's correct. The redirection we perform would be before headers are written. It's a function we've set up in IIS not via a script in the page. Still not completely sure why this wouldn't work. Other outside links we have to the support site work fine without specifically pointing to the ASP page. Maybe it's a combination of the redirect and the TeamSite environment... I'm just glad my suggestion worked Smiley Happy

-Frank