When importing to uc_products (uc2 from ni1.0rc4):
Fatal error: Call to undefined function uc_product_node_is_product() in ...\node_import\supported\ubercart\uc_product.inc on line 15

solution:

15c15
< if (($node_type = node_import_type_is_node($type)) !== FALSE && uc_product_node_is_product($node_type)) {
---
> if (($node_type = node_import_type_is_node($type)) !== FALSE && uc_product_is_product($node_type)) {

Comments

Alun’s picture

Status: Active » Fixed

If it is solved, its not really an issue then, is it?
This is a well documented change in Ubercart, and I believe has been fixed at least in the latest DEV release.

dkeays’s picture

I thought you might want to know about it. Apparently I didn't look close enough at the dev release.

Where would you expect this kind of information in the future?

joecanti’s picture

thanks for posting that dkeays - this solved my problem and now i can import all my products at the click of a button...you saved me hours of work :-)

Oh, and this was a good place to post it...put my error message into the forum search and came straight here!

Thanks again, Joe

Alun’s picture

Sorry, I came across a little snappy in the last post.

With node import, as it hasn't been updated in a while, the best solution, since it is in development anyway, is to download the dev copy. This fixes certain taxonomy issues when importing through ubercart aswell.

Robrecht's message about the fix which was applied to the CVS is here
http://drupal.org/cvs?commit=272836

Other posts referring to the same topic are
http://drupal.org/node/555202
http://drupal.org/node/647524
http://drupal.org/node/569596

Cheers!
Al

dkeays’s picture

No problem.

It turns out that this module didn't fit my needs 100% so I wrote my own. But while evaluating the module I ran into the problem above.

Would a module for price updates fit into your idea of the node_import module?

steps in the module:
1- update the price if the product exists
2- import a new product if the product doesn't exist

other considerations:
1- update/import products based on multiple fields (sku and gender)
2- update/import products based on a value entered at run time (vendor)

Alun’s picture

That pretty much goes along with what I am trying to do with Node Import myself. I suppose it contradicts the phrase 'import' and its more of a node_update thing.

I have a shop with over 40,000 items. The owner maintains a database on his computer, so he needs an update functionaility to change items, rather than have to delete them and upload new revisions. The SKU of the items always stays the same, prices, stock levels and other details are subject to change from upload to upload.

There are a number of posts focusing on building an update feature into node_import. I'm going to have a look at these and see what I can do over Christmas. I'll be sure to post back with my findings.

Related posts on the project are here.. I'm sure if you have developed some coding on updating nodes, they would love for you to get involved on the posts.
http://drupal.org/node/150397
http://drupal.org/node/349408#comment-1359732
http://drupal.org/node/422282

The last post is pretty close in terms of what I need, so it'll probably be the one I follow.

Hope that helps.
Al

kingandy’s picture

Status: Fixed » Reviewed & tested by the community

I can confirm that the posted amendment resolves the issue on the current 6.x-1.0-rc4 release.

Given that the change has not yet made it to a non-dev release, I'm changing the status of this issue to RTBC.

Maroli’s picture

Ahhhh

This node_import does not save anything to the database... How come???

Alun’s picture

What do you mean? What are you trying to import? are you getting any errors? etc etc..

hixster’s picture

Subscribing ...

Really need price update and merging for existing Product nodes in upcoming project

DrupalSza’s picture

Also THANK YOU! for posting this.
=)

Robrecht Jacques’s picture

Version: 6.x-1.0-rc4 » 6.x-1.x-dev
Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.