I just installed the project and project release modules. Then I try to create a project, all works fine. I try to create a release, all works fine.

Let problems start!

I tryed to edit a project and select the subtab "Releases" and I get this error :

Notice: Trying to get property of non-object in project_release_project_edit_form() (line 20 of /path/to/drupal/sites/default/modules/project/release/includes/project_edit_releases.inc).

I try to add a new release to this project (its version format is !api#major%minor%patch#extra) the version I write is: "test-1.0.0-dev"

Then I get two errors:

Notice: Trying to get property of non-object in project_release_get_release_api_tid() (line 578 of /path/to/drupal/sites/default/modules/project/release/project_release.module).

Notice: Undefined property: stdClass::$taxonomy_ in project_release_get_release_api_tid() (line 578 of /path/to/drupal/sites/default/modules/project/release/project_release.module).

Comments

dww’s picture

Issue tags: +project, +drupal.org D7

Thanks for the report. These seem to have slipped by when #1551384: Port project_release to D7 was marked fixed. Hopefully relatively easy fixes. Either myself or drumm will get to this soon.

Cheers,
-Derek

drumm’s picture

This is likely related to #1822392: Project Release 7.x has Drupal 6 dependency: PHP Fatal: EntityFieldQueryException: Unknown field: taxonomy_version. I'm not going to say this is a duplicate quite yet, I think we need an issue to ensure project release works without an API vocabulary, which I think most people will not need. This might be that issue.

The API vocabulary and !api part of the version number is used on Drupal.org for 6.x/7.x/etc as a prefix for module/theme/etc project versions. Flohw - do you even want this, or do you want more simple version numbers like X.Y or X.Y.Z? For simple versions, remove !api from the version format, and we should make that the default in project release. For using the API version component, maybe #1822392: Project Release 7.x has Drupal 6 dependency: PHP Fatal: EntityFieldQueryException: Unknown field: taxonomy_version is the issue to tackle.

This shouldn't be a blocker for Drupal.org D7, we have the API junk configured to work for us. It certainly should be nicer for Project 7.x-2.0.

dww’s picture

Ahh, good points. Thanks drumm. Agreed all around.

Flohw’s picture

Thanks for answer!

I want a simple version number like X.Y.Z and be able to set multiple version number like in drupal : -.

If you can also be more clear on your field names : what are "Version extra delta" and "Update status" fields for?

I may create a feature request to auto fill "Project" when create a release. I used Rules module to auto fill it but it is not the easier way to do that. And I think this field have to not be edited.

One more thing: we have build our system based on Drupal default behavior by create content types, creating rules etc... the development version have not solved our problems and nothing looks changed. The "Project release configuration" link does not exists as it is mentioned on the documentation pages.

Thanks for hearing me!

dww’s picture

While working on #2145667: project_release_node_presave() should only parse the version string if the version elements are not already set on a local dev site (on a train), I ran into some of these bugs and just pushed some commits to address some of them. Still not completely resolved by any means, but getting closer:

http://drupalcode.org/project/project.git/commit/e6e50cf
http://drupalcode.org/project/project.git/commit/4af48e3
http://drupalcode.org/project/project.git/commit/23055b3