When trying to retrieve leech items, the following errors are displayed, one set per leech item:

# warning: Illegal offset type in C:\xampp\htdocs\thrillus5\modules\taxonomy\taxonomy.module on line 1150.
# warning: Illegal offset type in C:\xampp\htdocs\thrillus5\modules\taxonomy\taxonomy.module on line 1151.
# warning: Illegal offset type in C:\xampp\htdocs\thrillus5\modules\taxonomy\taxonomy.module on line 1154.

Comments

aron novak’s picture

aron novak
Primary language Hungarian
Location Hungary, Budapest
commented
Assigned: Unassigned » aron novak

Can you tell me that you use Yahoo Terms module or not? Do you know that leech switch from leech_yahoo_terms to Yahoo Terms module? This is a standalone module w/ a connector to leech.

aron novak’s picture

aron novak
Primary language Hungarian
Location Hungary, Budapest
commented
Status: Active » Postponed (maintainer needs more info)

Have you turned on this: Leech feed taxonomy?

Thanks for the information in advance!

zoon_unit’s picture

zoon_unit commented

Have you turned on this: Leech feed taxonomy?

No.

In fact, I've never used that module in 1.7 or prior to 1.7.

aron novak’s picture

aron novak
Primary language Hungarian
Location Hungary, Budapest
commented

Ok. Have you experienced this for all of your feeds or only a specific one?
Please send me the URL of one of the problematic feeds! It would be a great help if you can send a dump of the leech, leech_news_items and leech_news_feed sql tables.
Do you use PHP4 or PHP5?
First I have to be able to reproduce the problem, without this i cannot fix.

deelight’s picture

deelight commented

I encountered the exact same bug, but i'm not using the Leech module. Investigating on this problem lead me to the pathauto module. Are you also using it ?

taqwa’s picture

taqwa commented

I have the same bug and yes I'm using pathauto but I have the newest one. Do you know of any working patches that haven't been incorporated into the release?

zoon_unit’s picture

zoon_unit commented

This error is a tricky one. The error does occur within Pathauto (I have the latest one) however, it is only TRIGGERED by feed items from leech. I don't get this error from any other nodes or in any other circumstances.

I even spent several days rebuilding my website from scratch in 5.0, with the latest modules, to remove any old cruft from prior versions, then installed leech fresh. I STILL get copious errors.

I've spent well over 40 hours trying to get leech to work, so I've moved on to simplefeed instead. It "had" one parsing error of its own, but I've found a fix for it. (see the issues queue)

alex_b’s picture

alex_b commented

What are the settings on pathauto that you're using?

gaijinu’s picture

gaijinu commented

Had the same problem, in admin/settings/leech -> "Advanced leech settings" check "Pass on taxonomy from feed to feed items" and the errors will go away...
Drupal 5.1
leech 5.x-1.8
no yahoo term module

hth

alex_b’s picture

alex_b commented

gaijinu,

do you have pathauto turned on?

keesje’s picture

keesje commented

Hi,

Sorry to interrupt. Have same problem. Yes, I have Pathauto enabled. I just disabled it, problem disappears. Any suggestions?

Website Nijkerk

keesje’s picture

keesje commented

In addition:

Suggested configuration in #9 does not solve in my case, this was all ready turned on.

My answer on #8:
Pathauto:
My nodepath settings
node: [catpath]/[title]
category: [catpath]

keesje’s picture

keesje commented

In addition2:

It doesn't matter if I remove [catpath] from the pathauto settings, contrary to my expectations.

Even with node settings blank (no alias is generated) the error occurs.

Beats me...

keesje’s picture

keesje commented

Reading this post: http://drupal.org/node/123001#comment-265751 and it's parent thread,

I believe it's a Pathauto thing, not a Leech issue.

keesje’s picture

keesje commented

Pathauto it is.

Applying pathauto_value_cast.patch posted in mentioned thread is a fix for this problem. Pathauto should update soon.

alex_b’s picture

alex_b commented
Status: Postponed (maintainer needs more info) » Fixed

Fixed, then - right?

keesje’s picture

keesje commented

As far as I can see, yes, fixed.

Thanks

web applicaties

Anonymous’s picture

(not verified) commented
Status: Fixed » Closed (fixed)