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

Teamsite 6.7.2 SP1 installation

vikaslohia

Hi,

I am planning to install the latest version of teamsite, 6.7.2 SP1 on a fresh server. I am a bit confused with the different versions, teamsite patches and service packs on the download site. Can someone please help me with the installation path. What would be the best installation path?
- Do I first install 6.7 and then move to 6.7.2 and then SP1? Where do I fit the teamsite patches?
- Or can I directly install 6.7.2 and then apply SP1 and teamsite patches?

Rgds,
Vikas

Find more posts tagged with

Comments

IWJava

Hi,

I am planning to install the latest version of teamsite, 6.7.2 SP1 on a fresh server. I am a bit confused with the different versions, teamsite patches and service packs on the download site. Can someone please help me with the installation path. What would be the best installation path?
- Do I first install 6.7 and then move to 6.7.2 and then SP1? Where do I fit the teamsite patches?
- Or can I directly install 6.7.2 and then apply SP1 and teamsite patches?

Rgds,
Vikas

Vikas,

Its really a great news that you are planning to install TS 6.7.2 SP1. Dont be confuse for the different versions. First of all install TS 6.7.2 directly. Then Install TS 6.7.2 SP1 and TS patches.
Go ahead confidently. If you are facing any problem while installation, post your problem on devnet. We are here to help you out.

Best of Luck.

AK

gzevin

Hi,

I am planning to install the latest version of teamsite, 6.7.2 SP1 on a fresh server. I am a bit confused with the different versions, teamsite patches and service packs on the download site. Can someone please help me with the installation path. What would be the best installation path?
- Do I first install 6.7 and then move to 6.7.2 and then SP1? Where do I fit the teamsite patches?
- Or can I directly install 6.7.2 and then apply SP1 and teamsite patches?

Rgds,
Vikas

as far as I know, one should be avoiding SP1 for 6.7.2. very badly tested, as I was told.

but yes, install 6.7.2 and then the rest. if you like.

gzevin

Vikas,

Its really a great news that you are planning to install TS 6.7.2 SP1

AK

why is this such a great news?

ccprofessional

I'm sure its great news 'cuz his client made someone in Sales very happy ;-)

Greg, On the contrary, TS 6.7.2 without SP1 is buggy. I ran into the following without SP1:

1. TinyMCE is totally broken - It spews out tons of errors (version 2.x)
2. The DB schema needs an update in SP1 - so any development you do in the base that depends on the db is at risk in a future upgrade.
3. SP1 adds additional segmentation and targetting related tags (even when you do not use those modules) to .page and .site files. That in itself is not bad, but it makes upgrading to SP1 on already developed sites more difficult.

I would either stay at TS 6.7.1 SP1 ( a little buggy but OK) or move to TS6.7.2 SP1 but not anywhere in between.

tanguyr

Greg, On the contrary, TS 6.7.2 without SP1 is buggy...I would either stay at TS 6.7.1 SP1 ( a little buggy but OK) or move to TS6.7.2 SP1 but not anywhere in between.

We've been pretty happy with 6.7.2 plain, and had numerous issues with SP1 (luckily just on our dev server). We got a "black patch" on SP1 from support, then had to get another fix for that (some missing jars used to compile toolkits had to be copied from another location), then ran into issues where groups had disappeared from files and folders **including in EDITIONS**. We've halted any plans to apply SP1 in our other environments and are planning to wait for the first official patch on SP1 to come out (told to expect it some time next month).

just my 0.02$

/t

ccprofessional

Migrating existing sites from TS 6.7.2 to SP1 is a pain, but if its a new install SP1 works fine.

I recently migrated my client from 671 sp1 to 672 sp1, and while the migration has had its hiccups (and required a good bit of hacking) 672sp1 is stable and business actually says its better.

It goes to show that every implementation is different.

One big reason for me was the ability to use TinyMCE's new api (which is not supported by IW). Also, I like to be able to use IDOLs power in TS search - in the future.

gzevin

I'm sure its great news 'cuz his client made someone in Sales very happy ;-)

Greg, On the contrary, TS 6.7.2 without SP1 is buggy. I ran into the following without SP1:

1. TinyMCE is totally broken - It spews out tons of errors (version 2.x)
2. The DB schema needs an update in SP1 - so any development you do in the base that depends on the db is at risk in a future upgrade.
3. SP1 adds additional segmentation and targetting related tags (even when you do not use those modules) to .page and .site files. That in itself is not bad, but it makes upgrading to SP1 on already developed sites more difficult.

I would either stay at TS 6.7.1 SP1 ( a little buggy but OK) or move to TS6.7.2 SP1 but not anywhere in between.

I think you are obfuscating the matter.

If you think that the SitePublisher component is somehow a part of core TeamSite, I totally disagree. I never thought that TeamSite isdependent on some sort of a database Smiley Happy

otherwise the product is stable, not sure much about tinyMCE, as we have only a handful of sites with it - but nobody complained so far.

gzevin

We've been pretty happy with 6.7.2 plain, and had numerous issues with SP1 (luckily just on our dev server). We got a "black patch" on SP1 from support, then had to get another fix for that (some missing jars used to compile toolkits had to be copied from another location), then ran into issues where groups had disappeared from files and folders **including in EDITIONS**. We've halted any plans to apply SP1 in our other environments and are planning to wait for the first official patch on SP1 to come out (told to expect it some time next month).

just my 0.02$

/t

this is what I heard as well.