Adapt Learning Community: Version 0.1.2 of the authoring tool has been released

Hi everybody,

I'm happy to announce that we've just released version 0.1.2 of the authoring tool. Thanks to all the community for the feedback we have received and the developers who have made this happen.

The primary focus of this release has been support for version 2.x of the Adapt Framework, but there are numerous minor enhancements and bug fixes.

The full list of issues resolved can be viewed here, but these are the highlights:

Added

Support for _isOptional (Adapt Framework v2.x)
Support for accessibility (Adapt Framework v2.x)
Support for plugin 'globals' (Adapt Framework v2.x)
Improved install/upgrade
'Global' configurations for plugins are conditionally applied
Added basic browser-based spell-check to HTML editor
Table editing is now an option on the HTML editor
Any tag added in the HTML editor is now preserved
Support for 'Autofill' on graphic components
Confirmation when deleting a component/extension item, such as a narrative or question stem
Ability to delete assets
Support for Adapt Framework v2.x assessment extension

Changed

Course now has a Display Title property
Default plugins are now taken from the framework adapt.json file, hard-coded references to plugins are
Removed the dependency on adapt-cli
Added better logging for Validation Failed errors on database operations
Remove hard-coded references to core plugins
Upgrade to Express 4, support NodeJS 0.12.6, i.e. removed hard dependency on 0.10.33
Any logger.log() calls now support placeholders properly
Authoring tool specific properties now removed from output JSON
Updated logo

Fixed

Bug: Course tags lost when a hero image is added or removed
Bug: Broken preview and publish after deleting asset
Bug: Tutor extension breaks configuration screen
Bug: Asset collection not displaying results when a small number of records should have been retrieved
Bug: Component type label gets lost on plugin upgrade
Bug: 500 error when updating plugins with framework v1.1.5
Bug: Resource link save errors
Bug: Assets on moved components hold reference to previous block
Bug: When ffmpeg is not installed, the thumbnailPath 'none' causes issues with routers
Bug: Deleting an article or page does not remove associated assets contained with in
Bug: Modal overlay has a few responsive issues when appending content/custom editing views
Bug: Issue with long list item attribute values going outside of the list item box
Bug: Issue with nested items in backbone forms showing as [object Object]
Bug: Course tags were removed when a hero image was added or removed

How to upgrade

IMPORTANT: If upgrading from a previous installation, first remove the node_modules folder and run

npm install --production

to install the latest code dependencies, then run

node upgrade

to get the latest authoring tool and framework changes.

I hope you enjoy using 0.1.2 and welcome any feedback at:
https://github.com/adaptlearning/adapt_authoring/issues

Thanks,

Brian

This is fantastic news. Thanks to Brian and the team. I am currently running the upgrade and cannot wait to get my hands on the tool.

Show parent | Reply

Great news, thanks to everyone involved!

For those of us currently using the develop branch (see Authoring Tool Headaches), is it safe to just switch back to the master branch and run the upgrade as above, or is there anything else/different that we need to do? For example,

git checkout master

Remove node_modules

npm install --production

node upgrade

Show parent | Reply

Hi Ryan,

Yes, it should be safe to switch to the master branch. Following running node upgrade as you're switching branches you may have to run

grunt build:dev

grunt build:prod

in order to regenerate the en.json language pack. (The second command generates compressed JavaScript and CSS) .

Show parent | Reply

Hi,

I'm just getting around to testing this out on my local machine today (before I touch our production server) and the upgrade script seems to be failing without showing any errors:

$ node upgrade
This script will update the Adapt Builder (and/or Adapt Framework) to the latest
 released version. Would you like to continue?
prompt: Y/n: (Y)
Checking versions
Currently installed versions:
- Adapt Builder: v0.1.1
- Adapt Framework: v1.1.1
Checking for Adapt Builder upgrades...
Checking for Adapt Framework upgrades...

If I start the server, it does recognize that an upgrade is available:

You are currently running Adapt Builder v0.1.1 - v0.1.2 is now available
The Adapt Framework being used is v1.1.1 - v2.0.2 is now available
Run "node upgrade.js" to update to the latest version

Any suggestions?

Show parent | Reply

Ok, think I figured it out. Apologies if I missed an earlier thread about this somewhere, but there must have been a bug in the 0.1.1 upgrade script. I copied over a newer version of upgrade.js from github into adapt_authoring and the upgrade worked this time.

Cheers,

Ryan

Show parent | Reply

i got this error when i run node upgrade , how can i solve this error

Show parent | Reply

Hi Khaled,

The log output seems to indicate some problem with nodist. What do you get if you use the NodeJS 0.10.33 installer instead of nodist?

Brian

Show parent | Reply

thank you Brian Quinn for your replay

I got this error when i use Nodejs command .

Show parent | Reply

Hi Khaleed,

There appears to be something wrong with your Node.js installation. Have you installed the binaries from here?
https://nodejs.org/dist/v0.10.33/

Brian

Show parent | Reply

Khaled appears to be using the node.exe directly, instead of invoking node from a standard command prompt (have a look at the path in the title bar).

Khaled, can you try hitting opening a standard windows command prompt in administrator mode, then running the command "node -v" once again?

Show parent | Reply

I got this error msg when i run the node -v from the CMD with admin write

Show parent | Reply

Hi Khaled,

Maybe you've solved this already, but to me it looks like you need to tell nodist to install a specific version of node AND to use that version before you can run any node commands (you may or may not have done the first step already):

Install 0.10.33:

nodist + v0.10.33

Use 0.10.33:

nodist 0.10.33

Hope that helps.

Show parent | Reply