Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Trying to configure a feeds tamper -- feeds is installed and running correctly. I have permissions for feeds tamper.
I've created a test feedstamper plug in, and tried to 'enable' it -- but the checkbox clears itself when I hit 'save'. Is there a setting I'm missing?
Comments
Comment #1
verres CreditAttribution: verres commentedeven stranger...is if I clone the default 'node importer'....I can create/enable feed tamper plug-ins.... just not with the importers I had previously created. I've double checked all the settings of the importers and they're identical to the 'default' node import settings. Why would some importers allow feed tamper plug-ins, while others don't? again, I keep thinking there must be some setting i'm not aware of.... but so far, I can't seem to see it. Thanks, C
Comment #2
timoguic CreditAttribution: timoguic commentedSame problem here, cannot keep the 'enabled' checkbox checked at http://mysite/admin/build/feeds/edit/my_feed/mapping. This importer is using the standalone form (not tied to a content type).
I did not manage to find what the problem was...
Thanks!
Comment #3
RockSoup CreditAttribution: RockSoup commentedI am also experiencing this error, but on D7. Should I make a new issue?
Comment #4
RockSoup CreditAttribution: RockSoup commentedI switched to dev and got it to work.
Comment #5
Sinan Erdem CreditAttribution: Sinan Erdem commented6.x.dev doesn't work either...
Comment #6
stefan81 CreditAttribution: stefan81 commentedsame issue here.
I am trying to apply a "explode" plugin on a taxonomy field.
But cant activate it...
6.x.dev doesn't work either...
Other plugins like "find replace" appear to work
Comment #7
architectJpres CreditAttribution: architectJpres commentedI too am having this issue on explode, although upgraded to dev and seems to work
Comment #8
wizonesolutionsExperiencing the same issue on 6.x-1.x-dev. I've removed and re-added the plugin, too.
Comment #9
wizonesolutionsComment #10
wizonesolutionsCreating another plugin fixed this for me.
Comment #11
picxelplay CreditAttribution: picxelplay commentedI did extensive testing, and the way to keep the check boxes checked is to NOT press the save button on the plugins overview page (admin/build/feeds_tamper/edit/MY_NAMED_IMPORT. Once you press the save button, all your checks will be gone. So just add your plugins, and that's it. Then it will work fine.
Comment #12
harrybw CreditAttribution: harrybw commentedI am having this same issue. I will do as pixelplay has done but it does make things difficult if you get the ordering wrong. Twistor, thanks for a great module. Would love it if you could assist with this.
I am using D7 dev version. I was using beta2 but the plugins seemed to have no effect on imported data.
Thanks,
harry
Comment #13
vinmassaro CreditAttribution: vinmassaro commentedI am having the same issue with this module. I can't get any transformations to work at all. I tried harrybw's advice in #12 and I can see it enabled in my plugin list, but no transformations happen then. If I hit 'Save', it becomes unchecked and still doesn't work.
Comment #14
twistor CreditAttribution: twistor commentedI haven't been able to reproduce this at all. Can anyone give me details about their setup, so that I may be able to reproduce this?
Comment #15
vinmassaro CreditAttribution: vinmassaro commentedAdding an explode plugin to the node importer that comes with feeds performs the transformations for me. When I add a tamper plugin to the field of a custom importer, no transformation happens. In this case, I added a 'Convert case' -> 'uppercase' plugin to the title field and imported some nodes. When I add the same plugin to my own contact type and a CCK text field, no transformation occurs upon import. The strange thing is that if I add a plugin to all fields then uncheck them all and hit save, then re-check them all and hit save, only some of them stay enabled.
Pressflow 6.16 (tried updating to 6.22 as well, no difference)
Modules:
CCK 6.x-2.9
Ctools 6.x-1.8
Context
Feeds 6.x-1.0-beta10
Feeds Tamper 6.x-1.x-dev or 6.x-1.0-beta2, tried with both
Comment #16
vinmassaro CreditAttribution: vinmassaro commentedUpdated to the 6.x-1.x-dev (2011-Jul-23) and creating a new plugin enables it by default fine. I can do an import and the plugin works as expected. When I uncheck it and click save, it disables it, and if I re-check it and hit save, it remains greyed out - I cannot re-enable the plugin. It is also not possible to delete it at this point since there is no link. If I try to force it by going to /admin/build/feeds/tamper/delete/[plugin_machine_name], I get a white screen. This is the explode plugin on a CCK multi-value text field.
Comment #17
twistor CreditAttribution: twistor commentedYou don't by any chance have spaces in your source names?
What Parser are you using? And what do the mappings look like?
Comment #18
wizonesolutionsJust to contribute - spaces in source column names were causing this issue for me. Still having another issue that I'll post separately.
Comment #19
twistor CreditAttribution: twistor commentedTentatively marking as fixed. Let me know if it's not.
Comment #21
Anonymous (not verified) CreditAttribution: Anonymous commentedI cannot see it as fixed yet on Drupal 7.
Just pointing out where the problem occurs on the code is:
around line 388 on the file feeds_tamper_ui.admin.inc.
When you comment out those lines, it will correct the issues. As the id gets a NULL on those lines which renders the Id field on the database obsolete.
Hope this helps to someone.
Comment #22
foopang CreditAttribution: foopang commentedSame problem here on Drupal 7.
@phpcitizen, I can't find the code above in the dev version.
Comment #23
AlsI have run on this same problem with current version for Drupal 6 (6.x-1.0-beta4). Solved installing current dev (6.x-1.x-dev on 2012-Jul-04).
Re-setting this bug to identify the currently "recommended" version as the flawed one.
*Current* dev (#9 mentioned it an year ago) should be seen as the "reviewed & tested by the community" .
Comment #24
twistor CreditAttribution: twistor commentedComment #25
devkinetic CreditAttribution: devkinetic commentedThis issue still exists in 6.x-dev