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

Next Gen Tag UI is not working

TeamsiteUser

Hi

I have written following new rule set with Next Gen tag UI for TeamSite 6.7.1 with SP1. attached with this post
But I am getting error that " There is some error in meta data capture information . Please contact your administrator "
can any one suggest me the possible reason for this

Thanks in advance
Abha

Find more posts tagged with

Comments

nipper

Hi

I have written following new rule set with Next Gen tag UI for TeamSite 6.7.1 with SP1. attached with this post
But I am getting error that " There is some error in meta data capture information . Please contact your administrator "
can any one suggest me the possible reason for this

Thanks in advance
Abha

You forgot to attach whatever you forgot to attach

TeamsiteUser

Hi

Attached is the ruleset file and snippet of metadata - rule .cfg. Still dont able to find why it is giving error "There is some error with you meta data capture information . Please contact your System Administrator"

Thanks in advance

Abha

Adam Stoller

Hi

Attached is the ruleset file and snippet of metadata - rule .cfg. Still dont able to find why it is giving error "There is some error with you meta data capture information . Please contact your System Administrator"

Thanks in advance

Abha

Have you tried commenting out / removing the script / alert section? This should help either eliminate or isolate that part of the datacapture.cfg as being the source of the error.

nipper

Have you tried commenting out / removing the script / alert section? This should help either eliminate or isolate that part of the datacapture.cfg as being the source of the error.

I do not think it is the alert at the bottom, though it does not work. I added it to my DC.cfg and it still ran. I noticed the lack of view and view_containers in the DCT posted but have not read the DTD to see if tabs and views are either or.

Adam Stoller

I do not think it is the alert at the bottom, though it does not work. I added it to my DC.cfg and it still ran. I noticed the lack of view and view_containers in the DCT posted but have not read the DTD to see if tabs and views are either or.

Actually - the posted code does not explicitly refer to the DTD - I'm assuming it is the metadatacapture6.0.dtd - in which case one may need to specify that the 'type' is metadata (though I think if you specify the DTD it will do that for you:

<data-capture-requirements type="metadata">

But then if you're using that DTD - you would be running into problems due to the use of

<root-container...>...</root-container>

as there is no such element defined in that DTD.
That's just scraping the top - I didn't bother to examine the rest of the file.

nipper

Yea, this will take some trial and error to debug. I did not see anything that jumped out at me. You would be best loading the OOTB dct (or some working dct) and start making changes until you can determine the issue.

TeamsiteUser

We have upgraded to 6.7.1 version. Rest of the ruleset are still in old format in local/config. This is the default ruleset which comes as example in local/config/tagui/rulesets60. I am trying to run it just by defining it in metadat-rules.cfg and it is not working. Are we missing some configuration entries to run both rulesets.Will you suggest me any method so that I can debug the cause of error ?

Adam Stoller

We have upgraded to 6.7.1 version. Rest of the ruleset are still in old format in local/config. This is the default ruleset which comes as example in local/config/tagui/rulesets60. I am trying to run it just by defining it in metadat-rules.cfg and it is not working. Are we missing some configuration entries to run both rulesets.Will you suggest me any method so that I can debug the cause of error ?

Ideas have already been suggested.
Beyond those - I'd recommend spending time reading the documentation - (again). This includes Release Notes as well as the Administration Guide - and go through any section that deals with the configuration of metadata capture slowly and carefully.

Migrateduser

Try this in your metadata-rules.cfg

vpath-regex="^.*?/default/main/sps/external/public_site/(.*)/files"

We ran into a similar issue after 6.7.1 SP1