Feel connected, no matter where you are.

Member Login



Endre Release Date: 25-August PDF Print E-mail
Written by Administrator   
Friday, 21 August 2009 07:23

Yes, we know we're late and we apologize for this.   Next Tuesday we will be releasing Dingo 1.5.8 [Endre] which incorporates about 45 changes.   From a functional perspective, the biggest difference is in what we call "item visibility."

In all previous versions of Dingo, the only way a visitor could touch Dingo was via the Visitor Ticket.  A project that had been deemed public could have anonymous guests submit tickets into the Dingo item table.   This part remains unchanged, but we've taken that a step further.   Now within the Project edit screen you will notice two dropdowns that control item creation and visibility.


Item Control in Projects


This means if you set both to Everybody, that project, and all tasks within can be accessed by all users, even the anonymous guests.  While Dingo isn't a forum product, that's a good example how this might be used.  If you wanted to allow anyone to view tasks and make comments, this would be a way to do it.

When Creation and Visibility are set to Project Members, it means only those who have been assigned to the project will have those tasks appear in their dashboard.

Our intention with this was to improve client access as we're finding a niche using Dingo to service multiple clients, while keeping them all separate.

 

 

A summary of changes in Endre

Functional
Project visibilty overhaul
Date due is now sortable in task list   
Project priority is now included in project list
Non-managers now see all links in dashboard (but are disabled)
Length of subject field increased to 90 (was 50)
When a new item is added, it will now appear in the Changed Today query
Hours column added to linked items (for controller tasks)
Clients added to project dropdown  (if you had two projects with same name you didn't know which was which)
Added date/time an item was submitted

Added item# in history log  (previous versions didn't always have the item#)
eg.,
Added new item charge #182 (Test)
Added new comment #182(History comment test)
Added to resource #182(Csenteri Zoltan)
Updated item #182(History testing)

Comment time changed to match user's local
Previously, an item could be closed/suspened/terminated just by the owner. Now users have access to all status types

Bugs Fixed
Reset filter in Files screen
Profile view can now be called from menu
Export time corrected
Mail sending procedure updated when user is assigned to a project
If you make a new item and assign a resource, the notifcation was not correct

Cosmetic
CAPTCHA label changed
Moved label in Files screen
Item charge screen:
1.  Align the top fields so they are all left justified
2.  Default the editor to non-HTML
3.  Reduce the number of rows in the text
change item to items in user profile screen
updated the language file with the PROJECT_HISTORY_DELETE=Deleted project record

Notes
Joomfish integration

This problem is related to the integration of joomfish and dingo, and probably due to joomfish project decisions.
This problem is solved using MYSQLi.   Enable mysqli extension on php ini file. Reset apache. Change joomla database configuration to from mysq to mysqli … And all is solved.   I believe the developers decided for the use of mysqli_connect instead of mysql_connect etc, that generated the error messages

Last Updated on Tuesday, 25 August 2009 09:09