How do we revert back to the Pre-SP1 Tagger UI?

Hi there,

Regarding 6.7.1 SP1's “Next Generation” Tagger UI…

We just applied SP1 to our 6.7.1 Dev box, and we'd really like to wait for the "next generation" Tagger UI to mature for a cycle or two before rolling it out to our users. There are just too many inconsistencies between tagging one file vs. multiple files. Additionally, it simply doesn't seem to be working with our taxonomy at all. For example, suggestions completely stopped working. Also, we no longer can add top-level taxonomy items to a field.

For now, we'd be perfectly happy with the older Tagger UI. Has anyone had any luck rolling back to the pre-SP1 Tagger UI? I followed the instructions on page 7 of the 6.7.1 SP1 release notes (and ran the make_toolkit.ipl), but the new Tagger UI is still appearing. What am I missing?

Our application_custom.xml is as follows:




  PUBLIC "-//Interwoven, Inc.//DTD Application Customizations 1.0//EN"
  "../../../../reference/etc/conf/application_custom.dtd">

I've also contacted IW support regarding this.

Thoughts?

TeamSite 6.7.1 SP1 (Solaris 9)
MetaTagger 4.1.2 (Solaris 9)

Thanks,

Find more posts tagged with

Comments

Migrateduser

Dan,

You might want to try the following steps:

1.Edit application.xml present in /iw-home/httpd/webapps/content_center/WEB-INF/conf/tagui.
2.Change value for 3.Change the value for 4.Restart Servletd.
5.Select a file and click File->Tag.
You should see the old tagui.

looks like a doc bug!

regards,
Audi

mgal

You can also try this

In the following file:

iw-home/local/config/lib/content_center/customer_src_new/etc/conf/customer/application_custom.xml file

add this:

and then go to:

iw-home/local/config/lib/content_center/customer_src_new and run /iw-home/bin/make_toolkit.ipl

Migrateduser

editing webapp config files directly may work, but can complicate product support later. Always incorporate your customziations with make_toolkit. And as Mgal says put the iw.tagui.singleFileUI param in the application_custom.xml and build your customer_src.

Migrateduser

Yep, that worked. And snkmoorthy correct, it's always best to make these types of modifications via the make_toolkit way. Here's what our application_custom.xml ended up looking like:

Thanks, audumberr et al, for your help!

Thanks,