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

To IWOV: don't hide release notes in a 472MB download

Frederik

There's a new patch for TS6.5 sp2 : Patch ID 1756 : TeamSite 6.5.0 for Solaris

Unfortunately, to know what's inside one must download the full 472MB package
(cfr https://support.interwoven.com/newdownload/download/patches/TeamSite_Search_Cssdk_P12_Solaris_README.txt)
... which is also the case for previous patch 1699

To iwov: Please make release notes separately available.

To anyone else: I requested the 1756 notes from Support, will attach here ...

Find more posts tagged with

Comments

IwovHeather

Hi Frederik,

You made a good point about not being able to read the readme easily. We will be breaking it out separately from the patch to make it be the primary readme download for the patch.

Also, to make it easier for people to find the information, a KB is available on support now with the bug fixes and the full readme is attached to the KB as well. Patches and Readme's are restricted to supported customers. Please don't re-post them on DevNet.

https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=57085

I hope this helps but please contact me if you need more information,

Heather
hsimon@interwoven.com
408.220.7551

Frederik

Patches and Readme's are restricted to supported customers. Please don't re-post them on DevNet.

ok, Thanks & not reposting as per instructions...

FYI: I have taken on a habit of re-editing the various 6.5 patch readme's into a txt file that shows the fixes chronologically per patch. That way it's easier to spot at what patch level we would like to be (given that each patch installation costs $$, my company doesn't just install for the love of installing). Sorry I can't share that with the devnet public.

IwovHeather

Hi Frederick,

If you send an example to my email address below of how you structure you patch readme's, we can examine releasing all our readme information in patches in the same format in KB articles to make it more useful to other users.

Thanks for all the great feedback,

Heather
hsimon@interwoven.com
408.220.7551

ok, Thanks & not reposting as per instructions...

FYI: I have taken on a habit of re-editing the various 6.5 patch readme's into a txt file that shows the fixes chronologically per patch. That way it's easier to spot at what patch level we would like to be (given that each patch installation costs $$, my company doesn't just install for the love of installing). Sorry I can't share that with the devnet public.

Frederik

New patch 1767. Same problem. Download 472 MB to read 10KB release notes. Smiley Sad

Frederik

New patch 1824 for TS 6.7.1. Rated Critical.
Same problem. Download 700 MB to read 10KB release notes. This is so tiring Smiley Sad

:mad:

Odd, it's dated 2 days ago, but I've seen a new "patch 3" already early last week on the support site. Maybe issued, pulled, rebuilt?

EDIT: ok, it's dated 22/5 on Product download and 29/5 on Patch download.

nipper

Even more fun, if you view this patch through Patches and try to view the readme or download, you get a file not found. Then read more and there is a note that you should download from the products section.

Making links to nowhere is not a great plan.

Andy

IwovHeather

Hi guys,

Does this KB work for you in terms of the contents of the patch?

http://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=57890

It has an attachment with the readme's for the patch. Because of the patches size, we are recommending downloads through the product download area, under TeamSite. I apologize for the delay in updating the KB with the new patch information and readme. If this format doesn't work for you, please let me know what you would like instead.

Thanks,

Heather

Frederik

Hi Heather,

yeah, that KB is ok IMO.

Some suggestions at improvement still

- Personally, I'm a bit dizzy from the multiple patch number that are in use. This is both "Patch 3" (logical patch# for TS 6.7.1) and "Patch 1824" (physical patch bundle for TS 6.7.1 Solaris) and "TeamSite 6.7.1 Patch 70516, Search Patch 70900, etc". I understand that all these IDs have a good use to identify parts and pieces, but would it be possible to either use different words (e.g. "Update 3", "Patch/Bundle 1788", "P70516"), or to just explain this correspondence in an introduction to the KB or in a linked, separate KB? (I think the former idea is weak if not everyone is consistent in the terminology).

- there's a mixup near the end, where the Win-Linux-Sol Patch 3 are match to 1823-1824-1725. Correct is Win-Sol-Linux => 1823-1824-1825

- I guess the search index isn't updated yet, cause a search for 1824 yields nothing, but search for 1788 gets this result (based on previous content of this KB?). As such, my next point is speculative:

- Since the word 1788 doesn't appear any more in the KB, I fear it will soon no longer be found when searching for string 1788. It would be good if a search for any of the discussed patch numbers, would yield this KB as result.

I feel like I've spent the last half hour working for IWOV rather than for my employer :cool:

lhdavis

I get a file not found when trying to download the Windows version, patch 1823 and started a support case for it.

We've also had trouble with the 6.7.1 patch downloads timing out because these patches are so large so I've had Interwoven Support place it in our folder on their ftp server.

UPDATE: We are able to download from the Products section, just not the Patches section. It used the ESD functionality too which does not time out if you use the FTP option. Thanks for the recommendation!