Hello,

I know it could be more complex task but I'll ask it here...

Is it possible to import added tags (taxonomy "tags") as values to the keywords field? Without I have to set internal tags and meta keywords twice. I think it could be a simple way to set internal tags and use it as keywords too...

CommentFileSizeAuthor
#26 1134192.patch518 bytesvalthebald

Comments

valthebald’s picture

It is possible with patched token module, see #1122486: Support for tokens in field values
For example, set [node:field-tags] as meta keywords default value and it should work

JohnnyX’s picture

Ok, thanks. But if I won't patch my token module I have to wait for a new token release...
I haven't found the patch but should search later again with a little bit more time ;)

valthebald’s picture

JohnnyX’s picture

Many thanks! I'll try it with a test installation first ;)

JohnnyX’s picture

Status: Closed (duplicate) » Active

Mh, patched token module doesn't work for me. I get a endless loop if I load the node with "[node:field-tags]" token...
I added token during edit the node. Any idea?

I open up this issue again for this last question...

valthebald’s picture

Just a moment, where did you put [node:field-tags] value? In keyword field? Did you use standard or minimal profile during install?

JohnnyX’s picture

I used standard profil and placed the token into the keywords field (= metatag_quick field) during edit the node/ blog entry.
Also put it into content type default value for the keywords field in first step...

valthebald’s picture

Not sure if it can help, but try to put Tags (taxonomy) field before meta tags in node editing form

JohnnyX’s picture

Tags were/ are before meta keywords. Doesn't work. Any other idea?
I also patched the beta and the dev release... same problem.

valthebald’s picture

to continue further need more details.
Did you check error logs? Anything suspicious? What other contrib modules enabled?

JohnnyX’s picture

Chaos tools 1.0-alpha4
Views3.0-beta3
Wysiwyg 2.0
CKEditor Link 1.2-beta1
Meta tag field 1.6
Automatic Nodetitles
Colorbox 1.0-beta4
Favicon (?)
Global redirect 1.3
Image resize filter 1.12
Insert 1.0
Menu Block 2.2
Menu Block Export 2.2
Pathauto 1.0-beta1
Token 1.0-beta1 (<- which working correct so far, unpatched)
Piwik Web analytics 2.1
Tagadelic (?)
Taxonomy Menu 1.1

Missing versions not displayed at modules page...
I see no errors at the Drupal logs.

valthebald’s picture

Non-patched token does not expose field values as token.
Don't forget to run update.php / flush all drupal caches after patching.
Do you see anything in logs after patching and trying to save?

JohnnyX’s picture

Yes, I tried the patched version and than roll back to the working version ;) update.php and flush cache was done more than one time...

valthebald’s picture

I have run out f ideas :(

JohnnyX’s picture

Mh, I'll give it a second try with a test installation soon...
Anybody get it work?

JohnnyX’s picture

I tested it again with a patched token module (http://drupal.org/node/691078#comment-4499612) but don't work like it should....
The keywords aren't comma separated.

default value: [node:field-tags]
added tags: test, keywords
result: testkeywords

Any idea how to fix it?

valthebald’s picture

@JohnyX,
can you confirm using D7.2?

JohnnyX’s picture

Yes! I upgraded my installation to D7.2.

JohnnyX’s picture

Any new information or plans about this issue/ feature request?

I found this issue:
http://drupal.org/node/1170820

valthebald’s picture

No, #1170820: Configurable auto-create for different entity types and meta tags is not related to this issue. I'm afraid I can't help you, since I can't reproduce the problem.

JohnnyX’s picture

Did you test to use a token to duplicate/ copy the added tags to the metatag_quick field for keywords of this node? Do you know the token module version you used?

valthebald’s picture

Yes, I used token 7.x-1.0-beta2 + patch, and it worked with taxonomy tokens as expected

JohnnyX’s picture

Ok, I used the same.

Which token did you put into the field? Maybe I used a wrong token?!

valthebald’s picture

Ah!
I never tried more than one term as a value, that's the point!
OK, I see the problem, will try to solve it

JohnnyX’s picture

Ah, great! Thank you very much! :)

valthebald’s picture

Version: 7.x-1.x-dev » 7.x-2.x-dev
Assigned: Unassigned » valthebald
Status: Active » Needs review
StatusFileSize
new518 bytes

Patch is done against 2.x, but would work with 1.x as well

JohnnyX’s picture

Ok, thanks.

I'll update to 7.x.2-dev and test the patch ;)

JohnnyX’s picture

Works fine in a test site! Many thanks :)

valthebald’s picture

Status: Needs review » Fixed
valthebald’s picture

Title: Add taxonomy tags to field meta keywords » Support for tokens in meta tag field values
Issue tags: +Tokens in field values

Changing title to better describe the issue

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

TravelTechie’s picture

Category: feature » support
Status: Closed (fixed) » Needs work

I saw that the fix for the tokens in fields is for token_1.2_beta with a patch. I was unable to get the [node: field-tags] to work given the steps here. It looks like maybe an issue with the token module. They have since released beta_4 just recently and now use [node: field_tags] (see underscore). Would it be a simple fix to change the code to work with this new token format since they will be going forward with this format?

valthebald’s picture

Status: Needs work » Needs review

metatags_quick_extra (ships with metatags_quick) suggests another solution for tokens in field values, could you check that please

valthebald’s picture

Status: Needs review » Closed (fixed)