The boincuser_load() function was expecting a drupal uid instead of a boinc user id. This has been changed to accept either, but now uses boinc id as the more logical default.
(DBOINC-133)
The function to generate default site content (i.e. Help page) is not available yet when the boinccore module is first being enabled. Explicitly include the admin.inc file to ensure it is in place first.
(DBOINC-133)
A change to the friend page templates was too broad and broke the friend block on the account page. Renamed the template file to be more specific and only apply to friend pages.
(DBOINCP-96)
Some issues were resolved with friend links:
* Use a more proper approach for determining link context by checking the flag status for a given user-friend relationship
* Set the friend link on the user profile page to be "Approve friend request" if appropriate; this prevents a user from adding someone when there is already an open approval for that person (which did not fail smoothly)
* Added templates for fields on friend pages to format links properly
(DBOINCP-96)
* Set up general permissions for the team_forum node type
* Gave "manage boincteam forum" permission to administators
* Added forum sidebar to team page for team members, users with permission to manage team forums, or in general for teams with public forums
(DBOINCP-80)
The friend request process needed some polish:
* Determined contexts for different friend forms to that action buttons are appropriate (i.e. "Send request" or "Remove friend instead of a generic label)
* Added a "goto/friend-requests" URL for use in notification emails to handle login sessions automatically
* Updated friend email templates to use proper URLs, the correct user name, and less repetative text
(DBOINCP-96)
* Added descriptions to make it less confusing when "0 means no limit"
* Fixed bug in preset admin form that could break the submitter's preferences rather than update the preset
(DBOINCP-99)
The Captcha module has a bug that causes image uploads to a user profile to result in captcha session re-use attack error messages. A patch has been released, but the module was never updated, so it must be overridden locally.
(DBOINCP-98)
* Removed team_forum content from search index
* Fixed site search title
* Hide facets for team search
* Added search form to team pages
* Fixed links on team search results
(DBOINCP-59)
The confirmation form when adding a friend had unstyled buttons:
* Added proper formatting to form control buttons
* Changed label on Send button to "Send request"
* Set link on Cancel button to go to the target user's profile
(DBOINCP-95)
When quoting another comment, an inconsistency in how form buttons are defined causes the buttons to render below the quoted post rather than below the form. This has been updated to be consistent, but further caused another layout bug that would somehow move the form above the preview of the post. This has been worked around also.
(DBOINCP-93)
The "Create forum topic" form had unstyled buttons:
* Added proper formatting to form control buttons
* Changed label on Save button to Post topic
* Added Cancel button
(DBOINCP-94)
Updated datestamps on locally-patched contrib modules. When an update is available for one of these (i.e. it has a newer timestamp), it will have to be reviewed. If the local version is still needed, the timestamp of the local module can be updated again.
Further added a "-dev" flag to the revision number to all contrib modules that are patched locally. This is required to prevent Drupal from assuming that the recommended release with the same major and minor version numbers should be installed. The "-dev" flag forces the update process to look at the datestamp of the module as well as the version information and uses that to determine whether a recommended release is actually newer.
The intended goal couldn't be achieved as the Drupal update mechanism always judged our custom versions to be older than the stock ones of the same major.minor version.
This reverts commit 82779e834f.
This reverts commit 40e88c2a88.
Added a "-boinc" suffix to all contrib modules that are patched locally. This allows identification of which modules are patched and also what the original version of the module was prior to patching.
The BBcode module has an unfixed bug that allows improper usage of [quote] tags to break the page output. This has been patched locally until the problem is solved by a new release.
(DBOINCP-92)
Removed the conversion to ghours, since it is not used elsewhere on the site. Also, set format to 2 decimal places there and on the team overview page.
(DBOINCP-59)
Post and topic counts were not always adding up. Updated queries to account for topic starting posts, empty topics, and topics and posts already imported.
(DBOINCP-59)
The Forum Access module was incorrectly defining the rid field as INT(11) rather than INT(10) unsigned. Because INT(11) isn't actually any bigger than INT(10), dropping the unsigned declaration causes half of the available rid space to be lost.
Until the module is fixed by the maintainer, it must be overridden locally. A database update has been added to the install file to redeclare the rid field as INT(10) unsigned.
(DBOINCP-91)
Updated topic import messages to include better statistics on which topics were imported or skipped and why (i.e. already imported, empty, or error)
(DBOINCP-59)
Fixed hook to add entry to mapping table on team_forum node insert. The UID must be from the node, not the current user, in case the node is being created by a third party (i.e. during import)
(DBOINCP-59)
Added boincteam_members_email_list() callback to output an email list with content-type text/plain; disabled corresponding variant in page manager.
(DBOINCP-80)
A duplicate role was showing up for the special "Forum Moderator" role that the forum access module creates. The code that renames this has been improved to ensure that the role is set up and named properly when the discussion forums feature is enabled.
(DBOINCP-80)
The call to node_save() while importing team topics was not including the tfid, so it was always being set to zero. Added this to the node_save call.
(DBOINCP-59)
The forum menu export is no longer needed and has caused the discussion_forums feature to be stuck in an overridden state. Just delete the menu export file for this feature.
(DBOINCP-59)
Report the actual number of teams imported, not a count of records in the boincteam table
Removed duplicate insert into boincteam_forum_node (this is handled more properly by boincteam_forum_node_insert())
(DBOINCP-59)
The incorrect variable was being saved to establish the Forum vocabulary; renamed to proper variable.
Also, fix the cleanup process to unset team forum variables.
Tristan Olive