Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
This release fixes a security vulnerability, all users of project_issue 4.7.x-1.2 and earlier are urged to upgrade. For more details, see DRUPAL-SA-2007-012.
Besides the security fix, 2 critical PostgreSQL bugs are fixed in this version:
#109851 by Rok Zlender: SQL error on "My issues" page with PostgreSQL
#82696: PostgreSQL sequence missing for {project}_cid.
This release fixes a security vulnerability, all users of project-4.7.x-1.x (or 4.7.0 from before the new release system) are urged to upgrade. For more details, see DRUPAL-SA-2007-004.
Besides the security fix, the only other changes in this release are bug fixes since project-4.7.x-1.1:
#100901: there was 1 more call to project_project_set_location() which i missed when backporting this fix to DRUPAL-4-7. :( This causes undefined function errors when you try to add a release in 4.7.x-1.*.
This release fixes a security vulnerability, all users of project 5.x-0.x-dev from before 2007-01-23 are urged to upgrade. For more details, see DRUPAL-SA-2007-004.
NOTE: The upgrade path from 4.7.x-1.* version of the Project module is still very confusing, undocumented, and error prone. Sites that use the project module are strongly recommended to not upgrade to Drupal core 5.x until the official 5.x-1.0 release of this module is available.
Besides the security fix, other changes in this release include: