Hi all,

I am having a problem getting my "XML data document" to update to include the fields specified in the fields list. Basically I have added some of my custom CCK fields to the fields list, and they seem to be appearing in the query. But they do not show up in the xml output.

I have noticed a few other issues that mention similar issues, and defining relationships, however normally cck fields appear in view results without need to define relationships, so I am confused as to what I should configure, and whether this is a bug

Thanks,

Tom

Comments

tolland76’s picture

tolland76 commented
Category: support » bug

Ah, what it seems to be, is that "XML data document" picks up the fields list when the "Style" is set in basic settings, but does not update the fields list dynamically when the fields are subsequently changed. ie you have to set the fields before setting the style to "XML data document"

tolland76’s picture

tolland76 commented

errm that is not true either.
It seems not set certain fields like Node:link
but adding fields is reflected

mcfilms’s picture

mcfilms commented

I am discovering a similar issue. I DO get the extra fields to display in my XML output. But the XML created fails to validate. I am using the XML validator at:
http://schneegans.de/sv

Which tells ne it is well formed, but not valid. Errors include:

# No supported document type declaration was found, thus a standalone document declaration is assumed. This means that your document must not contain character entity references such as ' '.
# Your document lacks a namespace declaration such as '' in the document element. Only well-formedness constraints have been checked, while validity constraints have been ignored.
# The 'text/xml' media type is not supported. Use 'application/xml' instead.
# The root element does not comply with the schema. (3:2)

mcfilms’s picture

mcfilms commented

@tolland76 -- Please check the fields you are having trouble with. Have you enabled permissions for them?

allisterbeharry’s picture

allisterbeharry commented
Assigned: Unassigned » allisterbeharry
Category: bug » feature

The plugin in the next release will give you more control over the XML output - you can define what the root element will be and I'll use your example and add in options to define the namespace and the media type returned.

allisterbeharry’s picture

allisterbeharry commented
Category: feature » bug

I'll try to reproduce this, but have you looked for the field using the raw field id? A field with label Node:link might show up as node_link because the plugin only accesses the raw field id.

allisterbeharry’s picture

allisterbeharry commented
Status: Active » Fixed

Fixed in 6.x-1.0-beta1. CCK fields are now handled properly.

allisterbeharry’s picture

allisterbeharry commented

This should be fixed in 6.x-1.0-beta1. CCK fields are now handled properly.

Status: Fixed » Closed (fixed)

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