What's New - 2.1.2
From DotProjectWiki
FIRST DRAFT OF RELEASE NOTES - SUBJECT TO CHANGE AT A MOMENT'S NOTICE UNTIL RELEASE IS ACTUALLY ANNOUNCED.
IN OTHER WORDS - DON'T BELIEVE A WORD OF THIS UNTIL YOU SEE THE RELEASE ANNOUNCEMENT.
Release: 2.1.2
Release Date: late July 2008
A variety of small fixes and improvements have been incorporated in this release, which is part of a general clean-up of some of the worst of the poor code in the 2.x branch discovered during the 2.1 testing and release process.
For a full listing of the resolved issue reports see Closed Issues and Feature Requests - 2.1.2
Over and above the error reports, we have also changed the following:
Contents |
1 Default User Preferences
As of 2.1.2 user preferences only override default user preferences if you specifically set them to a non-default value. In all other cases if you update the user defaults, any user that has not set their own preferences to non-default values will be given the new default. See http://docs.dotproject.net/index.php/Default_User_Preferences
2 Files Module
- Resolved folders so that the honour the file module permissions as well as company / project and task permissions for the current user.
- Added ability to set permissions against folders down to individual folder level.
2.1 Quick Run-Down of Indented File-Folder Permission Effects
2.1.1 Module Level
Access: Controls ability to view "Folder Explorer" tab in files module View: Controls ability to view all Folders (and files in them) except for "Root" folder (Root is better thought of as "no folder association") Add: Controls ability to add any folders Edit: Controls ability to edit any folders (except for "Root" folder, non-editable) Delete: Controls ability to delete any folders (except for "Root" folder, non-deletable)
2.1.2 Item Level
Access: No effect in code. View: Controls ability to view a specific Folders (and files/folders in them), cannot set permissions on Root "folder".
- (Note: At present users can directly view folders under the indicated folder (even though they are not displayed in the view of the Root folder). Additional modifications would need to be made to check for accessibility of subfolders based on parent folder permissions)*
Add: Controls ability to add folders within the given folder Edit: Controls ability to edit the given folder's properties Delete: Controls ability to delete the given folder.
3 Custom Fields
Added custom field type = file (see Custom Field Editor for more details).
4 General Performance Improvements
- Modified a number of poorly structured SQL queries to improve general performance.
5 Permissions
Item level permissions are now included at the role level (and not just at the user level) as a result of cleaning up duplicated functions.
A new permission for "User Table" was incorporated in 2.1.1 that may require you to adjust your roles. The User Table permission allows you to control which users can assign human resources. Please note - this currently means that WITHOUT the permission a user cannot access human resources. With the permission a user can access ALL human resources - at this stage this option DOES NOT PROVIDE ITEM LEVEL control - ie you cannot stipulate which resources a user can access. This limitation is due to the way that the work was specified by the sponsor and will be considered for further advancement in 3.x
6 Today View
Added a project tab to list the current user's projects.
7 System Admin - Manage Permissions Cache / Performance
We have added options for managing Permissions Cache to System Admin > System Configuration, rather than have to edit files as suggested frequently on the forums. The options available are:
Expire Permissions Cache (click to turn on / save / click to turn off again) Setting this will force the expiry of the permissions cache, if you use Permissions Caching you should only set this to clear an old cache to get around problems, and reset it afterwards
Enable Permissions Cache - click to turn on / can be left on. Turn this on to improve performance in task listings, make sure you also set the permissions cache directory
Permissions Cache Directory - defaults to /tmp Set this to a directory on your system that the web server can write to, this holds the cache for the permissions system
Permissions Cache Timeout - Number of seconds to hold onto cached permissions information.
8 Security Updates
General information only to protect those who have not updated yet - we have resolved a potential privileges exploit where somebody could have obtained admin privileges if they handcrafted a form. Ongoing prevention of XSS exploits - no major issues reported.
