Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
Although still a work-in-progress, this release includes the code that's been running on Drupal.org for quite some time. Since we're about to do a weekend of sprinting and hopefully getting closer to an official 7.x-2.0 release, I wanted to cut a new set of releases as an initial starting point. Changes since 7.x-2.0-unstable1:
Apologies to all the users of this module -- it's been far too long since we've done an official release! The drupal.org redesign, Git migration, and a number of other significant changes have all happened since alpha4. We're gearing up to do another round of fixes and improvements, so before we start merging all of that into the mainline branch we wanted to ship this release (which has been running quite happily on drupal.org for months).
First official release compatible with Drupal 6 core (note that the alpha1 and alpha2 releases were tagged months ago but never officially released -- they were used internally for initial deployment on drupal.org). There are still a number of known issues before we're ready to release an official 6.x-1.0 release. There will almost certainly be more schema and API changes. However, in the near future, the HEAD branch will be a bit unstable, so sites that are already using the 6.x-1.x-dev release are encouraged to upgrade to this official release and stay there, instead of continuing to use 6.x-1.x-dev.
#76725 by aclight, dww: Refactored project issue module to use Views.
Detailed changes
(Note, this list is currently incomplete. See the CVS messages between commit id #167784 and #166021 for other changes during the initial Drupal 6 porting).
#361649 by netaustin, hunmonk: does all the following:
This release fixes two security vulnerabilities described in DRUPAL-SA-CONTRIB-2009-002. Sites are urged to upgrade immediately. Other changes since version 5.x-2.2:
Bug fixes
#209507 by aclight: Fixed critical bug introduced with #188198 where the original poster of an issue wouldn't get notification emails about that issue unless they also commented on it.
#283332 by hunmonk: {project_issues} table not being created when module is enabled. Removed erroneous default value from original_issue_data text column. No database update is necessary because MySQL simply tosses the default value declaration if it does install the table.
#272618 by aclight: Fixed bug where 'Create Issue' menu item was visible even when 'create project issues' permission is disabled.
#11211 by Gabor Hojtsy: proper use of drupal_add_feed().
#293882 by agentrickard and scor: Fixed broken project lookup in mailhandler code.
#275323 by aclight and hunmonk: Prevent project_issue_generate_issue_comments() from causing fatal errors in rare cases.
Initial port to Drupal 6 API. Views is now required to run project*. This code is mostly working, but there's no guarantee that the upgrade path is stabilized. There are still a number of known bugs. Production sites should not upgrade until there's an official release.
This is the first official release of the 5.x-2.* series. The major new feature here is that issue followups now use core comments, instead of the previous special-case pseudo comments. This means the project_issue now depends on comment.module, upload.module (for file attachments to the initial issue post), and the comment_upload.module (for file attachments to followup comments).
This release requires Drupal 5.2 or greater.
Users of the 5.x-2.x-dev release should upgrade to this version immediately, since it fixes some critical security flaws:
NOTE: Unless critical bugs are uncovered, this will be the last official release for the 4.7.x-1.* series. All users are strongly encouraged to upgrade to at least 4.7.x-2.*, or better yet, 5.x-1.*, as soon as feasible. Support for this release series is basically over.
#180568 (SA-2007-021) by hunmonk: Fix XSS holes in project subscription forms. #177312 by hunmonk: add project links, fix breakage on issue subscription form. #168650 by pwolanin, hunmonk: fix improper use of %s
#180568 (SA-2007-021) by hunmonk: Fix XSS holes in project subscription forms. #177312 by hunmonk: add project links, fix breakage on issue subscription form. #168650 by pwolanin, hunmonk: fix improper use of %s
#180568 (SA-2007-021) by hunmonk: Fix XSS holes in project subscription forms. #177312 by hunmonk: add project links, fix breakage on issue subscription form. #168650 by pwolanin, hunmonk: fix improper use of %s #172327 by hunmonk: INSTALL.txt outdated
This release addresses an access bypass security issue, DRUPAL-SA-2007-020. Sites that try to restrict access to issues based on the 'access project issues' or 'access own project issues' permissions should upgrade immediately.
This release addresses an access bypass security issue, DRUPAL-SA-2007-020. Sites that try to restrict access to issues based on the 'access project issues' or 'access own project issues' permissions should upgrade immediately.
This release addresses an access bypass security issue, DRUPAL-SA-2007-020. Sites that try to restrict access to issues based on the 'access project issues' or 'access own project issues' permissions should upgrade immediately.
This release fixes a security vulnerability, all users of project_issue 5.x-0.1-beta or any 5.x-0.x-dev snapshot from before 2007-03-08 are urged to upgrade. For more details, see DRUPAL-SA-2007-012.
NOTE: The upgrade path from 4.7.x-1.* version of the Project issue tracking 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.
This release fixes a security vulnerability, all users of project_issue 4.7.x-2.2 and earlier are urged to upgrade. For more details, see DRUPAL-SA-2007-012.
Besides the security fix, two 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_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:
Reformatting menu item array declarations to be more readable.
#105227: validation failing when project in URL doesn't match selected value in the form. This was due to bad logic in the form builder.
#105704: foreach() warning if you do a completely empty advanced search.
#105521: rip out bizzare "default version" behavior
#105229: fix CSS to handle new behavior of FAPI #prefix/#suffix (#100787)
Don't reuse the class="options" div, since that makes the "Publishing options" fieldset become inline, too. now, we use an "inline-options" div when we want everything floated and inline.
#106783: "inline-table" messes up fieldsets on Opera. It's ignored by Firefox. Safari gets it right, but that's not enough reason to keep it.
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 issue tracking 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.
#61453: fixing broken "Issues e-mail address" setting. The UI was mostly hidden unless you were a project administrator, and the code didn't match the descriptions. :( Now, if none of the filters are selected, you really do get the email (as the description has always said).
#85788 by fgm: project comment id (project_cid) sequence needs DB prefix.
#82619: blobs from comment bodies need to be decoded (for PostgreSQL).
New features:
#94000: adding $Name$ tags for automated version identification
#96971: make better use of tabs and subtabs on project nodes. Patch from comment #3
by dww, to split up the project edit tab into subtabs for project, issues and releases.
This release fixes a security vulnerability, all users of project_issue (4.7.x-1.0 or 4.7.0 from before the new release system) are urged to upgrade. For more details, see DRUPAL-SA-2006-031.
Besides the security fix, the only other changes in this release are bug fixes since project-issue-4.7.x-1.0:
The initial stable release compatible with Drupal core 4.7.x. This is the code from before the new release system. It is incompatible with the 4.7.x-2.x series of the project.module, so be sure you use the 4.7.x-1.x series of both modules.
The initial release of the 4.7.x-2.x series which implements the new release system. This series requires a version of the project.module that is also version 4.7.x-2.x, since the project API changed for major revision 2.