When attempting import, I'm getting a "URL Field Required" error. It's true that I don't have a URL field in my import but the node type has an automatic URL alias pattern set with pathauto. Even if I didn't, I don't understand why it would be required.

What could possibly be making node_import believe that I have a required URL field?

Comments

Robrecht Jacques’s picture

Robrecht Jacques commented

I think the error comes from a required CCK Link field. Is that possible? Or another CCK field that has some URL in it.

The "URL Path setings" probably is not causing the error, especially if you have pathauto. That field never is required as far as i know.

You can go to the node creation path (node/add) and see what URL needs to be filled in on that form.

cristianff’s picture

cristianff commented

I have the same problem: "URL field required" on step 7 when I import content, but it is even worse because my URL field is completed!!!

any idea??

websage_gr’s picture

websage_gr commented
Version: 6.x-1.x-dev » 6.x-1.1
Category: support » bug
Issue tags: +import csv node_import error url field required

Hi,

I was using node import without locale/internationalization, it was working fine before and didn't require the URL field. Now that I installed Spanish as another language it won't import anything.

So I guess this has to do with another language than English. Anyone else who can confirm that?

The error is thrown to this field:
cck:field_link:url

Even assigning a column on the csv to this field doesn't fix the problem. I tested with relative links up to
3 levels of hierarchy.

Some additional info:
Going back to the former default language, in my case English and disabling the additional language Spanish
couldn't fix the problem. Assigning a column or not even with absolute or relative URLs doesn't change anything on the error.

Best Regards

Frank

TrevorG’s picture

TrevorG commented
Status: Active » Needs review

I had the URL is Required error, and thankfully I'm doing a new simple site with no content yet. Feeds module caused my problem... disabled it and it went away. I think its because Feeds asks for a Feed URL on a content type.

indydas’s picture

indydas commented

Yep disabling the feeds module fixed it for me too.