ContentCenter Standard in 7.3.1

Is anyone using ContentCenter Standard in 7.3.1? We've started looking into the updated TeamSite user interface but as CCStd is still listed in the Administration section as an available interface I'm trying to get information on anyone who's attempted to continue using it with their move to 7.3.1.

Just trying to figure out how much of our user documentation we're going to have to rewrite with our migration from 6.7.1 to 7.3.1.

Find more posts tagged with

Comments

nipper

STD is still there. The TeamSite UI is basically much nicer STD interface so I would expect you would *want* to move to TeamSite UI. I have used it and it is basically as (un)functional as before. No customizations when I tried.

nipper

One more oddity (and it may be on my own setup), I cannot find a link to cc_std.

From my GUI I can get to Admin & TeamSite but no link to STD. I checked my user and I am set to use either UI.

When I changed my URL to /iw-cc/command/iw.ccstd.switch_ui the STD UI came up.

Again, do not know if this is a bug or a config on my part (and frankly I do not really care). Just thought you would be interested.

Capture.PNG

lhdavis

I didn't have a link either and originally tried the /command/iw.ccstd.switch_ui URL successsfully. However I sent it out to two of our other test users and now all of us are getting a JBoss error no matter trying to access ccstd.

nipper

Anything of interest in the iwjboss.log ?

BTW, if you run iwreset -a, expect to wait about 5 minutes AFTER it completes for the UI to come back.

Adam Stoller

Anything of interest in the iwjboss.log ?

BTW, if you run iwreset -a, expect to wait about 5 minutes AFTER it completes for the UI to come back.

I usually tail the IWHOME/local/logs/iwui/content_center.log to watch until it completes before trying to access the UI - I found this to be the case in 7.2.1 too.

FWIW - the few times I've played with my 7.3.1 installation, I didn't see a CCStd link either - but I didn't really care because I never liked that UI :-)

mart2001

I used to look at the content_center.log to see when the ui comes up. This worked well back before jboss. But the server.log in the applicationcontainer deploy server log directory tells you when the UI is really up.

Adam Stoller

I used to look at the content_center.log to see when the ui comes up. This worked well back before jboss. But the server.log in the applicationcontainer deploy server log directory tells you when the UI is really up.

Hmm - maybe it was with 6.7.2 that I tailed the content_center.log - either way, I actually complained about this kind of thing about 9 or 10 years ago because I ran into situations where I wanted to start something after the server had started and I couldn't rely on the server start script returning after the server was fully up.

lhdavis

"Official" response from Support:
Since the new UI has replaced CCSTD, we will not have any more development or QA cycles designated to CCSTD. As such, we will not be able to support CCSTD as of 7.3, although you can use it if it is not causing any problems. We can just not guarentee that it will continue to work.

So I guess we'll be updating everything to use the brand new interface Smiley Happy

Adam Stoller

"Official" response from Support:
Since the new UI has replaced CCSTD, we will not have any more development or QA cycles designated to CCSTD. As such, we will not be able to support CCSTD as of 7.3, although you can use it if it is not causing any problems. We can just not guarentee that it will continue to work.

So I guess we'll be updating everything to use the brand new interface

That's interesting. Autonomy doesn't put an EOL on releases, so they're essentially supported forever, but they put put an [undocumented] EOL on part of the UI ?

Even more "funny" is that the 7.3 documents still reference CCStd: