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.
When updating feeds to the latest dev (sept-8-2012) I get the following error when editing a feed:
Notice: Trying to get property of non-object in feeds_tamper_ui_form_feeds_ui_mapping_form_alter() (line 136 of /sites/all/modules/contrib/feeds_tamper/feeds_tamper_ui/feeds_tamper_ui.module).
The interface on the edit form changed for feeds with this update, so I think it's simply breaking something that feeds tamper is using to display the tamper links.
Comment | File | Size | Author |
---|---|---|---|
#11 | feeds_tamper_ui.module_7.x1.0-beta4.1794482.patch.gz | 292 bytes | deltahex |
Comments
Comment #1
gittosj CreditAttribution: gittosj commentedI think you can work around this by disabling overlay (drush dis overlay) and the tamper plugins / fields are then visible. That said, I still can't get my taxonomy terms to import so I may be incorrect
Comment #2
Strompf CreditAttribution: Strompf commentedSame here. When I'm on the Feeds Importer's Mapping page and I click on Configure Feeds Tamper, I get an empty main screen. It didn't help to disable overlay (through the Modules page).
Goal was to import Übercart product data (nodes) that contain hierarchical taxonomical data.
Comment #3
Strompf CreditAttribution: Strompf commentedI uninstalled and deleted the recommended current version of Feeds Tamper, and installed the newest dev version (feeds_tamper-7.x-1.0-beta4+7-dev). Problem gone! The Feeds Tamper link has moved to a tab.
Comment #4
twistor CreditAttribution: twistor commentedThe latest dev is a tab, should have a new release soon.
Comment #5
1mundus CreditAttribution: 1mundus commentedI had the same problem until I updated beta-4 to the current dev version (using Feeds alpha-6).
Comment #6
vregouby CreditAttribution: vregouby commentedI get the same problem with beta4...
Actualy it is fine if I click on tamper in the list of feeds, but if I click on feeds tamper in the cartography page, I get the error.
I think this link on the cartography page should be gone with beta4, but I desinstalled and reinstalled feeds tamper, it is still here...
Comment #7
MrHaroldA CreditAttribution: MrHaroldA commented@vregouby: this should be fixed in the next version (-beta5?). You can always download the -dev version if you can't wait anymore ...
Comment #8
vregouby CreditAttribution: vregouby commented@MrHarold. Thanks a lot for the update. Now that I know which link to use, it's not really an issue any more. I'll wait for the next beta5 version.
Comment #9
johnvBetter title, and status for finding this issue.
The solution is : update to feeds tamper dev-version.
Comment #11
deltahex CreditAttribution: deltahex commentedpatch suggestion temp fix
Comment #12
Sinovchi CreditAttribution: Sinovchi commentedThe patch #11 fixes the problem when you use new dev version from 2013-May-12.
Thanx, deltahex!
Comment #13
bcreeves CreditAttribution: bcreeves commentedThis issue reemerges after updating to the May 11th dev release. I tried running the patch in #11 but it said:
patch: **** Only garbage was found in the patch input.
Comment #14
bcreeves CreditAttribution: bcreeves commentedComment #15
tmsimont CreditAttribution: tmsimont commentedusing latest dev worked for me without any patches
Comment #16
cknoebel CreditAttribution: cknoebel commentedI can confirm: the error doesn't appear with the latest dev.
Comment #17
polarsky CreditAttribution: polarsky commentedConfirmed: just used the latest dev version to get rid of the error. Thanks
Comment #18
alar CreditAttribution: alar commentedfeeds_tamper-7.x-1.x-dev works fine. And yes new tab is on the Feeds page
Edit | Export | Clone | Delete | Tamper
(not mapping like it used to be)
Comment #19
imperator_99 CreditAttribution: imperator_99 commentedConfirming also that the latest DEV version gets rid of the error.
Comment #20
MacSim CreditAttribution: MacSim commentedI had the same error using the version 7.x-1.0-beta4
Easy to resolve
Line 136 just change
to
Done, it's working like a charm !
Comment #21
Lumis CreditAttribution: Lumis commented@MacSim
Thank you a lot! Works here too now.
Comment #22
fStew CreditAttribution: fStew commented@MacSim
Worked for me too. I suggest submitting this patch as a fix
Comment #23
MrHaroldA CreditAttribution: MrHaroldA commentedLike said before a couple of times: this is already fixed a long time ago.