Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
why rebuilding the CCpro after each patch or upgrade??
CRB
<---on windows--->
HI,
i am sure alot of you noticed and suffered with the change in the interface that happens to teamsite about installing SP3 on 6.5 sp2... we finally got over that issue, and then i run into it when i upgrade to 6.7.1... and got it fixed , then i decided to apply patch2 that came out for 6.7.1 and that s also changed my interface to the "ajuba" sample interface... why do i have to deal with that issue after everytime i install a patch or SP? i thought the upgrade or installing patch should cause major change...
any ideas to how to avoid that next time i install a patch or sp ?
i have a case open with support since SP3 came out, but i havent heard from them about the root cause of the miss that SP3 made...
Find more posts tagged with
Comments
Bill Klish
Interesting, I have applied both of the software packages you mention, but I haven't seen this issue. Granted, we have made our own customizations to the UI, which you don't mention doing.
Can you explain what you mean by the Ajuba site?
CRB
Ajuba is one of the "brands" that interwoven provides with teamsite in customer_src_sample to use for sample customization (examples)...
this is what i have customized in my TS:
1)i added to items (cgi tasks) to the file menu.
2)i added to two tabs (opens webpage) to ccpro
as you know those changes are made in ui.custome.xml
that s all i have changed in TS after the installation...
and after installing SP3 or a patch it changes the interface to look like the picture below: (notice: it also addes the devnet tab, current user and writting guide tab...)
Bill Klish
Odd, have not seen that.
Can you check this file for me and tell me if the customer_samples toolkit is enabled:
iw-home/local/config/lib/content_center/toolkits.xml
Since this is happening I suspect either it was enabled before for some testing, or Interwoven mistakenly updated it in the sp. I have not seen it in either 6.7.1 (patch 1 or 2) or sp3.
ExecuteReport.java
barchartpalette.rptdesign
CRB
i have that entery commented out in toolkit.xml, because what happens is that i after an upgrade or a patch, it gets uncommented so i have to comment it and rebuilld my webapp... does this mean that every installation replaces my existing toolkit.xml?
Bill Klish
I just tried installing sp3 on windows 2003 EE server as an upgrade to sp2 and I don't see this happening at all. That file is touched, but contains the base entries. The customer samples toolkit isn't even present in my install. Not sure how this could be happening to you.
Keywil
Were you ever able to figure out why this was happened? We've run into the same issue after testing the recent patch3 on TS6.7.1 SP1,
Our customizations to the UI menus appear to be intact but new portlets render in the ccStd interface.
new portlets:Column1
Corporate Style Guide
Current User Information
new portlets:Column2
Interwoven Developers Network
Saved Searches
In addition there's a 'Search the Web' link in the upper right (ccStd only) connecting to Google...
In ccPro
Some of the wording on the tabs appears to have changed as well... "Content" has become "Files" in ccPro
There is a "Custom Menu 1" on the right hand of the actions bar beside 'Submit'
TS6.7.1 SP1
Win2K3
Keywil
I (finally) realized that after installing the July 31 Patch, TeamSite was implementing the
customer_samples/portal_custom.xml
instead of our
/customer_src/etc/conf/customer/portal_custom.xml
even though there was no mention of the customer_samples in our toolkits.xml file.
Page 32 of TeamSite User Interface Customization Guide explains how to remove the Customer Samples Toolkit and rebuild the ContentCenter web application.
from cmd in Win2K3
/iw-home/iw-perl/bin/iwperl /iw-home/install/install_webapps.ipl -i -f content_center
Voila! Offending portlets and tabs are gone
the documentation makes a point to say
*This is not the normal ContentCenter web application rebuild command.