Rewrite - how to use replacement patterns

This was fixed in beta3. The help text was missing. The replacement patters look like [source_name].

No, PHP code cannot be used.

sorry to re-open this -- but I'm also having trouble with this issue (replacement patterns not working). On my site, the replacement tokens are not being 'replaced' during the node creation. I've typed them into the Replacement Pattern form just as they appear below in the 'available replacement patterns' list -- but they are imported simply as text strings, (e.g., "[source_name]" in the tampered field) once the import takes place.

I've got token enabled -- is there a setting I'm missing? thanks

added: I've been playing with it more - I created a new cck type and a new import feed for it. On that content type, the feeds tamper module works correctly on some fields, but not all. It will rewrite (using tokens) a text field - but if I try to rewrite the 'body' field, it simply puts the tokens in as text (as above)....

would feeds tamper treat a cck field DIFFERENTLY than a standard node field such as body? I'm thinking this might have to do with permissions/node access or some such thing -- but so far I haven't figured it out....

Solved - (at least I think so). The titles of the fields I was importing were capitalized - e.g., "Scanned Item". In the Available Replacement Patterns list - this would appear as: [Scanned Item].

however, in order for it to work, it must be entered into the Replacement Pattern box as: [scanned item].

I hope this saves someone else a few hours of headache.... (thanks to everyone who works on this module...it's really a great tool), cheers.

Solved - (at least I think so). The titles of the fields I was importing were capitalized - e.g., "Scanned Item". In the Available Replacement Patterns list - this would appear as: [Scanned Item].

however, in order for it to work, it must be entered into the Replacement Pattern box as: [scanned item].

I hope this saves someone else a few hours of headache.... (thanks to everyone who works on this module...it's really a great tool), cheers.

Yes, this solve the problem, but it seems to me a bug to fix.

I would upload a proposed patch that show on the list of "Replacement Pattern" the right replacement

I'm confused; should the "Available Replacement Patterns" fieldset (?) be collapsible? on my site, it isn't collapsible, and thus there are no replacement patterns... What would the expected behaviour be?

I had the same issue with tokens not being replaced when importing users. Changing the tokens to lowercase solved the problem for me as well.

@asb - I'm using the Rubik theme and I get a list of "Available Replacement Patterns" from the collapsed fieldset shown uncollapsed in the attached screenshot.

@shawngo: Thanks for the screenshot. This seems not to work for 'Fusion' based themes :-(

Running JQuery Update 1.3.2 and jQuery UI 1.7.3. Are there other dependencies?

Yup, the tokens do need to be lower case, and not as displayed in the UI.

I just downloaded the current dev version and the token suggestions are now listed in all lower case, compared to Beta3 version that lists them as shown in the csv file.

Thanks for seeing the capitalization issue. I couldn't see what was wrong. Problem solved.

In my case, the release tagged as "recommended" simply wasn't working at all. Updating to the current dev release fixed the issue for me. Actually it's incredible what this module does, very helpful and highly recommendable. But don't use the "recommended" release ;)

help text is still missing in beta 3

uninstalled beta 3 and installed -dev
Still no help text and suggested replacment patterns.
I am using theme seven for the admin.

Can someone give me some directions??

thanks

Can you give this a try?

Is the patch for the -dev and / or for the beta 3?

At this moment I reinstalled beta 3 (uninstalled -dev).
because of this problem:

http://drupal.org/node/1694062

So can I use the patch for beta-3

thx

oke the problem i mentioned before http://drupal.org/node/1694062
also occured in beta-3

Hey, lowercasing the tokens saved me some time.

Cheers
Chris

Solution from #5 worked for me too, thanks a ton!!

This should be fixed. Please do not re-open this issue, there are too many different problems being reported. If you have a problem with the latest release, please create a new issue.

http://drupalcode.org/project/feeds_tamper.git/commit/13beb7d

Thanks #5 this was driving me nuts!