Warning: include_once(mapper_soort.php)

Hello

I've used Bram's component on Jooma 1.5 and 2.5 platforms, with success, but I have a problem with Joomla 3.3.0.

In Datafeeds backend under the 'Import Data' menu item I get this:

All feeds are up to date

Warning: include_once(mapper_soort.php) [function.include-once]: failed to open stream: No such file or directory in /home/villaazl/public_html/administrator/components/com_datafeeds/cron/feeds.php on line 59

Warning: include_once() [function.include]: Failed opening 'mapper_soort.php' for inclusion (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/villaaz/public_html/administrator/components/com_datafeeds/cron/feeds.php on line 59
Cleanup of unpublised feed items : 0.000
3457 items in database : 0.000
Optimize start : 0.015
2014-06-08T11:50:24+01:00
System load:0,0.01,0.05
Clean End : 0.015
3457 items in database : 0.015

Line 59 in feeds.php = include_once('mapper_soort.php');

Can anyone give any idea as to where I find mapper_soort.php or why/what is happening here?

Thanks for any assistance!

Davidh

i don't have that line and file !!

somehow feeds.php from the demo install and from the normal package got mixed up, please remove the line.

sorry for the inconvenience

Hi Bram

Thanks for getting back, I figured it out yesterday.

Saw your reply this morning, when I came back to the forum, to say that I'd commented-out the line and all appears to be working OK now.

I do have a report arriving by email:

key not existing: image images_image_image_0

Don't know what that's about, but I'll try and work that out too!

Kind regards and thanks

David

in the feed configuration you map feed-fields to database fields.

feeds change and whenever you use a field from the feed that doesn't exist any more you will get the message.


and from the weird fieldname 'images_image_image_0' it appears that you are using a wrong xml parser for the feed.

Hi Bram

Thanks for the info. - much appreciated.

I'm using the XML2U parser which you built for me in February 2012, and I've re-mapped the fields to suit.

As I say, it appears to still work OK on J3.3.0, as it did on J1.5.26 & J2.5.19.

I haven't received that message since, and it was only once.

Kind regards

David