Ability to use tokens, from other tampered sources

Created on 12 February 2025, 3 months ago

Problem/Motivation

It seems if I have a Feed with two sources, if I create a tamper for one source to alter it's value, and then for the second source, use the replace tamper, to append the value from the first source, what I get is the original, un-tampered value. Not the modified one from my first tamper.

So how can I insert a tampered version of the first value if at all? I suppose this is just the way it is, but it would be a nice option to have.

✨ Feature request
Status

Active

Version

2.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States bburg Washington D.C.

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @bburg
  • πŸ‡³πŸ‡±Netherlands megachriz

    I noticed this too. There appears to be a flaw in the design for making this intuitive. I found out that if I manually edit the weights of the Tamper instances, you can get a chain like this work in the right order.

    The flaw is that you order Tamper instances per source. But if tampering one source is dependent of tampering of an other source, then you would need to manually adjust the weights to get things executed in the right order. So the weight of the tamper of source one would for example need to be 0 and then the weight of the replace tamper would need to be 1. If they are both 0, it is possible that the replace tamper gets handled first.

    Suggestions for making this process more intuitive are welcome. πŸ™‚
    I am thinking of a preview feature myself, but I'm not sure yet how that would need to look like in the Feeds Tamper interface. And if it makes sense to provide a preview feature there. Because my idea was to add a preview feature to the mapping page that would look like the Feeds Import Preview β†’ module that I wrote for the D7 version of Feeds.

Production build 0.71.5 2024