Picture of Brian Quinn
Authoring tool v0.2.0 has been released!
by Brian Quinn - Friday, 29 July 2016, 8:12 AM
 

Hi everybody,

I'm happy to announce that we've released version 0.2.0 of the authoring tool.  

The focus on this version was to overhaul the user interface, and apply more of an Adapt brand to the tool, consistent with the adaptlearning.org site.  In terms of functionality, some minor tweaks and bug-fixes have also been made.  

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

Added

  • UI consistent with the Adapt brand
  • Support for v2.0.11 of the Adapt Framework

Changed

  • Disabled SSL certificate check during Vagrant install

Fixed

  • Bug: Caching issue related to course schemas
  • Bug: Tag autocomplete mechanism sometimes throws 500 error
  • Bug: Form validation
  • Bug: Saving course settings hangs if nothing has been changed

 

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.2.0 and welcome any feedback at:
https://github.com/adaptlearning/adapt_authoring/issues

Thanks,

Brian

Picture of James Yorke
Re: Authoring tool v0.2.0 has been released!
by James Yorke - Saturday, 30 July 2016, 5:53 PM
 

Hi new to this tool (and a storyline instructional designer with some tech knowledge so making massive leaps here!)

how do i actually do the upgrade with a vagrant install on mac - where do i enter the commands listed above? in terminal i get the error 

npm: command not found

 

Thanks :)

 

James

Picture of Thomas Berger
Re: Authoring tool v0.2.0 has been released!
by Thomas Berger - Wednesday, 3 August 2016, 12:03 PM
 

Hello James,

the commands must be executed inside the Virtual Machine, if you are on a Mac you can do the following:

Remove the node_modules directory.

Open a Terminal and navigate into the directory of the authoring tool.

execture vagrant ssh

Now you should be connected to the Virtual Machine running Ubuntu 14.04.

execute cd /vagrant/

Now you are good to execute the commands Brian mentioned.

npm install --production

node upgrade

 

Thomas

Picture of Stephen Harlow
Re: Authoring tool v0.2.0 has been released!
by Stephen Harlow - Thursday, 4 August 2016, 6:18 AM
 

So I got to this point:

Upgrading the Adapt authoring tool...please hold on!

I held on, but...

fatal: Not a git repository (or any parent up to mount point /vagrant)

Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

 

ERROR: 128

Any clues? Something to do with this being a vagrant install combined with the fact I originally downloaded the Authoring Tool folder rather than cloning from the repository?

Picture of Thomas Berger
Re: Authoring tool v0.2.0 has been released!
by Thomas Berger - Wednesday, 10 August 2016, 12:49 PM
 

Hello Stephen,

exactly, upgrade requires a git repository and on Windows a hacky workaround.

Please let me know if I should guide you through this workaround. However, if you downloaded the sourcecode instead of cloning, there is no way to upgrade I am afraid.

Thomas

Picture of Stephen Harlow
Re: Authoring tool v0.2.0 has been released!
by Stephen Harlow - Wednesday, 10 August 2016, 9:36 PM
 

Thanks Thomas

I did finally manage to upgrade, from memory I think I cloned the Authoring tool from the git repository, deleted the original AT files and re-ran the upgrade script. It was a mess, but I got there in the end. I'm beginning to think that, while it may be useful for trying out Adapt, the Vagrant install path is not a long-term option for production use.

Picture of Thomas Berger
Re: Authoring tool v0.2.0 has been released!
by Thomas Berger - Thursday, 11 August 2016, 11:49 AM
 

Hello Stephen,

well done, but this step requires quite a good set of command-line skills and confidence in the same.

We fixed this issue for missing upgrade support on Windows using Vagrant in the next release.

 

But you are right, the Vagrant install method is not recommended for production. It is intended to be a convenient way to test the Authoring Tool without installing node and mongoDB.

Unfortunately the wiki was not very precise about this limitation. Sorry about that, we fixed this and hope that is now easier to understand which path is suitable for what goal.

Thomas

Picture of Stephen Harlow
Re: Authoring tool v0.2.0 has been released!
by Stephen Harlow - Thursday, 11 August 2016, 8:33 PM
 

I've now installed the Framework locally and will trial using that. Is it possible to move courses created with the Authoring tool out and edit them "by hand" as it were? Whereabouts, and for what files does one look?

It appears that this is possible as I read that Nigel's workflow involves shifting courses in and out of the Authoring tool.