• last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LDEV-1324 Allow group admins/managers to edit group details, but not group permissions; group's status editable by admin/manager when 'canChangeStatusOfCourse' is enabled; refactored organisation related jsps into their own directory.

  1. … 8 more files in changeset.
lams_central shouldn't have dependency in lams_learning - moving method from LearnerService to LessonService in lams_common, as a result also moving Index*Beans to lams_common

    • -0
    • +126
    ./src/java/org/lamsfoundation/lams/index/IndexLessonBean.java
    • -0
    • +86
    ./src/java/org/lamsfoundation/lams/index/IndexLinkBean.java
    • -0
    • +167
    ./src/java/org/lamsfoundation/lams/index/IndexOrgBean.java
  1. … 9 more files in changeset.
Refactor jdbc call in DisplayGroupAction (gets list of lessons for index page) to use hibernate named query via LessonDAO and ICoreLearnerService.

  1. … 3 more files in changeset.
Update LessonDAO.getActiveLessonsForLearner's database query so that lessons where user is in the staff group and not the learner group are not returned. Currently only used in 'all my lessons' page - LDEV-1483

LDEV-1284 alter the register (web) service to accept course ids and names as inputs. Also altered the integration service to handle course names, and boolean flags for whether users are staff, and whether to use the extServer's prefix in the org/user name. Tested with Moodle integration and sign up script.

  1. … 3 more files in changeset.
Missed some of the updates to the system tool table for branching and optional sequences.

update config settings in 2.0.6 update script.

Preparing for 2.1 Beta Release - Updated dictionary date.

    • -1
    • +1
    ./db/sql/insert_lams_unix_config_data.sql
    • -1
    • +1
    ./db/sql/insert_lams_windows_config_data.sql
Preparing for 2.1 Beta Release

    • -5
    • +5
    ./db/sql/insert_lams_unix_config_data.sql
    • -5
    • +5
    ./db/sql/insert_lams_windows_config_data.sql
  1. … 1 more file in changeset.
Updated version to 2.0.6

    • -5
    • +5
    ./db/sql/insert_lams_unix_config_data.sql
    • -5
    • +5
    ./db/sql/insert_lams_windows_config_data.sql
Refactor admin breadcrumb so that title of a page is separate from the breadcrumb; put more info in orgs and user lists.

  1. … 31 more files in changeset.
LDEV-1284 add check for when organisation is missing in integration entry; don't add new users to the integration org since there no longer is one. Backported from HEAD.

  1. … 1 more file in changeset.
LDEV-1284 add check for when organisation is missing in integration entry; don't add new users to the integration org since there no longer is one.

  1. … 1 more file in changeset.
LDEV-1284 integration organisation no longer mandatory; marking file as ascii, not binary

    • -53
    • +53
    ./db/sql/create_integration_tables.sql
LDEV-1284 integration organisation no longer mandatory; marking file as ascii, not binary

    • -53
    • +53
    ./db/sql/create_integration_tables.sql
merge changes from HEAD to ldap2_0_4 branch for LDEV-1284, making integration organsiations not mandatory (requires alter_206_integration.sql update script to be run)

  1. … 2 more files in changeset.
file alter_206_integration.sql was initially added on branch ldap2_0_4.

LDEV-1284 integration organisation no longer mandatory; orgid column in lams_ext_server_org_map can be null now.

  1. … 2 more files in changeset.
Merge LDEV-1284 changes to ldap2_0_4 branch

Changes to merge 2.0.5 with ldap2_0_4 branch to be used for macquarie uni and the webCt-LAMS integration

  1. … 8 more files in changeset.
Updating Dutch and Chinese

    • -0
    • +52
    ./conf/language/lams/ApplicationResources_nl_BE.properties
LDEV-1376: Couple of small tweaks needed on the back end - the validation wanted start to be not null so that was removed (the logic in the runtime test was fine, it was just the validation) and the greater than was sending back a dummy 9999, which is now null.

LDEV-1218: Adding the batch size for the learner progress screen to the monitoring call.

    • -0
    • +3
    ./db/sql/insert_lams_unix_config_data.sql
    • -0
    • +3
    ./db/sql/insert_lams_windows_config_data.sql
    • -0
    • +3
    ./db/sql/insert_rams_unix_config_data.sql
    • -0
    • +3
    ./db/sql/insert_rams_windows_config_data.sql
  1. … 1 more file in changeset.
LDEV-750: Adding insert sequence into sequence functionality. Basic functionality done - still yet to do the Flash side and some security checking.

  1. … 21 more files in changeset.
LDEV-1328 fixed group managers and group admins should be able to edit subgroup details

  1. … 3 more files in changeset.
LDEV-1323 overhaul add/remove user screen which didn't scale well for sysadmins - users added via search field now, with the option to click a link to retrieve all potential users

  1. … 7 more files in changeset.
LDEV-1301: Changing some of the I18N labels for the configuration screen to reuse existing labels. Removed the LearnerProgressBatchSize as we aren't using it for the Learner Progress screen after all.

    • -22
    • +19
    ./db/sql/insert_lams_unix_config_data.sql
    • -22
    • +19
    ./db/sql/insert_lams_windows_config_data.sql
    • -23
    • +20
    ./db/sql/insert_rams_unix_config_data.sql
    • -22
    • +19
    ./db/sql/insert_rams_windows_config_data.sql
Updating English, Norwegian and Polish

  1. … 4 more files in changeset.
LDEV-1179: Export portfolio now displays a different msg for run offline activities. The screen comes from the learning war, and is called from the code on AbstractExportPortfolioServlet. Tools don't have to do anything, but they can override a new method in the servlet and supply the name of the activity (as per the tool's authoring screen) or do their own screen. Our tools will just display the name of the activity.

  1. … 14 more files in changeset.
LDEV-1285: Adding a new Activity type "Options With Sequences" so the Flash will know whether to expect sequences or not. The type is stored in the database otherwise we won't know which type it will be if the user saves the Optional without any child activities. The back end treats all Optional activities the same.