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.
I have followed every example I can find, read every post I've seen 10 times. When I select XPath as my feed parser the only Source I have available under mappings is "Feed node: User ID". Surely I am missing something. Any help would be appreciated.
Comment | File | Size | Author |
---|---|---|---|
mapping.png | 15.14 KB | matttrax-1 |
Comments
Comment #1
brycesenz CreditAttribution: brycesenz commentedI just recently encounter this problem after upgradings from Feeds 6.x-1.0-beta4 to 6.x-1.0-beta5. I do not know in which module the error lies, but I have opened up an issue report in the Feeds queue #908862: Cannot name new sources.
Comment #2
matttrax-1 CreditAttribution: matttrax-1 commentedI downgraded Feeds to Beta4 and it is working like the tutorial describes. Thank you for getting back so quickly.
Comment #3
rbrownellI can confirm the problem. Subscribing...
Comment #4
alex_b CreditAttribution: alex_b commentedFeeds XPath Parser needs to overwrite getMappingSources() and return FALSE to be compatible with beta5. Just added this to the release notes.
Thank you for reporting.
Comment #5
twistor CreditAttribution: twistor commentedThanks, committed.
Comment #6
brycesenz CreditAttribution: brycesenz commentedActually, I don't think that this has been completely resolved. The latest Feeds XPath Dev version fixes one problem, but now there is not the Feeds functionality to let the feed items inherit taxonomy terms from the parent node.
Is there any way to allow fields to be imported to come EITHER from an XPath/REGEX/HTML query string OR to be inherited? Technically, that was possible before this fix, albeit with a very awkward user interface.
Comment #7
rbrownellI concure, though this is probably a Feeds issue and not a xPath Parser issue. They should design it similar to CCK's "use existing fields or create new ones".
This should be started as a new issue for Feeds.
Comment #8
twistor CreditAttribution: twistor commentedAt this time, it seems that inheritance is in compatible with this module. The fact that it was showing up at all was because of this bug. Opening a new issue for that.
Comment #9
brycesenz CreditAttribution: brycesenz commentedThanks twistor. For community reference, the new issue is here #911618: Add support for field inheritance..
Comment #10
fereira CreditAttribution: fereira commentedHere's what I have had to do. In the basic settings of the importer, change the "Attach to content type:" selection to "use standalone form". Then go add all your mappings. Then go back to the basic settings page and select the feed content type you want to attach to for the importer. It's a bit annoying, but it works with feeds version 6.x-1.0-beta5.
And, yes, this is a Feeds issue, not a feeds_xpathparser issue. I see the same behaviour when using the feeds_xmlparser module.
Comment #11
rbrownellIt is funny because I posted this issue on Feeds #632920: Inherit properties from parent feed node (taxonomy, author, OG, language) #226 and they seemed to disagree with me citing that the parsers were to blame.
-R
Comment #12
tyler-durden CreditAttribution: tyler-durden commentedfereira,
I am trying to recreate the steps you outlined in comment #10, but I am not getting any selection lists. I am using Feeds 6.x-1.0-beta7, do I need to do this on Beta5?
Also, the feed item is requesting a "parser" for the taxonomy field. Is this supposed to be happening? Thanks!
Comment #13
fereira CreditAttribution: fereira commentedI haven't tried feeds 6.x-1.0-beta7 yet so I don't know how things would work with that version. It looks like there were several things changed in the beta6 version related to taxonomy fields that have been described in the release notes.
Comment #14
twistor CreditAttribution: twistor commentedThis should be working in dev. Testing welcome. You will have to flush the caches because the REGEX and QueryPath parsers are gone.
Comment #15
tyler-durden CreditAttribution: tyler-durden commentedtwistor,
I'm a bit confused. I cannot find any dev. modules, only the standard Beta's. Beta7 is dated Sep 17th so it's only 4 days old, am I looking for something newer?
Comment #16
twistor CreditAttribution: twistor commentedThe dev module of this project.
Comment #17
tyler-durden CreditAttribution: tyler-durden commentedDoh! I feel like an idiot. Thanks! I'll do some testing later today.
Comment #18
tyler-durden CreditAttribution: tyler-durden commentedI have installed Feeds 6.x-1.0-beta7 and the latest Dev snapshot of Feeds XPath Parser, and when I try to select the "XPath XML parser" under the Parser options, I get the error below?
Fatal error: Class 'FeedsXPathParserBase' not found in ...sites/all/modules/feeds_xpathparser/FeedsXPathParser.inc on line 12
I cannot use Beta5 or earlier since it does not work with my xml file. Beta7 has worked flawlessly before I tried getting the taxonomy settings to transfer, where I am currently hung up on. Can anyone else confirm this error? I am going to try a fresh install again this evening before installing Beta5 to atleast see if the error goes away.
Comment #19
twistor CreditAttribution: twistor commentedCan you try clearing the cache?
Comment #20
tyler-durden CreditAttribution: tyler-durden commentedThat was the first thing I tried.
Comment #21
twistor CreditAttribution: twistor commentedCan you verify that "class FeedsXPathParserBase" is in FeedsXPathParser.inc?
Comment #22
tyler-durden CreditAttribution: tyler-durden commentedNot 100% sure what is being asked, but when I search for "FeedsXPathParserBase" in FeedsXPathParser.inc I get these three lines:
class FeedsXPathParserHTML extends FeedsXPathParserBase {
class FeedsXPathParserXML extends FeedsXPathParserBase {
class FeedsXPathParserBase extends FeedsParser {
Comment #23
tyler-durden CreditAttribution: tyler-durden commentedI am still not having any luck using Feeds Beta5 and Beta7 with multiple versions of the Xpath Parser module now. I feel like something basic is messed up as I have the example nodes enabled but do not see any, which I used to.
I am going to start over again with a fresh install of Drupal tomorrow and keep you updated.
Comment #24
tyler-durden CreditAttribution: tyler-durden commentedGoing to bed...
But I have confirmed I receive the same error on a new drupal install using Feeds Beta7 and the latest Dev snapshot of Feeds Xpath Parser.
Comment #25
bryanb229 CreditAttribution: bryanb229 commentedSubscribing...
Comment #26
brycesenz CreditAttribution: brycesenz commented@tyler-durden:
I'm using both of those modules, and things seem to be working just fine. I'm a little confused reading through this thread though, trying to piece together exactly how you're using the module. My setup and use case described are below; can you post how yours differs for reference?
- Drupal 6.19
- Chaos Tools 6.x-1.7
- Feeds 6.x-1.0-beta7
- Feeds XPath Parser 6.x-1.x-dev (2010-Sep-21 Release)
- Job Scheduler 6.x-1.0-beta3
Obviously, I've cleared my caches, run updates, etc. My Feed Importer setup is as below:
Basic Settings
Attached to: Feed Item
Refresh: every 1 day
Import on create
Fetcher
HTTP Fetcher
Download content from a URL.
Parser
XPath XML parser
Parse XML using XPath.
Processor
Node processor
Create and update nodes.
In the Mapping settings, I see a dropdown field that lets me select either "Feed node: Taxonomy: ", "Feed Node: User ID", or "XPath Expression", then map each of those options to a target.
Again, that's probably not all that helpful by itself, but if you let me know where your setup differs then I'll happily see if I can replicate/fix the issue.
Comment #27
tyler-durden CreditAttribution: tyler-durden commentedDrupal 6.17
Feeds 6.x-1.0-beta7
Feeds XPath Parser 6.x-1.x-dev (9/21)
Chaos tools 6.x-1.7
Job Scheduler 6.x-1.0-beta3
I have no problems when I install Feeds XPath Parser 6.x-1.01 dated June 28, but as soon as I upgrade to the latest Dev as soon as I try to select the xml parser I get the above error still. I have cleared cache multiple times and ran the update scripts to no avail.
The only difference in our setups are the Drupal versions. I likely will not have any more time until the weekend to work on this, and I need to upgrade to 6.19 anyways so I will do more testing after that and keep you updated.
Comment #28
tyler-durden CreditAttribution: tyler-durden commentedbrycesenz,
I just did a fresh install of Drupal 6.19 and installed these modules (the same ones you mentioned earlier).
- Chaos Tools 6.x-1.7
- Feeds 6.x-1.0-beta7
- Feeds XPath Parser 6.x-1.x-dev (2010-Sep-21 Release)
- Job Scheduler 6.x-1.0-beta3
I can get to the screen to change the Parser, but as soon as I click to select XPath XML parser, I get the same exact error.
Fatal error: Class 'FeedsXPathParserBase' not found in ...sites/all/modules/feeds_xpathparser/FeedsXPathParser.inc on line 12
Comment #29
Catalyst5 CreditAttribution: Catalyst5 commentedSame issue here
Only difference is that I am using:
C Tools 6.x-1.x-dev.tar.gz
Feeds beta 9
Comment #30
brycesenz CreditAttribution: brycesenz commentedOk,
I tried a fresh install of Drupal 6.19, CTool 6.x-1.7, Job Scheduler 6.x-1.0, Feeds 6.x-1.0-beat9, and Feeds XPath Parser 6.x-dev (the September 29 release).
I enabled the modules, then went to create a new feed importer. I go to the screen to change the parser, change to XML Parser, but the only message that I get is "Changed parser plugin." In short, I cannot reproduce this error.
A few notes - I'm using a newer version of XPath parser and of Feeds, so maybe that will fix the problem. But I'm not getting that error on either my local server or on a dummy URL from a shared host.
Comment #31
tyler-durden CreditAttribution: tyler-durden commentedbrycesenz,
Check out http://drupal.org/node/925138 - the new XPath Parser 6.x-dev dated Sep 29 resolved the issue and everything should be working ok.