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

7.2 for those not using SitePublisher

gzevin

Ok, I finally got an official answer that 6.7.2SP2 will not support Win7 and IE8 as clients.

I started looking at 7.2 at the request of a number of my clients, some of whom will be forced into 7.2 by the above fact (i.e. their SOE will be moved to Win 7 soon). And yes, they use VisualFormat and the implementation is massive to change everything to tinyMCE so they could use a Firefox.

I am simply horrified. Again, I can see a total absence of regression testing and some deficiencies in UI design.

I will be dumping here some of my finding so those who do not need to use 7.2 just for the sake of the marvel called SitePublisher, have some heads up.

----------------
Finding Number 1.

(working, as of 6.7.2) CGI callouts are no longer working in both metadata tagging and DCT. What's more some of them don't work at all. And these are callouts that use the standard documented javascript code that handles value return to the fields and CGI window closures.

I had to rewrite some of the callouts completely, some got fixed. I kind of know what is causing it, but will wait for support's confirmation. They did manage to replicate the issue - the OOTB sample callout DOES NOT WORK!!!!!!!!!
-------------------------
Finding Number 2.

Admin tab - adding users. Does not work, I mean it does not find OS users.

AMAZINGLY, I have found a second version of the Admin UI that handles users and groups. That works. But it's accessible from CC PRO, not from the Admin tab.

---------------------------
Number 3

WHAT'S MORE - the Admin tab UI does not show OS group for a user. Only TS groups. The second version of the UI seems to show the groups Ok.

-----------------------

more to follow, watch this space

Find more posts tagged with

Comments

nipper

Yea 7.2 is quite buggy. 7.1 is much better. That being said, there is some really cool functionality in 7.2

I hope 7.2.1 is due really soon.

gzevin

Yea 7.2 is quite buggy. 7.1 is much better. That being said, there is some really cool functionality in 7.2

I hope 7.2.1 is due really soon.

Andy, what's cool in particular? I'm really interested.

The issue is that with some clients they insist on going with the latest version.

nipper

Andy, what's cool in particular? I'm really interested.

The issue is that with some clients they insist on going with the latest version.

It is new, therefore it is cool. You must be too old to understand. Smiley Tongue

The language translation functionality will be a big plus to a lot of my customers, as will the association management (associate disparate objects into 1 logical item).

gzevin

It is new, therefore it is cool. You must be too old to understand.

The language translation functionality will be a big plus to a lot of my customers, as will the association management (associate disparate objects into 1 logical item).

Last time I checked, you were a few months older than me :eek: Even the Aussie dollar reaching parity with the greenback does not change it Smiley Tongue

Yeah, I understand some site publisher stuff, but we have a very little uptake of the SP here, and quite a few huge legacy accounts that just need the continuation of business. Which I can hardly see happening with this release.

srosewall

Careful: "language translation functionality" may be mis-intepreted by some.
(Is it possible that the Autonomy marketeers have used vague terms to entice the unwary?)

It's the provision of a workflow to help manage the translation process and some tools to help you see what has/hasn't been translated from a master asset.

GCM (Globalised Content Management) - the ability to have a hierarchy of localised sites and assets is interesting, but I've yet to use it in anger, and call be synical, but I suspect there will be some capability that the developers haven't consider / provided for in the first cut - expect this area to mature over the next few releases I'd say.

Another key thing to look out for: switch to JBoss for everything (goodbye stand-alone Tomcat) with the added joy of having to learn the whereabouts for a whole new bunch of log files... no more servletd logging I'm afraid.

gzevin

Careful: "language translation functionality" may be mis-intepreted by some.
(Is it possible that the Autonomy marketeers have used vague terms to entice the unwary?)

It's the provision of a workflow to help manage the translation process and some tools to help you see what has/hasn't been translated from a master asset.

GCM (Globalised Content Management) - the ability to have a hierarchy of localised sites and assets is interesting, but I've yet to use it in anger, and call be synical, but I suspect there will be some capability that the developers haven't consider / provided for in the first cut - expect this area to mature over the next few releases I'd say.

Another key thing to look out for: switch to JBoss for everything (goodbye stand-alone Tomcat) with the added joy of having to learn the whereabouts for a whole new bunch of log files... no more servletd logging I'm afraid.

well. I have been developing translation workflows and infrastructure in 2002. In TeamSite. nothing new Smiley Happy

srosewall

well. I have been developing translation workflows and infrastructure in 2002. In TeamSite. nothing new

Indeed - most implementations have their own take on localisation, but now it's a vendor provided/supported "feature"... a tick box for RFPs Smiley Happy

vpatel

Yeah, I understand some site publisher stuff, but we have a very little uptake of the SP here, and quite a few huge legacy accounts that just need the continuation of business. Which I can hardly see happening with this release.

I am not sure if you are aware of this but the Dependency Management functionality can be used for DCRs and other assets -- not just SP pages. Say for example: you have an image and want to find out what are all of the other assets (DCRs, generated HTML/JSP/ASP files, etc.) that are referrencing that particular image -- this is what that provides. It is a bi-directional relationship mapping:

1. Given an image (or any other asset -- including DCRs), find out all of the other assets using this image.

2. Given a DCR, find out all of the assets that are being used in this DCR.

This is very basic and powerful functionality that was introduced in 7.2. It is not just limited to SP.

HTH!

interDev

I am not sure if you are aware of this but the Dependency Management functionality can be used for DCRs and other assets -- not just SP pages. Say for example: you have an image and want to find out what are all of the other assets (DCRs, generated HTML/JSP/ASP files, etc.) that are referrencing that particular image -- this is what that provides. It is a bi-directional relationship mapping:

1. Given an image (or any other asset -- including DCRs), find out all of the other assets using this image.

2. Given a DCR, find out all of the assets that are being used in this DCR.

This is very basic and powerful functionality that was introduced in 7.2. It is not just limited to SP.

HTH!

What is the way to find out all dependent assets for a DCR in TS7.2 environment programatically?

Adam Stoller

What is the way to find out all dependent assets for a DCR in TS7.2 environment programatically?

You will have to do it using Java - take a look at this thread starting from post # 12 and onward.