• last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
support multiple base DNs; support paged search results from ldap; remove bulk update method from spring's transactions; improve bulk update results report

    • -1
    • +2
    /lams_common/db/sql/insert_lams_unix_config_data.sql
    • -1
    • +2
    /lams_common/db/sql/insert_lams_windows_config_data.sql
LDEV-1249: Null ptr exception was being thrown when trying to generate a chart and there were no votes. Now if no votes exist, no charts are created.

added 'remove' option for when lesson is in the STARTED state in monitor

    • binary
    /lams_monitoring/web/lams_monitoring.swf
    • binary
    /lams_monitoring/web/lams_monitoring_library.swf
endGate linkage, alertDialog added + Mitches branching changes

Release notes addes to lams_bb_integration project

    • -0
    • +23
    /lams_bb_integration/RELEASE_NOTES.TXT
All bugs fixes for the 2.0.2 release have been done, awaiting further testing

merge change from ldap2_0_4 branch back to HEAD

fix error when hibernate didn't initialise user.userOrgs for newly created user during bulk update

merge changes from ldap2_0_4 branch back to HEAD

move user disabled check after authentication, to give non-db methods a chance to update disabled flag.

fix bug when ldap user has no disabled attribute and LDAPDisabledAttr is prefixed with '!'.

LDEV-1284 change integration classes to courses (also creates workspace/folders)

integrationService.getExtCourseClassMap creates the ext_course_class_map, and the matching lams org, for the 3rd party course; since the org is now a course (with workspace folder) instead of class, it's nice to have the folder appear when 3rd party users browse list of learning designs.

merge changes from ldap2_0_4 branch back to HEAD

    • -0
    • +1
    /lams_common/db/sql/insert_lams_unix_config_data.sql
    • -0
    • +1
    /lams_common/db/sql/insert_lams_windows_config_data.sql
add support for user enabled/disabled flag in ldap

    • -0
    • +1
    /lams_common/db/sql/insert_lams_unix_config_data.sql
    • -0
    • +1
    /lams_common/db/sql/insert_lams_windows_config_data.sql
LDEV-1134: Fixed the View Branches screen for tool output based branching - I can't list the users based on groups as they aren't in groups (and I can't put them in groups as the groups have to be linked to the condition and if the user goes to the default branch there is no condition). So for tool output based branching I have to find the users via their progress records.

LDEV-1194: Fixed custom dialog problems for long messages

    • binary
    /lams_central/web/lams_authoring.swf
    • binary
    /lams_central/web/lams_authoring_library.swf
    • binary
    /lams_monitoring/web/lams_monitoring.swf
    • binary
    /lams_monitoring/web/lams_monitoring_library.swf
LDEV-1134: Fixing up condition key - copy and paste error earlier.

LDEV-1134: Fixing up condition key - copy and paste error earlier.

Updating Chinese(China) and Polish

LDEV-1134: Fixing up class cast errors

LDEV-1134: Complete implementation of conditions in MCQ and Forum.

merge LangUtil into LanguageUtil

merge LangUtil into LanguageUtil

merge changes from ldap2_0_4 branch back to HEAD

    • -10
    • +22
    /lams_central/web/editprofile.jsp
    • -1
    • +10
    /lams_common/db/sql/insert_lams_unix_config_data.sql
    • -1
    • +10
    /lams_common/db/sql/insert_lams_windows_config_data.sql
add default names for some ldap attributes, add LDAPLocaleAttr

    • -10
    • +22
    /lams_central/web/editprofile.jsp
    • -5
    • +6
    /lams_common/db/sql/insert_lams_unix_config_data.sql
    • -5
    • +6
    /lams_common/db/sql/insert_lams_windows_config_data.sql
file LangUtil.java was initially added on branch ldap2_0_4.

refactor locale related code into new LangUtil class, modify existing calls to use LangUtil methods

Added alot of regex management to the rename tool code, hopefully this will prevent collisions beteen the user's choice of nameing for the rename tool

Added alot of regex management to the rename tool code, hopefully this will prevent collisions beteen the user's choice of nameing for the rename tool