Hello,

I have a problem with the deployment module: When I try to deploy nodes from a node type, I always get the error:
Node / error / Parse error. Not well formed

There are no other errors in the logs of both drupal systems.

This node-type has the following fields
- some general CCK fields (text, ...)
- 1 filefield / imagefield (multiple values allowed)
- 1 location (1 value)
- 1 date (datestamp – textfield with calendar – 1 value - start and end date)

Are there any known problems with one of these field-types? What other problems could result in this error-message?

Deployment works correctly with simple node-types (like Drupal’s page) and node-types with location and general CCK fields. So the problem must be with one of the other fields.

My System:
Drupal 6.15

Drupal 1:
Deployment 6.x-1.x-dev (2009-Dez-10)

Drupal 2:
Deployment 6.x-1.x-dev (2009-Dez-10)
Services 6.x-2.x-dev (2009-Dez-25)

Comments

gdd’s picture

gdd
he/him
Primary language English
Location Portland, OR
commented

There are known problems with Date fields, the only combination that I know of working is using the Date field type with pulldown menus. These have to do with how Date interacts with drupal_execute(), and Date's maintainer has indicated that she is not willing to address these problems. There is a very long thread around this in the issue queue for the Node Import module, wherein they have had to jump through enormous hoops to even get partial Date functionality working

#374346: Can't import date values into Date module fields

Given the issues surrounding this I don't predict a solution being forthcoming anytime soon. If you can try your nodes without just the Date fields, they will probably work.

MJH’s picture

MJH commented

Thanks for your answer. The problem is indeed the date field. All my node-types without a date field can be deployed successfully. And if I deactivate the date-field in the other node-types, they get deployed successfully, too.

The problem: i especially need deployment for a node-type with a date field. And I can not get this working.
I normally use "datestamp – textfield with calendar – 1 value - start and end date".
For a test I switched to pulldown mode (and all other date widgets), and they do not work either is my case. All I get is the "Not well formed" - error.

Well I think I will have to look for another solution. But as it seems all other deploy/import-modules seem to have the same problems with date-widgets :(

gdd’s picture

gdd
he/him
Primary language English
Location Portland, OR
commented
Status: Active » Closed (won't fix)

I've documented this in a troubleshooting page in the handbook for future reference.

Rob Knight’s picture

Rob Knight commented

I'm experiencing the same problem, but without any date fields.

I do have a few contrib modules enabled which might be causing the problem (Omniture Node, Workflow, Printer-friendly Pages), but none of them seem to be adding complex data to nodes, so I can't see why these would be causing a problem.

Is there a good way of debugging this problem? Services doesn't seem to log useful error information.