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

Bugs in TeamSite 6.7.2 Service Pack 2

System

Has anyone come across any major bugs in TeamSite 6.7.2 Service Pack 2 ? Thank you.

Find more posts tagged with

Comments

ccprofessional

Good question.
In a few weeks, i am doing a go/ no-go decision with SP2 in my client's environment. We plan to install on a dev environment - regression test and all the jazz.

The upgrade from 671->672->672sp1 was not smooth (livesite pages totally broke. DCT tabs broke).. so there's a lot of trepidation.

nipper

Has anyone come across any major bugs in TeamSite 6.7.2 Service Pack 2 ? Thank you.

I put SP2 in our dev environment when it was released. No problems as of yet.

Jamik

I'm currently working with 6.7.2 SP2 in our dev environment as well and so far no big problems yet, but we're just starting the testing process so we'll see what we find.

SethHickel

We are moving from 6.7.1 to 6.7.2 SP2 via path of 6.7.1 -> 6.7.2 -> SP2. Will start on our development box. I will post back any oddities that come out of testing. We are not sure when the work will start though.

Per support here is the list of the minimum versions you have to be on for other components when on TS 6.7.2:

???? SitePublisher
???? OpenDeploy Deployment Server 6.2
???? MetaTagger Intelligence Server 4.1.2
???? TeamSite Front-Office 6.7.2
???? UI Toolkit 2.0
???? Report Center 2.0 (Crystal 11)
???? Search 2.1.1
???? Workflow Modeler 1.0.1.0
???? ECM Connector 3.x
???? CTS 2.x (xDoc Server 3.0)
???? MediaBin 4.6.x
???? ContentServices 3.1.1

Also per support there are not any deprications or concerns with iwperl in this upgrade.

A suggestion: back up your current current iw-home folder.

nipper

We are moving from 6.7.1 to 6.7.2 SP2 via path of 6.7.1 -> 6.7.2 -> SP2. Will start on our development box. I will post back any oddities that come out of testing. We are not sure when the work will start though.

A suggestion: back up your current current iw-home folder.

A better idea, have your server (at least Dev) on a VMWare instace, back up the complete VM and be prepared to reload it if things break.

SethHickel

Yes - a much better idea. Thank you.

Samplet.pdf

rodigz

Hi there,

I've login in support site and I can't find instructions on how to install 6.7.2 SP2.
We have solaris TS 6.7.2, we are thinking to install SP2 directly.
Please advise.

thanks

Samplet.pdf

Migrateduser

You can just run the installer....

Just make sure that you still have your iwinstall folder and don't mess with it. The installer will look at that directory to determine what has been installed and if the SP2 could be installed on top of your base software.

ccprofessional

You can just run the installer....

You will be eating more than just noodles if you 'just run the installer'.

Like any upgrade, you need to have a proper plan of action that takes into account everything in the Install guide, Release notes, your existing customizations, among other things.

Adam Stoller

Hi there,

I've login in support site and I can't find instructions on how to install 6.7.2 SP2.
We have solaris TS 6.7.2, we are thinking to install SP2 directly.
Please advise.

thanks

When you say "we are thinking to install SP2 directly" do you mean on a server that does not have 672 [base version] already installed? Or do you mean without installing SP1 first?

The former is not possible - the latter should work by unpacking the SP2 tar.gz file and then running the installation script within the unpacked directory. The instructions should be in the 672SP2 TeamSite Installation Guide manual.

SethHickel

I had a conference call with our Interwoven/Autonomy rep yesterday. There were two interesting things that I found out.

1. 7.0 is coming soon and since we are planning to budget this upgrade for our next fiscal year we are going to wait on 7.0 and perhaps the first minor release after that.

2. ReportCenter will not be returning until the 7.0 version. We were told that ReportCenter is not part of 6.7.2.

ccprofessional

I am looking at using Report Center and have 672 sp1 and soon sp2.

I realized my customer does not have a Report Center download option from the Support Center. I was thinking its because of a licensing issue. Are you saying that Report Center is not compatible with 672 SP2?

SethHickel.. can you shed more light on what you learnt about Report Center and 672?

SethHickel

The only light I can shed is that which I already have. My notes from the meeting are:

Don’t have report center in 6.7 but will be back in 7.0 (released at the end of august)

I believe that they were referring to 6.7.2 but I am not 100% sure that they were not referring to any 6.7.
Any knowledge out there about this?

miletwo

Just upgraded existing 6.7.1 SP1 to 6.7.2 SP2 and found issues with xml parsing. Both in the webapp (via make_toolkit.ipl) and in solutions email templates not validating. Other than that it looks okay but so far this is a showstopper for us until we get an answer from IW.

Jamik

I had a conference call with our Interwoven/Autonomy rep yesterday. There were two interesting things that I found out.

1. 7.0 is coming soon and since we are planning to budget this upgrade for our next fiscal year we are going to wait on 7.0 and perhaps the first minor release after that.

2. ReportCenter will not be returning until the 7.0 version. We were told that ReportCenter is not part of 6.7.2.

Based on your #2 (pretty sure ReportCenter is still in 6.7.2 unless they're talking about some other kind of ReportCenter) I'm highly suspect on #1. #1 has been "coming soon" for a couple years now, but I suppose with Autonomy driving things now they could surprise us.

SethHickel

I only know what I've been told. :-) We are not on 6.7.2 so I really can't confirm/deny ReportCenter's inclusion/exclusion.

CRB

#1 has been "coming soon" for a couple years now, but I suppose with Autonomy driving things now they could surprise us.

I heard from an iwov salesman that 7.0 is coming out next month (sept 09). however, he did give some wrong info before, so i wouldn't be surprised if he turns out wrong about the 7.0 too.

nipper

I heard from an iwov salesman that 7.0 is coming out next month (sept 09). however, he did give some wrong info before, so i wouldn't be surprised if he turns out wrong about the 7.0 too.

Hmmm, that is strage, we had the local sales critter in and he talked about 7.0 but was very vague about the release date.

CRB

Hmmm, that is strage, we had the local sales critter in and he talked about 7.0 but was very vague about the release date.

I was also surprised, but he insisted on sept 2009 date...

Migrateduser

Has anyone been able to successfully remove TinyMCE attributes in TeamSite 6.7.2 SP2?
We are looking to remove the following:

A. Insert/Edit Image Plugin:
1) Border attribute.

B. Table Plugin:
1) General tab - “Class” drop down field.
2) Advanced tab - Style
3) Advanced tab - Language Code
4) Advanced tab - Language Direction
- Thank you

CRB

i believe TS 671 SP1 Patch 6 has the same version of tinymce as TS 672 SP2, so i can say yes we have remove some of those attributes. you will have to make change in multiple files, not only one file. what have you tried so far that didnt work?

vpatel

i believe TS 671 SP1 Patch 6 has the same version of tinymce as TS 672 SP2, so i can say yes we have remove some of those attributes.

Not true. TS 671 SP1 had TinyMCE 2.x and TS 672 SP1 and onwards has TinyMCE 3.1.2.

CRB

Not true. TS 671 SP1 had TinyMCE 2.x and TS 672 SP1 and onwards has TinyMCE 3.1.2.

TS 671 SP1 Patch 6

: )

vpatel

: )

Ah my bad, I overlooked that *Patch 6* part :-)!