Closed (fixed)
Project:
Feeds entity processor
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Oct 2015 at 14:39 UTC
Updated:
4 Nov 2015 at 14:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
computerbarry commentedFor the record, the default Title does show, it's only my Entity bundles fields that don't.
See attached. Thanks.
Comment #3
megachrizI noticed this too a few days ago. It is caused by a combination of changes in these two issues:
This added the hook
hook_feeds_processor_targets()+ a clever solution to invoke it when a processor only invokeshook_feeds_processor_targets_alter().This made the processor to lookup mapping targets twice during one request. The clever solution from above works only the first time.
I opened an issue in Feeds to extend the clever solution so the right hooks are also invoked when looking up mapping targets a second time: #2584157: Missing mapping targets in the UI for contrib processors
And here is a patch to let the Feeds entity processor to invoke
hook_feeds_processor_targets()itself which should solve the problem for itself. (The other issue is made for processors that haven't adapted yet.)Comment #4
computerbarry commentedGood catch :)
I've just added the patch, all mappings are now showing, works good MegaChriz, thanks for the patch and update.
Will report anymore issues, also keep an eye on the feeds issue.
Just wondering if, and when will this patch be added to the module itself for download?
Cheers, Barry
Comment #5
megachrizAs soon I have time to commit it. Thanks for reporting back that the patch worked for you.
Comment #6
computerbarry commentedCool :)
See attached for confirmation.
Just to confirm, after adding the patch:
Cheers, Barry
One question MegaChriz, with all the buzz around Drupal 8 lifting off:
Where does that leave us if we want this same functionality with D8? Or it will be sometime before we can do this?
Comment #8
megachrizCommitted #3.
@computerbarry
Unfortunately, a D8 version of this functionality seems to be lightyears away. At the moment I'm still focussing on the D7 version of Feeds, which I hope to bring to a stable release someday. As soon as that is done I can shift my focus to the D8 version of Feeds, for which first a UI revamp is planned (see #2443471: Implement configurable parsers.). Given that I can only spend a few hours a week on Feeds, I would need help from other developers in the community to accomplish that.
If you would like to help, you could help a lot with answering support requests in the Feeds issue queue and in trying to reproduce bugs that others reported. Would you like to do that? I know we are all busy of course, so feel free to say no. It's so easy to get too much work on your plate. I need to take care of that too, so in that light I would say no D8 version of this module in the nearby future.
Comment #9
computerbarry commentedIn a way, that's good to know, I don't have to learn D8 just yet :)
I feel quite privileged for you to ask me MegaChriz, I wish I could help, though I think I'd cause more problems than solutions :(
My PHP coding skills are very basic/limited and after looking of the issue list, truthly, I have no idea how to fix most. I will keep an eye on things, if I see any I can help with, by all means I will help out.
Thanks, Barry
Comment #10
megachriz@computerbarry
You don't necessary need to have PHP skills if you would like to help. You don't even need to know how to fix issues to help. For example, when someone reports a bug, but with limited info to reproduce it, you could already help a lot by trying to reproduce the bug and if you succeed to do so, provide the steps to reproduce it, so someone who can fix it have to spend less time figuring out what the bug is about (and if it is really a bug or just a configuration error).
A good guide to start is the Bug Squad guide that is used for Views (note that "Start at the back of queue" is less useful to apply to the Feeds issue queue as the oldest issues are more than 4 years old and therefore less likely to be still relevant).
Again, don't feel compulsory to do this. Only if you would like to help and have time to do so. Because before you know it, suddenly all your free time is swallowed by this project (which sort of happens to me from time to time).
Comment #11
computerbarry commentedCool, thanks for that MegaChriz, was feeling a little bad if I don't help :)
Barry