Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.This began after the Semptember 29, dev build. It was most likely introduced on the October 1 build.
Going to view a FeedAPI enabled node:
* warning: Illegal offset type in isset or empty in /DrupalTest/includes/path.inc on line 64.
* warning: Illegal offset type in /DrupalTest/includes/path.inc on line 69.
* warning: preg_match() expects parameter 2 to be string, array given in /DrupalTest/includes/bootstrap.inc on line 723.
Comments
Comment #1
Büke Beyond commentedView and Refresh tabs show the warnings. Remove Items asks for the confirmation without the warnings, and Edit is fine too. This might help.
Comment #2
aron novakDo you still have the errors?
Do you have a localized version of FeedAPI?
Comment #3
Büke Beyond commentedI investigated the problem more:
Recently, the contents of the feedapi_node_views directory has been mostly emptied. So updating FeedAPI from an overwrite will leave these files still in effect.
A clean installation of the October 9 dev version removes the problem messages.
Thank you for asking.
Comment #4
Büke Beyond commentedA clean update (removing the old feedapi directory) is required.
Comment #5
spiffyd commentedThe latest dev did fix this problem, but upon feed creation/refresh, I get a white screen with this:
ArrayArrayArrayArrayArrayArrayArrayArrayArrayArrayArrayArrayArrayArrayArrayArrayArrayArrayArrayArrayArrayArrayArrayArrayArray
I believe each Array refers to each feed item imported.
There is no problem importing the feeds though... they all show up.
Comment #6
aron novakspiffyd: you mention importing the feeds. Do you use the OPML import feature? It's confusing because at the previous paragraph you talk about "feed item imported".
Do you still experience this bug?
Make sure you don't use a patched version of feedapi. It looks like the source code that you use contains a print statement somewhere... FeedAPI code does not contain any print or dprint_r function call.
Comment #7
aron novakspiffyd: you mention importing the feeds. Do you use the OPML import feature? It's confusing because at the previous paragraph you talk about "feed item imported".
Do you still experience this bug?
Make sure you don't use a patched version of feedapi. It looks like the source code that you use contains a print statement somewhere... FeedAPI code does not contain any print or dprint_r function call.
Comment #8
spiffyd commentedNo iI was not using the OPML import feature but SimplePie. I think the latest DEV fixed the issue as I cannot reproduce the Array error anymore.