lams-github

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LDEV-1144: Two bugs: * The submit is trying to call a javascript function that does not exist. I can't find any code that suggests it ever existed! * The pages are trying to load up a css file that doesn't exist. At least in this case, the file did exist in the past but it was removed.

Removed the onsubmit call and the css reference.

    • -1
    • +0
    /lams_tool_forum/web/common/header.jsp
    • -1
    • +1
    /lams_tool_forum/web/jsps/learning/edit.jsp
    • -1
    • +1
    /lams_tool_forum/web/jsps/learning/reply.jsp
Changes made to all tools, so they should be made in the example tool

Changes to build, so the tool deployer can put the tool_version in the deploy.xml when the tool is build.

Now, the tool_version in tool_insert.sql must be replaced by @tool_version@, and the actual tool version goes in the buld.properties under tool.version

    • -1
    • +1
    /lams_tool_example/db/sql/tool_insert.sql
    • -1
    • +1
    /lams_tool_lamc/db/sql/tool_insert.sql
    • -1
    • +1
    /lams_tool_laqa/db/sql/tool_insert.sql
Changes made to all tools, so they should be made in the example tool

Changes to build, so the tool deployer can put the tool_version in the deploy.xml when the tool is build.

Now, the tool_version in tool_insert.sql must be replaced by @tool_version@, and the actual tool version goes in the buld.properties under tool.version

Changes to build, so the tool deployer can put the tool_version in the deploy.xml when the tool is build.

Now, the tool_version in tool_insert.sql must be replaced by @tool_version@, and the actual tool version goes in the buld.properties under tool.version

    • -1
    • +1
    /lams_tool_chat/db/sql/tool_insert.sql
Changes to build, so the tool deployer can put the tool_version in the deploy.xml when the tool is build.

Now, the tool_version in tool_insert.sql must be replaced by @tool_version@, and the actual tool version goes in the buld.properties under tool.version

    • -1
    • +1
    /lams_tool_forum/db/sql/tool_insert.sql
lams-tool_deploy generates a tool_version entry for a tool's deploy.xml

missing message key (also found in lams_admin's resources)

Translation key was wrong for the export button.

LDEV-1097: Changed the learner progress screen to be a read only version of the learner's progressive results screen.

LDEV-1142: Change the answer text field to text, so that it can take longer text.

    • -133
    • +132
    /lams_tool_survey/db/model/survey.clay
    • -1
    • +1
    /lams_tool_survey/db/sql/create_lams_tool_survey.sql
    • -1
    • +1
    /lams_tool_survey/db/sql/tool_insert.sql
Small changes to date fields and, supported locales for the 09/02/07 language pack

Updating Welsh, Spanish, English, Polish

Updating Welsh, Spanish

    • -24
    • +24
    /lams_learning/conf/language/ApplicationResources_cy_GB.properties
    • -9
    • +9
    /lams_tool_larsrc/conf/language/ApplicationResources_cy_GB.properties
    • -12
    • +12
    /lams_tool_larsrc/conf/language/ApplicationResources_es_ES.properties
    • -13
    • +13
    /lams_tool_scribe/conf/language/ApplicationResources_cy_GB.properties
    • -6
    • +6
    /lams_tool_scribe/conf/language/ApplicationResources_es_ES.properties
    • -7
    • +7
    /lams_tool_survey/conf/language/ApplicationResources_cy_GB.properties
    • -2
    • +2
    /lams_tool_survey/conf/language/ApplicationResources_es_ES.properties
Updating Welsh

    • -23
    • +23
    /lams_central/conf/language/ApplicationResources_cy_GB.properties
    • -6
    • +6
    /lams_monitoring/conf/language/ApplicationResources_cy_GB.properties
    • -15
    • +15
    /lams_tool_forum/conf/language/ApplicationResources_cy_GB.properties
    • -34
    • +34
    /lams_tool_lamc/conf/language/ApplicationResources_cy_GB.properties
Updating Welsh, Spanish, Polish

Updating Welsh, Polish, Swedish

(This was changed in all the other tools, so should also be changed for the example tool) Changing build.xml "deploy-tool" target to separate the compilation and deploy processess. This will be used later for debian packaging

Changing build.xml "deploy-tool" target to separate the compilation and deploy processess. This will be used later for debian packaging

Improving the permission tests on the main monitoring calls.

    • binary
    /lams_build/lib/lams/lams-learning.jar
    • binary
    /lams_build/lib/lams/lams-monitoring.jar
LDEV-1097: Fixing up the behaviour of the learner progress screen, and other bugs found while testing the learner progress changes.

    • -46
    • +50
    /lams_tool_laqa/web/export/exportportfolio.jsp
LDEV-1141 sort organisations alphabetically

use change_password field in user table to show user 'password change' screen instead of index page when they login

Add a new column to user to indicate that the user needs to change their password.

    • -0
    • +1
    /lams_common/db/sql/create_lams_11_tables.sql
Change the grouping screen in learner progress to not have a finish button - required a change to the url for learner progress.

Add a new column to user to indicate that the user needs to change their password.

    • -0
    • +16
    /lams_common/db/sql/updatescripts/alter_201_system_tool_user.sql
Change the grouping screen in learner progress to not have a finish button - required a change to the url for learner progress

    • -1
    • +1
    /lams_common/db/sql/insert_types_data.sql
LDEV-1097: Remove the finish button from the learner progress view of the grouping screen, plus updated some out of date method calls relating to force complete.

LDEV-1097: Learner progress screen didn't cope when the learner had been force completed.

LDEV-1097: Learner progress screen didn't cope when the learner had been force completed. Also, was showing buttons for finish when in monitoring mode. Hopefully the buttons are right now.

change SpreadsheetService to ImportService; adjust jsp display

    • -4
    • +4
    /lams_admin/web/import/importexcel.jsp
    • -0
    • +7
    /lams_admin/web/import/importv1result.jsp
change imported passwords to sha1(login) instead of v1's md5 password; fix null bug