Closed (works as designed)
Project:
Feeds
Version:
7.x-2.x-dev
Component:
Feeds Import
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
6 Jul 2012 at 18:36 UTC
Updated:
7 Jul 2012 at 17:11 UTC
This problem is killing me and I've tried so many different things to troubleshoot I can barely keep things straight anymore....
Using Domain Access to create subdomains on our site...we currently have the root or default at example.com or www.example.com. Everything else is like so: subdomain1.example.com, subdomain2.example.com ...etc.
We are using the SQL parser to query a table that is within the drupal db. Fairly complicated query with 4 joins. It started out working fine, but has periodically quit working. Cannot delete feed items anymore, cannot import feed items anymore. We've monkeyed around with renaming fields, rebuilding queries, trying flat file imports, and cloning a couple times to get it working again, only to have it break again at seemingly random times.
In retrospect, the only possible common culprit that we can come up with is that we may have been working in one domain to import the feeds originally, and then possibly deleted them (in order to reimport modified data) from a different domain .
In other words, you can import/delete to your heart's content, as long as you're in the original domain you imported from. but if you happen to delete feeds items from a different domain, then all import/delete functions stop working. Deleting produces "no items to delete", importing just produces "0 items imported".
The SQL parser in the importer setup works fine, and the pre-fetch shows the correct results from the query. But somewhere, there is either a flag that I haven't found to get rid of, or the code is somehow in a dead-end that I cannot figure out how remediate. Unfortunately while I have produced a couple of errors here and there that may, or may not be related, the vast majority of the time importing produces no errors or other indication of its failing, other than to taunt me with the fact that it imported nothing.
I have attached a screen shot of one set of errors that I found relevatory, but that I have not been able to reproduce, nor can I say exactly how they were produced in the first place. I think it happened during an importer delete routine, but I'm not 100% sure of that.
Please, if anyone knows where I should be looking to get this cleared up - please let me know. My sanity, and this entire project is somewhat staked on this issue.
Thanks.
| Comment | File | Size | Author |
|---|---|---|---|
| domain error.JPG | 105.65 KB | timmay |
Comments
Comment #1
timmay commentedchanged to bug report
Comment #2
timmay commentedI can't decide how to feel about this...somewhat stupid on my part, but at the same time, there is room for confusion.
The problem turned out to be that our importers were set up to import to a standalone form. And unfortunately, we were unchecking the "Import on Submission" because we took it to mean "every time new content is added, re-import", which is not something we wanted. What this really means is that if you're importing to a standalone form, checking/unchecking this option effectively means your disabling/enabling the import task. You can still click on the Import button, but you get no result.
I still can't believe that such a simple problem caused us so much pain. The help text for this option currently says
, which I'll admit, sort of explains the situation, but is barely noticeable for the effect that it can have. It also assumes that you understand inherently the implications of importing to a standalone versus a content item.
Hopefully, this helps someone. I don't have a good suggestion for what it should say, but maybe at least a link to documentation, if such a page exists.