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...
| Comment | File | Size | Author |
|---|---|---|---|
| #26 | 1134192.patch | 518 bytes | valthebald |
Comments
Comment #1
valthebaldIt 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
Comment #2
JohnnyX commentedOk, 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 ;)
Comment #3
valthebaldPatch is here - http://drupal.org/files/issues/modules_token.92.patch
Reference issues: #691078: Field tokens, #1122486: Support for tokens in field values
Comment #4
JohnnyX commentedMany thanks! I'll try it with a test installation first ;)
Comment #5
JohnnyX commentedMh, 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...
Comment #6
valthebaldJust a moment, where did you put [node:field-tags] value? In keyword field? Did you use standard or minimal profile during install?
Comment #7
JohnnyX commentedI 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...
Comment #8
valthebaldNot sure if it can help, but try to put Tags (taxonomy) field before meta tags in node editing form
Comment #9
JohnnyX commentedTags were/ are before meta keywords. Doesn't work. Any other idea?
I also patched the beta and the dev release... same problem.
Comment #10
valthebaldto continue further need more details.
Did you check error logs? Anything suspicious? What other contrib modules enabled?
Comment #11
JohnnyX commentedChaos 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.
Comment #12
valthebaldNon-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?
Comment #13
JohnnyX commentedYes, I tried the patched version and than roll back to the working version ;) update.php and flush cache was done more than one time...
Comment #14
valthebaldI have run out f ideas :(
Comment #15
JohnnyX commentedMh, I'll give it a second try with a test installation soon...
Anybody get it work?
Comment #16
JohnnyX commentedI 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, keywordsresult:
testkeywordsAny idea how to fix it?
Comment #17
valthebald@JohnyX,
can you confirm using D7.2?
Comment #18
JohnnyX commentedYes! I upgraded my installation to D7.2.
Comment #19
JohnnyX commentedAny new information or plans about this issue/ feature request?
I found this issue:
http://drupal.org/node/1170820
Comment #20
valthebaldNo, #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.
Comment #21
JohnnyX commentedDid 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?
Comment #22
valthebaldYes, I used token 7.x-1.0-beta2 + patch, and it worked with taxonomy tokens as expected
Comment #23
JohnnyX commentedOk, I used the same.
Which token did you put into the field? Maybe I used a wrong token?!
Comment #24
valthebaldAh!
I never tried more than one term as a value, that's the point!
OK, I see the problem, will try to solve it
Comment #25
JohnnyX commentedAh, great! Thank you very much! :)
Comment #26
valthebaldPatch is done against 2.x, but would work with 1.x as well
Comment #27
JohnnyX commentedOk, thanks.
I'll update to 7.x.2-dev and test the patch ;)
Comment #28
JohnnyX commentedWorks fine in a test site! Many thanks :)
Comment #29
valthebaldComment #30
valthebaldChanging title to better describe the issue
Comment #32
TravelTechie commentedI 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?
Comment #33
valthebaldmetatags_quick_extra (ships with metatags_quick) suggests another solution for tokens in field values, could you check that please
Comment #34
valthebald