Closed (fixed)
Project:
Feed Element Mapper
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
28 Mar 2008 at 04:46 UTC
Updated:
9 Sep 2008 at 09:29 UTC
Jump to comment: Most recent file
Comments
Comment #1
alex_b commentedIf you could get on this, it would be huge. I don't have much time for doing upgrading work these days and haven't upgraded any other module so far - I guess you'd be a lot faster than I.
Comment #2
SeanBannister commentedI'll see what I can do, been really busy though
Comment #3
designerbrent commentedSubscribe
Comment #4
Fayna commentedSubscribing also.
Comment #5
designerbrent commentedI've taken an initial stab at this. Ran down the changes from the coder module and fixed everything that it brought up. However, I'm sure that it doesn't fix everything including things like intergration with CCK. I enabled it and it seemed to install properly but there are quite a few errors that it threw once it was enabled.
I also know that there are problems with the hook_menu() function but I haven't had time to debug them more.
So here is the patch if someone else wants to look at it and take a stab at moving it along.
Comment #6
alex_b commentedthanks for posting. testers feel encouraged!
Comment #7
John Bryan commentedSubscribing
Looking to upgrade a local Cancer charity site with numerous catagorised feeds from Drupal 5 to Drupal 6. FeedAPI sound like a good longterm replacement for FeedParser but not suitable without this module available 8¬(
So all the best to anyone working on this.
Comment #8
niklp commentedSubscribing (sorry)
Comment #9
fluxline commentedfirst off, thank you for putting this out there for us. second, i see the mapper as the more powerful of the two, mapper and feedapi. it would be a great help to have a drupal 6 version available. please ...
... with suger on top!
Comment #10
alex_b commentedI worked a bit on this patch last week I couldn't finish though and now I'm getting caught up here in other work - posting my intermediate results.
Outstanding:
- finish menu API conversion
- taxonomy mapper not showing up because taxonomy on node not in $node->taxonomy anymore
- test other mappers
Comment #11
geodaniel commentedsubscribing
Comment #12
happysnowmantech commentedsubscribing
Comment #13
Maitreya commentedSubscribing
Comment #14
subscribe commentedPatched module doesn't work... what to do?
Comment #15
alex_b commented#14: it doesn't, missing items as in #10 remain :) I don't have the time to work on this atm, but the outstanding tasks are no rocket science. Would appreciate it if somebody could step up.
Comment #16
greg.harveyMight take this on. Downloading now.
Comment #17
happysnowmantech commentedOk, I'm getting a little antsy to use this in D6, so I'm motivated to help. greg.harvey, please let me know how far you get and if you want help.
Comment #18
greg.harveyActually, company said I couldn't spend time on this (fair enough - I'm a contractor and it's their money I'm spending). =(
FYI, we opted for a different approach. Using the Services module in combination with the Views module. Services exposes a 'views.getView' method which allows you to retrieve the results of a node view, AS NODES! Since my whole model was needing to transfer nodes across the 'net from one Drupal instance to another, intact and identical, this works much better for me.
I set up a the Services module and a view on my "distribution" site listing all nodes created or updated in the last 24 hours, by type (using an argument) and then on my "recipient" site I write a small module which runs with cron and calls the 'views.getView' method on the "distribution" site's web service, which responds with a list of all the new and changed content. Each node is in the correct format in a nested array. For each node in the returned array, convert it to a proper node object, node_save($node), job done! =)
Obviously there are some other little niggles to circumvent, but it works well. When I'm done I'll write a HOWTO.
Ps - don't get me wrong, Feed Element Mapper is still a great module and a port of this is to Drupal 6 still a valuable contribution to the community. It just so happens there is a better solution for my specific problem, but I can think of many instances where I would still use this module. =)
Comment #19
letrice commentedSubscribe
Comment #20
gzfelix commentedSubscribe
Comment #21
pkej commentedsubscribe
Comment #22
alex ua commentedWe're going to need this for a client this week so we'll try to finish patching it...
Comment #23
krishaamer commentedGreat! Hope this gets updated.
Comment #24
VenDG commentedsubscribe
Comment #25
Markpanzee commentedsubscribe
Comment #26
blackdog commentedsub
Comment #27
skizzo commentedsubscribing
Comment #28
tebb commentedSubscribing
Comment #29
momper commentedsubscribing
Comment #30
toma commentedSubscribing
Comment #31
dipen chaudhary commentedhi,
I've been trying to help in the port and spent a lot of time understanding functionality of module and the workflow. I strongly think the problem is in these lines. I mean major problem.
As the above code does not return as full populated $form object. I have been trying with emvideo and text widget on a new cck type and $form[#node] does not have those fields, which in turn is used by _feedapi_mapper_get_field_names() function to get the field names and run it through feedapi_mapper hook.
Basically at end of it in feedapi_mapper_emvideo.inc $field is empty and hence no list or mapper is returned.
Finally, I am not sure why drupal_retrieve_form() does not return the baked $form object, this function should coordinate with cck to get the $form object right? $form_state variable looks fine to me as I checked some drupal_* functions and thats how they prepare it.
Any thoughts? More on this later.
Comment #32
John Bryan commentedThanks Dipen for the input & feedback.
It gives a chance for others like myself to help without starting from scratch (if ever by some miracle I get some time and also solve my current CVS problem).
Comment #33
glassgrrl commentedSubscribing
Comment #34
rbl commentedsubscribing
Comment #35
yellek commentedsubscribing
Comment #36
iem2509 commentedsubscribing
Comment #37
alex_b commented#31 this is the part that's not ported yet. FEMP tries to figure out what "fields" are available on the target feed item node type by building its form.
The structure of the node form has changed and probably this approach needs to be rethought...
I'm on vacation this week, won't come around to look into this.
Comment #38
oriol_e9gsubscribing... I'm not a coder but I can help with the test.
Comment #39
loze commentedsubscribing
Comment #40
loze commentedI'm going to attempt to make this work, has anyone made any more progress other than whats posted on this page?
Comment #41
loze commentedI got it working (sort of) this is my first patch ever and I'm not sure i generated it correctly, but here it is
its a patch for the d5 version to 6, building off the patch submitted above.
go easy on me :)
Comment #42
blackdog commentedloze: great work! This works quite good. I've tried it with some CCK text fields as well as a taxonomy field, and it seems to work.
I've just cleaned the patch up a bit, runned it through Coder to fix som minor issues.
Comment #43
oriol_e9gIs it possible to create a new Feed Element Mapper 6.x branch with this code? It would be better to work with a separated branch.
Comment #44
alex_b commented#43: I just committed. Please open new issues for bugs etc. coming up with Drupal 6 version.
Comment #45
oriol_e9gComment #46
iem2509 commentedLooks like it works for embedded video. Converted over this mapper.
Comment #47
alex_b commented#46 - please post as a patch against 6.x in a new issue. This issue is closed.
Comment #48
greg.harveyMarking as closed - could someone post a link to the new issue for subscribers to follow? =)
Comment #49
alex_b commented#48: http://drupal.org/project/issues/feedapi_mapper ;) Please post new issues for bugs/requests with 6.x version. There where no new issues posted so far.