Prerequisites for using the ilos Button plugin for Atto:

  • Access to the server where Moodle is installed and running. As this plugin is not registered for automatic update, it cannot be upgraded from Moodle UI and requires direct access to the server.
  • The Atto rich text editor for Moodle. This may be enabled by navigating to Site Administration > Plugins > Text editors > Manage editors on the left-hand column of the Moodle page and using the up/down arrows to move 'Atto HTML editor' to the top of the list. Make sure that Atto is enabled by confirming that its corresponding icon under the 'Enable' column shows an unobstructed eye, or click the icon until it appears this way.

Installation Instructions:

Watch this video to see how it's done or follow the written steps below.

Step 1: Get the latest release source package (either as zip or tar.gz) from https://github.com/ilosvideos/moodleAttoPlugin/releases

Step 2: (Upgrade only) Log in to your Moodle server as an administrator and delete /lib/editor/atto/plugins/ilosbutton

Step 3: Extract the source package under /lib/editor/atto/plugins. "ilos-Button-for-Atto-master" directory should be created.

Step 4: Rename "ilos-Button-for-Atto-master" "ilosbutton".

Step 5: Access the Moodle home page (as an admin). Moodle should detect the new/upgraded plug-in and show "Plugins check" screen which prompts you to install/upgrade. Click "Upgrade Moodle database now" button to proceed.

Step 6: After installation, Moodle is going to redirect you to the plugin settings page. Copy your Consumer key in the Textbox. You can find your Consumer key in the ilos web app (app.ilosvideos.com) under Account Settings > Integrations > LTI API Keys.

Step 7: Visit Site Administration > Plugins > Text Editors > Atto Toolbar Settings and confirm that 'ilosButton' has been added to the list of installed plugins for Atto.

Step 8: On this same page, add 'ilosbutton' to the list of buttons following the heading 'style1' (it should now read 'style1 = title, bold, italic, widget, ilosbutton') and save changes.

Step 9: Under the 'Site Administration' tab on the left side of the screen, navigate to Security > Site Policies and check the box next to 'Enable Trusted Content'. By default, trusted content (e.g. ilos Videos) can be posted by those assigned the role Manager or Course Creator. Trusted roles may be added under Site Administration > Permissions > Users > Define Roles by selecting a role and enabling or disabling 'Enable Trusted Content' for that role.

Step 10: Navigate to Site Administration > Users > Permissions > Define Roles and assign the users who should be allowed to post ilos videos one of the roles in which posting trusted content is enabled.

Step 11: The ilos button for Atto should now be installed and will appear on all rich text input windows throughout the Moodle site.

Usage Instructions:

  1. On a rich text input window on the Moodle site, navigate the cursor to the position at which you would like your video to be inserted and click the ilos button (the button containing the red ilos logo).
  2. Login, into your ilos account.
  3. Search the video you want.
  4. Click the video and it should be inserted as an iframe in the rich text editor

 Making changes to the code:

Any changes to the plugin code within 'button.js' must be processed using YUI Shifter found at https://github.com/yui/shifter. To use the shifter, first install it by following the instructions on the linked page. Then, after saving any changes to 'button.js', open a terminal or command prompt window and navigate to the directory within the ilos Button folder containing the file 'build.json' (this should be yui/src/button) and run the 'shifter' command. After the script confirms that it executed successfully, reinstall the plugin by first uninstalling the current active version via Site Administration > Plugins > Text Editors > Atto Toolbar Settings on the Moodle page (making sure you keep a copy of the newly modified directory), and then following the above installation instructions, using the directory containing the new, processed code.

Did this answer your question?