|
|
|
 |
- last updated a few seconds ago
Tuesday 13 Feb 2007
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
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
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.
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 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
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
lams-tool_deploy generates a tool_version entry for a tool's deploy.xml
Monday 12 Feb 2007
missing message key (also found in lams_admin's resources)
Friday 09 Feb 2007
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.
Small changes to date fields and, supported locales for the 09/02/07 language pack
Updating Welsh, Spanish, English, Polish
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.
Thursday 08 Feb 2007
LDEV-1097: Fixing up the behaviour of the learner progress screen, and other bugs found while testing the learner progress changes.
Wednesday 07 Feb 2007
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.
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.
Change the grouping screen in learner progress to not have a finish button - required a change to the url for learner progress
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.
|
