Feeds module conflicts with creation of new Biblio records

I'm afraid I can't reproduce this error, so there's not much I can do right now. I've enabled feeds and all it's sub-modules (except "feeds fast news") and biblio still works fine for me.

I've got exactly the same bug. The bug appears because when a biblio is created, the first (automatic) post is made with an empty title.

Here a workaround:

In includes/FeedsConfigurable.inc, line 124, add a "if (...) { ... }" to prevent for not set $config:
public function addConfig($config) {
if (is_array($config)) {
$this->config = is_array($this->config) ? array_merge($this->config, $config) : $config;
$default_keys = $this->configDefaults();
$this->config = array_intersect_key($this->config, $default_keys);
}
}

In feeds.module, line 363, replace the error messages by warnings:
catch (Exception $e) {
drupal_set_message($e->getMessage(), 'warning');
drupal_set_message(t('Could not retrieve title from feed.'), 'warning');
}

I was finally able to reproduce this (strangely only when vertical tabs were enabled), and fix it.

It really was a Biblio issue not a Feeds issue. The root of the problem was that during the first stage of the Biblio form (publication type selection) the $node->type was removed which was subsequently causing issues with Feeds. This has been resolved in the Biblio module now.

http://drupalcode.org/project/biblio.git/commit/52a696c

Ron.

The same issue has surfaced again, but can be patched by the same fix mentioned in #3.

I tested this with a clean install of drupal-6.25, biblio 6.x-1.17, feeds 6.x-1.0-beta11 and other required modules.
- A feed must be created in order to get the error. - I used a CSV feed to test.

Please review and patch. :)
Thanks!

http://drupalcode.org/project/biblio.git/commit/52a696c

I've pushed a fix to the 6.x-1.x-dev branch. Have you considered using the 6.x-2.x branch? It's quite stable and has more features.

http://drupalcode.org/project/biblio.git/commit/335f05b

This version is no longer maintained. If this issue is still relevant to the Drupal 7 version, please re-open and provide details.