Warning on saving ticket

I'm looking into this.

Note to self: In order to change multiple fields on the Ajax callback, we actually have to replace the entire form object.

In trying to recreate this error, I came across some strangeness to report (see Create_ticket-1.png).

To get this I created a new ticket from the PM Dashboard and selected choices as shown which had been created for earlier testing. Initially, the choices available in the "Assigned to" drop-down were only Teams, which I selected and saved. However, the "save" didn't take and kicked me back to the screen shown. Then the drop-down choices change to PM Persons.

When I select a PMPerson and save, the ticket seems to be created OK, however I get this additional message. ( see Create_ticket-2.png).

Here's a patch.

Patch applied cleanly.

When creating a new ticket, the "Assigned to" drop-down populated with PMPersons which is good.

Then saving worked, however when save completed an undefined property error showed. (see attached)

I've just tried this on the demo site (http://drupal-7.project-management-module.org/pm/tickets/test-ticket-0) and it worked fine without any error messages.

Are there any specific circumstances that you see this error, or all the time?

I'm struggling to reproduce it.

Committed that patch. Keeping this issue open to track that warning.

I see these errors too on my local installation.

This is because the date fields are not working yet.
They are not added to the $node object and the error occurs, because the properties are not existing when trying to get them from the object with $node->dateend;.

I have just commented out all lines with datebegin/dateend.
We better just directly add the new date fields with Field API.

Patch applied cleanly. Could edit Organization, Project, Task, Duration Unit and Price Mode and save without throwing any errors/warnings.

Coder says " Coder found 1 projects, 6 files, 17 normal warnings, 0 warnings were flagged to be ignored"...

Patch looks good to me...

Committed - thanks!

By the way, for clarity:

This fix will be included in the 7.x-1.x-dev release as of midday today, and in the next point release (currently scheduled for early August).