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

Ts 6.7.1 Sp1

mmb

Solaris 10 TS6.7.1 SP1

Installed this yesterday on dev server.

The main notable difference and where i am having problems is the new Tag UI.

This will not allow metadata to be saved no matter what.

It keeps reporting "No ruleset found for file..." when you click save & close.

It must have found a ruleset to render the form in the first place!

I have also tried the vague instructions for switching back to the original interface ... and these dont work either!

Am i missing something here?

Has anyone else tried installing and using SP1 yet?

thanks
-mark

Find more posts tagged with

Comments

moonkhanna

raise a case with IWOV support

Migrateduser

We are getting same error. Just sent case/email to support. Will update as soon as I get.

chicka

Have you checked the associated files.... and are they overwirtten because of SP1?

Jeffc

Check page 5 and 6 of the Release Notes.
You must create a new datacapture.cfg in local/config/tagui/rulesets60 to support the new tagging gui.

Jeff

Migrateduser

Ok. Is it mandatory...Please look at the description in README....

When loading a ruleset for display, the Next Gen Tag UI
will first look for rulesets specified in local/config/metadata-rules.cfg
by examining all .cfg files in this rulesets60 directory (expecting them
in the XML/datacapture6.0.dtd format ONLY), and selecting any rulesets that
match by ruleset name. If no matching rulesets are located, then Next Gen
Tag UI will proceed to look for the ruleset in local/config/datacapture.cfg,
anticipating the Old Tag UI format (metadatacapture6.0.dtd).

mmb

Hi just an update...

i had scoured the documentation before posting here but was not as clear as i should have been in my original post.

I had tried all combinations of creating new .cfg ruleset in the rulesets60 directory; removing old metadata datacapture.cfg; replacing the old version; running both new & old...still no luck

always get the error when you try to save the form entries.

it seems that the process is not following the sequence of events as detailed in the admin guide. There seems to be an undocumented step "on save" that is attempting to find and read some ruleset unsuccessfully.

Migrateduser

Any update??

mmb

Yes solved this one now.

There is an undocumented change to the vpath that is passed into metadata-rules.cfg

the vpath used to be /default/main/... whatever

its now //servername/default/main

this effectively caused the regex match in metadata-rules.cfg not to match on any rulesets when you tried to save the form.

The strange thing is that it did match when it opened the form...!?!

Check your regexes in metadata-rules.cfg to ensure that they match on

^.*?/default/main

to cater for the leading servername.

thanks
-mark

gzevin

I don't want to open a topic with the same name, but I have a different question - while I have not installled SP1 as yet, I have some serious worries.

The release notes say, that if TeamSite is installed to run as non-root, the current perl-based TPLs will not work.

Has anyone observed this?

Adam Stoller

I don't want to open a topic with the same name, but I have a different question - while I have not installled SP1 as yet, I have some serious worries.

The release notes say, that if TeamSite is installed to run as non-root, the current perl-based TPLs will not work.

Has anyone observed this?

I haven't had the chance to notice it one way or the other, but I believe that this is because, if run as non-root, the logged-in-user impersonation features won't work and it may alter the way the PTs work.

Are you sure this was with regard to running TS as non-root?

I know that you cannot use the Perl-based PTs (iwpt_compile.ipl, etc.) if you are using "non-OS users" - which is a feature of 671SP1 and is different than running TS as non-root.

gzevin

Are you sure this was with regard to running TS as non-root?

I know that you cannot use the Perl-based PTs (iwpt_compile.ipl, etc.) if you are using "non-OS users" - which is a feature of 671SP1 and is different than running TS as non-root.

I think so, and the issues appeared to be related to each other.