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; } } }

TS6[CCP]: CCI URLs

Adam Stoller

TS6.0L Solaris 8
----------------------
I have a cgitask script as part of a workflow, it displays a page with a link to edit the DCR that is associated with the workflow. I've modified the code so that the URL looks like:

http://localhost/iw/iw-cc/edit?vpath=/education/main/.../data/about/test

But I get "The page cannot be found / HTTP 404" error message when I click on the link.

I tried dropping the /iw/ part and had it go to just:

http://localhost/iw-cc/edit?vpath=/education/main/..../test

and get the same result.

First - what is the correct URL for this? the first one or the second one, or something else?
Second - how do I go about debugging why this is failing to work?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Find more posts tagged with

Comments

iwovGraduate

This works for me on TS 6.0; W2K:

http://localhost/iw-cc/edit?vpath=education/main/.../test

Notice that I have dropped the leading "/" in vpath value.
"education" is the name of your store, right ?

Adam Stoller

That didn't seem to work either (and I would have been a bit miffed if it had - since vpaths should begin with a '/')

Yes, /education is a store.

Any ideas how to debug what's going on to try and figure out if there's some configuration / installation problem?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Adam Stoller

I'm still looking for ideas on how to debug why this isn't working.

Anyone have any ideas?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Monil

Try http://localhost/iw/webdesk/edit?vpath=/education/main

Adam Stoller

I can try that - but that's a legacy URL not one of the new TS6 URL's - and I'd like to know why the new TS6 URL isn't working.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

The recommended URL to use is /iw-cc/edit?vpath=..

The first thing I'd try is hitting the URL outside of your CGITask (directly in a browser window). If you no longer get a 404 error, then the problem is in your CGI script. From a CGI in /iw-bin/, you should redirect to a CCI URL as follows:
window.location = /iw-cc/somecciurl?params... -- otherwise you will most definitely get a 404 error.

I doubt the problem is with the particular vpath (you'd see a proper error dialog instead of a 404); however, as a sanity check you might want to try hitting http://yourservername/iw-cc/edit with no parameters. You should see a CCPro or CCStd error dialog, not a 404 error.

Also, are you really using "localhost" instead of the proper name of the teamsite server in your CGI task script? Again, from a CGI in /iw-bin, you shouldn't have to use an absolute path to invoke a CCI URL.

Also, have you done any customizations that muck with web.xml? If you can't reach any of the CCI URLs, you might consider backing out your customizations to web.xml.

Hope this helps!

Michelle Neuringer
Interwoven Engineer

Adam Stoller

Also, are you really using "localhost" instead of the proper name of the teamsite server in your CGI task script?
Doh! - Of course that doesn't work within the CGI redirection.

Again, from a CGI in /iw-bin, you shouldn't have to use an absolute path to invoke a CCI URL.
So you're saying I could just use <a href="/iw-cc/edit?vpath=...">...</a> ? Hmm - that would probably be cleaner - I may try that.

My remaining problem seems to be (once I fixed the URL [sigh]) figuring out why it things the workarea being referenced in the vpath is not writable -- as that's the error message I get now:
Not a writable workarea: //servername/education/main/.../WORKAREA/work

Thanks again for banging me over the head with the URL.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

If you hit the URL outside of the CGI task (in the browser address bar), do you still get the same "not writable" error message?

Michelle Neuringer
Interwoven Engineer

Adam Stoller

I think the not-writable thing was a permissions snafu on my part - I'm essentially trying to recreate a customer's 5.5.2 environment on a separate 6.0L environment (soon to be upgraded to 6.1) and it appears to have been fixed when I added the logged in user to the group the workarea was shared with (understandably)

Thanks again for the localhost thing - it seems to work just fine now - at least as far as bringing up the window. I now need to figure out what some of the FormAPI code doesn't seem to be working.... but it's progress none-the-less.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com