https://docs.moodle.org/22/en/api.php?action=feedcontributions&feedformat=atom&user=DavmonMoodleDocs - User contributions [en]2026-05-13T09:31:44ZUser contributionsMediaWiki 1.43.5https://docs.moodle.org/22/en/index.php?title=Journal_module&diff=97058Journal module2012-04-19T15:05:31Z<p>Davmon: </p>
<hr />
<div>The Journal Module has been disabled during install by default since Moodle 1.5 (when all Journals were converted to Online Assignments)<br />
<br />
NOTE: From Moodle 2.0 you will no longer find the Journal module installed by default as part of your CVS version of Moodle. You'll need to install it separately from contrib.<br />
see [http://moodle.org/mod/forum/discuss.php?d=96337]<br />
and [http://moodle.org/mod/forum/discuss.php?d=96334]<br />
<br />
In order to avoid data loss, the installation of the journal plugin on a Moodle 2.0 should follow the [https://docs.moodle.org/20/en/Upgrading_to_Moodle_2.0#A_word_about_optional_plugins_and_themes Upgrading to Moodle 2.0 guidelines]. [http://moodle.org/mod/forum/discuss.php?d=154910 That discussion] about the best way to upgrade contrib plugins to Moodle 2.0 could also be useful.<br />
<br />
==See also==<br />
*[http://moodle.org/plugins/view.php?plugin=mod_journal Journal module for download]<br />
*Using Moodle [http://moodle.org/mod/forum/view.php?id=736 Journal module forum]<br />
<br />
[[Category:Contributed code]]</div>Davmonhttps://docs.moodle.org/22/en/index.php?title=Journal_module&diff=96441Journal module2012-03-15T09:16:48Z<p>Davmon: </p>
<hr />
<div>The Journal Module has been disabled during install by default since Moodle 1.5 (when all Journals were converted to Online Assignments)<br />
<br />
NOTE: From Moodle 2.0 you will no longer find the Journal module installed by default as part of your CVS version of Moodle. You'll need to install it separately from contrib.<br />
see [http://moodle.org/mod/forum/discuss.php?d=96337]<br />
and [http://moodle.org/mod/forum/discuss.php?d=96334]<br />
<br />
In order to avoid data loss, the installation of the journal plugin on a Moodle 2.0 should follow the [https://docs.moodle.org/20/en/Upgrading_to_Moodle_2.0#A_word_about_optional_plugins_and_themes Upgrading to Moodle 2.0 guidelines]. [http://moodle.org/mod/forum/discuss.php?d=154910 That discussion] about the best way to upgrade contrib plugins to Moodle 2.0 could also be useful.<br />
<br />
==See also==<br />
*[http://moodle.org/mod/data/view.php?d=13&rid=325 Journal module for download]<br />
*Using Moodle [http://moodle.org/mod/forum/view.php?id=736 Journal module forum]<br />
<br />
[[Category:Contributed code]]</div>Davmonhttps://docs.moodle.org/22/en/index.php?title=Development:Moodle_flavours&diff=83340Development:Moodle flavours2011-05-09T07:26:30Z<p>Davmon: </p>
<hr />
<div>{{Infobox Project<br />
|name = Moodle flavours<br />
|state = Planning<br />
|tracker = <br />
|discussion = http://moodle.org/mod/forum/discuss.php?d=174755<br />
|assignee = David Monllaó<br />
}}<br />
<br />
''Project specification coming soon...''<br />
<br />
<br />
==Introduction==<br />
<br />
A ''flavour'' is a packaged set of Moodle site settings, plugins and language packs. Moodle Administrators will be able to create a flavour from their installation, selecting which settings, plugins and language packs will be packaged into a compressed file. They can then, share the package with the Moodle community, store it as a backup or use it to replicate the flavour to other installations they manages. It could also be useful for administrators with little Moodle experienced, allowing them to explore the Moodle settings and setup recommended by others.<br />
<br />
==Examples==<br />
* Flavours for universities with common language packs, videoconferencing plugins and the secure quiz settings<br />
* Flavours for schools with plugins more oriented towards children<br />
* Sets of audio plugins for music teaching<br />
* Local language customisations for Italian (for example) and Romanic language packs, for languages teaching<br />
* Packs of admin monitoring / reporting plugins<br />
<br />
==GSOC Original Proposal==<br />
<br />
===Short description===<br />
This project will bring flavours to Moodle, allowing Administrators to choose and load a flavour from a public repository. Flavours can contain administration settings, Moodle plugins, sub-plugins, language packs and local language strings. The repository management could be done with a database module instance on moodle.org or through the Modules and Plugins databse, although, this project will focus on the development of the flavour packaging and deployment system.<br />
<br />
===Long description===<br />
There are a lot of Moodle settings, plugins and integrations with other applications. It's fun to explore Moodle options, but not everyone has time to achieve this.<br />
<br />
Based on [http://en.wikipedia.org/wiki/AppFuse Appfuse] nomenclature, a flavour will be a Moodle package of administration settings, installed plugins, languages and the local customisations. Flavours will be distributed using a database (like the M&P or themes dbs) on moodle.org where flavour contributors can share, describe, comment or rate the submitted flavours.<br />
<br />
Flavours will be distributed as compressed files, with a .xml file to structure the flavour contents. The packaging system should respect the moodle and moodledata directory structure.<br />
<br />
To ''deploy'' a flavour, the user interface will be similar to the courses backup and restore interface, which should be familiar to Administrators. During deployment, administrators will be able to selectively nominate the flavour contents that will be used.<br />
<br />
Another consideration will be versioning; there will need to be control over configuration, plugin and language pack versions to avoid incompatibilities between releases.</div>Davmonhttps://docs.moodle.org/22/en/index.php?title=Development:Moodle_flavours&diff=83149Development:Moodle flavours2011-05-01T09:39:25Z<p>Davmon: </p>
<hr />
<div>{{Infobox Project<br />
|name = Moodle flavours<br />
|state = Planning<br />
|tracker = <br />
|discussion = <br />
|assignee = David Monllaó<br />
}}<br />
<br />
''Project specification coming soon...''<br />
<br />
<br />
==Introduction==<br />
<br />
A flavour it's a set of moodle site settings, plugins and language packs. Moodle admins could create flavours from his installation, selecting which settings, plugins and language packs should be packaged into a compressed file and then, share the package with the Moodle community, store it as a backup or use it to replicate the same to other installations he/she manages. It could also be useful for administrators not very experienced with Moodle which don't have enough time to explore all the Moodle settings: they can install the latest Moodle release, look for a flavour which matches his needs and import it.<br />
<br />
==Examples==<br />
* Flavours for universities with the most "common" language packs, videoconferencing plugins and the quiz settings with "secure" values<br />
* Flavours for schools with plugins more oriented to children<br />
* Sets of audio plugins for music teaching<br />
* Local language customizations for Italian (for example) and Romanic language packs, for languages teaching<br />
* Packs of admin monitoring / reporting plugins<br />
<br />
==GSOC Original Proposal==<br />
<br />
===Short description===<br />
This project purpose is to bring Moodle different flavours, allowing administrators to choose and load a flavour from a public repository. Every flavour could contain administration settings, Moodle plugins, sub-plugins, language packs and local language strings. The repository management could be done with a database module instance, that's not the project, the development to do is the flavour packaging and deployment system.<br />
<br />
===Long description===<br />
There are a lot of Moodle settings, plugins and integrations with other applications, it's fun to explore all that options, but not everybody has enough time to do it.<br />
<br />
To complete the short description and leaving apart the appfuse nomenclature, it is a Moodle packaging/deployment system for administration settings, installed plugins, languages and the local customizations (the recent subplugins and the local language strings) That project will not be useful without a database (like the M&P or themes dbs) on moodle.org to share, describe, comment or rate the submitted flavours.<br />
<br />
The flavours should be distributed as compressed files, with a .xml file to structure the flavour contents. The packaging system should respect the moodle and moodledata directory structure.<br />
<br />
On the deployment side, the user interface can be similar to the courses backup and restore M2.0 steps to familiarized users and to specify which flavour contents will be added. Another important point is the versioning, there should be a control of the settings, plugins and language packs versions to avoid incoherences between incompatible releases.<br />
<br />
I'm not sure about the nomenclature, packaging/deployment, export/import, backup/restore...</div>Davmonhttps://docs.moodle.org/22/en/index.php?title=Development:Moodle_flavours&diff=83148Development:Moodle flavours2011-05-01T09:37:27Z<p>Davmon: </p>
<hr />
<div>{{Infobox Project<br />
|name = Moodle flavours<br />
|state = Planning<br />
|tracker = <br />
|discussion = <br />
|assignee = David Monllaó<br />
}}<br />
<br />
''Project specification coming soon...''<br />
<br />
<br />
==Introduction==<br />
<br />
A flavour it's a set of moodle site settings, plugins and language packs. Moodle admins could create flavours from his installation, selecting which settings, plugins and language packs should be packaged into a compressed file and then, share the package with the Moodle community, store it as a backup or use it to replicate the same to other installations he/she manages. It could also be useful for administrators not very experienced with Moodle which haven't enough time to explore all the Moodle settings: they can install the latest Moodle release, look for a flavour which matches his needs and import it.<br />
<br />
==Examples==<br />
* Flavours for universities with the most "common" language packs, videoconferencing plugins and the quiz settings with "secure" values<br />
* Flavours for schools with plugins more oriented to children<br />
* Sets of audio plugins for music teaching<br />
* Local language customizations for Italian (for example) and Romanic language packs, for languages teaching<br />
* Packs of admin monitoring / reporting plugins<br />
<br />
==GSOC Original Proposal==<br />
<br />
===Short description===<br />
This project purpose is to bring Moodle different flavours, allowing administrators to choose and load a flavour from a public repository. Every flavour could contain administration settings, Moodle plugins, sub-plugins, language packs and local language strings. The repository management could be done with a database module instance, that's not the project, the development to do is the flavour packaging and deployment system.<br />
<br />
===Long description===<br />
There are a lot of Moodle settings, plugins and integrations with other applications, it's fun to explore all that options, but not everybody has enough time to do it.<br />
<br />
To complete the short description and leaving apart the appfuse nomenclature, it is a Moodle packaging/deployment system for administration settings, installed plugins, languages and the local customizations (the recent subplugins and the local language strings) That project will not be useful without a database (like the M&P or themes dbs) on moodle.org to share, describe, comment or rate the submitted flavours.<br />
<br />
The flavours should be distributed as compressed files, with a .xml file to structure the flavour contents. The packaging system should respect the moodle and moodledata directory structure.<br />
<br />
On the deployment side, the user interface can be similar to the courses backup and restore M2.0 steps to familiarized users and to specify which flavour contents will be added. Another important point is the versioning, there should be a control of the settings, plugins and language packs versions to avoid incoherences between incompatible releases.<br />
<br />
I'm not sure about the nomenclature, packaging/deployment, export/import, backup/restore...</div>Davmonhttps://docs.moodle.org/22/en/index.php?title=Development:Moodle_flavours&diff=83147Development:Moodle flavours2011-05-01T08:12:36Z<p>Davmon: </p>
<hr />
<div>{{Infobox Project<br />
|name = Moodle flavours<br />
|state = Planning<br />
|tracker = <br />
|discussion = <br />
|assignee = David Monllaó<br />
}}<br />
<br />
''Project specification coming soon...''<br />
<br />
<br />
==Introduction==<br />
<br />
A flavour it's a set of moodle site settings, plugins and language packs. Moodle admins could create flavours from his installation, selecting which settings, plugins and language packs should be packaged into a compressed file and then, share it with the Moodle community, store it as a backup or use it to replicate the same to other installations. It could also be useful for administrators not very experienced with Moodle which haven't enough time to explore all the Moodle settings: they can install the latest Moodle release, look for a flavour which matches his needs and import it.<br />
<br />
<br />
==Examples==<br />
* Flavours for universities with the most "common" language packs, videoconferencing plugins and the quiz settings with "secure" values<br />
* Flavours for schools (with plugins more oriented to children)</div>Davmonhttps://docs.moodle.org/22/en/index.php?title=Admin_presets_block&diff=82160Admin presets block2011-03-22T08:16:28Z<p>Davmon: </p>
<hr />
<div>Allow users with the site configuration capability to export the site settings to .xml presets, import other sites .xml presets, load (totally or partially) presets settings and rollback the applied changes if necessary.<br />
<br />
==Features==<br />
* Export system settings to XML files<br />
* Import presets files<br />
* Preset preview and partial load<br />
* Rollback applied changes<br />
* Option to auto-exclude the sensible data (like passwords) when exporting settings<br />
* Editable sensible setting list<br />
* Third parties plugins supported (as long as they use the moodle core admin_setting classes)<br />
<br />
==Installation==<br />
* Download the latest version from the [http://moodle.org/mod/data/view.php?d=13&rid=4660 Modules and Plugins entry]<br />
* Unzip and rename the folder from dmonllao-moodle-block_admin_presets-xxxxxxx to admin_presets<br />
* Copy the admin_presets folder inside blocks/<br />
* Login as an admin user and install as usual through the 'Notifications' like of the frontpage administration block<br />
* Reconfigure the sensible settings if it's necessary<br />
<br />
==See also==<br />
* [http://moodle.org/mod/data/view.php?d=13&rid=4660 Modules and Plugins entry], where you can find more info about it<br />
* [http://moodle.org/mod/forum/discuss.php?d=171536 Forum discussion]<br />
* [http://tracker.moodle.org/browse/CONTRIB/component/10914 Tracker component], for bugs and other issues<br />
<br />
<br />
[[Category:Contributed_code]]</div>Davmonhttps://docs.moodle.org/22/en/index.php?title=Admin_presets_block&diff=82159Admin presets block2011-03-22T08:12:59Z<p>Davmon: New page: Allow users with the site configuration capability to export the site settings to .xml presets, import other sites .xml presets, load (totally or partially) presets settings and rollback t...</p>
<hr />
<div>Allow users with the site configuration capability to export the site settings to .xml presets, import other sites .xml presets, load (totally or partially) presets settings and rollback the applied changes if necessary.<br />
<br />
==Features==<br />
* Export system settings to XML files<br />
* Import presets files<br />
* Preset preview and partial load<br />
* Rollback applied changes<br />
* Option to auto-exclude the sensible data (like passwords) when exporting settings<br />
* Editable sensible setting list<br />
* Third parties plugins supported (as long as they use the moodle core admin_setting classes)<br />
<br />
==Installation==<br />
* Download the latest version from the [http://moodle.org/mod/data/view.php?d=13&rid=4660 Modules and Plugins entry]<br />
* Unzip and rename the folder from dmonllao-moodle-block_admin_presets-xxxxxxx to admin_presets<br />
* Copy the admin_presets folder inside blocks/<br />
* Login as an admin user and install as usual through the 'Notifications' like of the frontpage administration block<br />
* Reconfigure the sensible settings if it's necessary<br />
<br />
==See also==<br />
* [http://moodle.org/mod/data/view.php?d=13&rid=4660 Modules and Plugins entry], where you can find more info about it<br />
* [http://moodle.org/mod/forum/discuss.php?d=171536 Forum discussion]<br />
* [http://tracker.moodle.org/browse/CONTRIB/component/10914 Tracker component], for bugs and other issues</div>Davmonhttps://docs.moodle.org/22/en/index.php?title=Monitoraccesses_report&diff=80973Monitoraccesses report2011-01-31T22:09:10Z<p>Davmon: </p>
<hr />
<div>Admin report to check which users are logged into moodle between defined time ranges.<br />
<br />
It counts the time each selected user has passed connected to Moodle between the selected ranges, if the user didn't logout it considers the (login + session timeout) as logout time.<br />
<br />
==Features==<br />
Allows users (new capability defined report/monitoraccesses:view, available to admins by default) to <br />
monitor accesses of the selected users from the selected courses between the selected <br />
time ranges (until 3) and the selected days of the year.<br />
<br />
* Selection of courses and users<br />
* Filter by time and date/s and/or month/s<br />
<br />
==Installation==<br />
Following the [https://docs.moodle.org/en/Installing_contributed_modules_or_plugins Installing contributed code documentation]:<br />
* Copy the monitoraccesses/ folder into the folder admin/report<br />
* Logged as an admin user click 'Notifications' on the frontpage administration block<br />
* Redefine the default capability if necessary<br />
<br />
==See also==<br />
*[https://github.com/dmonllao/moodle-report_monitoraccesses Repository link]<br />
<br />
[[Category:Contributed_code]]</div>Davmonhttps://docs.moodle.org/22/en/index.php?title=Monitoraccesses_report&diff=80972Monitoraccesses report2011-01-31T22:04:36Z<p>Davmon: /* Installation */</p>
<hr />
<div>Admin report to check which users are logged into moodle between defined time ranges.<br />
<br />
It counts the time each selected user has passed connected to Moodle between the selected ranges, if the user didn't logout it considers the (login + session timeout) as logout time.<br />
<br />
==Features==<br />
Allows users (new capability defined report/monitoraccesses:view, available to admins by default) to <br />
monitor accesses of the selected users from the selected courses between the selected <br />
time ranges (until 3) and the selected days of the year.<br />
<br />
* Selection of courses and users<br />
* Filter by time and date/s and/or month/s<br />
<br />
==Installation==<br />
Following the [https://docs.moodle.org/en/Installing_contributed_modules_or_plugins Installing contributed code documentation]:<br />
* Copy the monitoraccesses/ folder into the folder admin/report<br />
* Logged as an admin user click 'Notifications' on the frontpage administration block<br />
* Redefine the default capability if necessary<br />
<br />
==See also==<br />
*[https://github.com/dmonllao/moodle-report_monitoraccesses Repository link]</div>Davmonhttps://docs.moodle.org/22/en/index.php?title=Monitoraccesses_report&diff=80971Monitoraccesses report2011-01-31T22:03:56Z<p>Davmon: New page: Admin report to check which users are logged into moodle between defined time ranges. It counts the time each selected user has passed connected to Moodle between the selected ranges, if ...</p>
<hr />
<div>Admin report to check which users are logged into moodle between defined time ranges.<br />
<br />
It counts the time each selected user has passed connected to Moodle between the selected ranges, if the user didn't logout it considers the (login + session timeout) as logout time.<br />
<br />
==Features==<br />
Allows users (new capability defined report/monitoraccesses:view, available to admins by default) to <br />
monitor accesses of the selected users from the selected courses between the selected <br />
time ranges (until 3) and the selected days of the year.<br />
<br />
* Selection of courses and users<br />
* Filter by time and date/s and/or month/s<br />
<br />
==Installation==<br />
Following the [https://docs.moodle.org/en/Installing_contributed_modules_or_plugins Install contributed code docs]:<br />
* Copy the monitoraccesses/ folder into the folder admin/report<br />
* Logged as an admin user click 'Notifications' on the frontpage administration block<br />
* Redefine the default capability if necessary<br />
<br />
==See also==<br />
*[https://github.com/dmonllao/moodle-report_monitoraccesses Repository link]</div>Davmonhttps://docs.moodle.org/22/en/index.php?title=Journal_module&diff=80970Journal module2011-01-31T17:59:09Z<p>Davmon: </p>
<hr />
<div>The Journal Module has been disabled during install by default since Moodle 1.5 (when all Journals were converted to Online Assignments)<br />
<br />
NOTE: From Moodle 2.0 you will no longer find the Journal module installed by default as part of your CVS version of Moodle. You'll need to install it separately from contrib.<br />
see [http://moodle.org/mod/forum/discuss.php?d=96337]<br />
and [http://moodle.org/mod/forum/discuss.php?d=96334]<br />
<br />
In order to avoid data loss, the installation of the journal plugin on a Moodle 2.0 should follow the [https://docs.moodle.org/en/Upgrading_to_Moodle_2.0#A_word_about_optional_plugins_and_themes Upgrading to Moodle 2.0 guidelines]. [http://moodle.org/mod/forum/discuss.php?d=154910 That discussion] about the best way to upgrade contrib plugins to Moodle 2.0 could also be useful.<br />
<br />
==See also==<br />
*[http://moodle.org/mod/data/view.php?d=13&rid=325 Journal module for download]<br />
*Using Moodle [http://moodle.org/mod/forum/view.php?id=736 Journal module forum]<br />
<br />
[[Category:Contributed code]]</div>Davmonhttps://docs.moodle.org/22/en/index.php?title=Adobe_Connect_block&diff=70857Adobe Connect block2010-04-09T08:14:15Z<p>Davmon: /* Features */</p>
<hr />
<div>The Adobe Connect block is contributed code that provides single sign on (SSO) with an Adobe Connect server, it also creates Adobe Connect rooms and users from Moodle courses and users. As web conferencing software, Adobe Connect has audio/video, screen sharing, text chat and conferencing tools. <br />
<br />
<br />
==Features==<br />
<br />
Simple one-way synchronization from Moodle to Adobe Connect. It creates the course room the first time a course user accesses, as well as the user-room assignment and the user itself.<br />
<br />
There are two capabilities, one for Adobe Connect "host" role, usually a teacher, and another for Adobe Connect "view" role.<br />
<br />
The block uses the Adobe Connect web services to create rooms, create users, assigns users to rooms and login users into Adobe Connect from Moodle, in order to do that, Adobe Connect administrator credentials must be configured on the block settings page.<br />
<br />
The Adobe Connect rooms names are the Moodle course id, and the users are created with the Moodle email as Adobe Connect username and the username in md5 as password.<br />
<br />
For a more suitable integration with Adobe Connect see Adobe Connect module by Remote Learner:<br />
<br />
[http://moodle.org/mod/data/view.php?d=13&rid=3599 Adobe Connect module by Remote Learner modules and plugins page]<br />
<br />
[https://docs.moodle.org/en/Remote_learner_adobe_connect_pro Adobe Connect module by Remote Learner Moodle Docs page]<br />
<br />
==Usage==<br />
* After the block installation and configuration, users with edition course privileges can add a block instance at course level (not at site level) as usual.<br />
* Once the logged user clicks on the block link, a new window will be opened and he/she will be redirected to the Adobe Connect room of the course.<br />
<br />
==Requirements==<br />
* Adobe Connect Server, version >= 6<br />
* PHP Curl library installed<br />
* Optional but highly recommended, Adobe Connect application server with SSL<br />
<br />
==Installation==<br />
* Copy to Moodle blocks/ folder<br />
* Click "Notifications" link, on frontpage admin settings tree<br />
* Go to the frontpage admin tree, "Modules" -> "Blocks" -> "Adobe Connect" to configure the block, setting the host and an Adobe Connect admin user to allow the block to create rooms, user...<br />
* Define which roles can use the integration in the frontpage admin settings tree, "Users" -> "Permissions" -> "Define roles". By default it's only enabled for Moodle 'admin' role<br />
<br />
==Other information==<br />
* Supported languages: English, Español and Català<br />
* Moodle supported versions: 1.9 and 1.9.x<br />
<br />
==See also==<br />
* [http://moodle.org/mod/data/view.php?d=13&rid=3594 Adobe Connect Block in Modules and Plugins Database]<br />
* [http://download.moodle.org/download.php/plugins19/blocks/adobeconnect.zip Download for Moodle 1.9]<br />
* [http://tracker.moodle.org/browse/CONTRIB/component/10610 Tracker Component]<br />
*[[Remote learner adobe connect pro]] - a contributed code activity module<br />
<br />
<br />
<br />
[[Category:Contributed_code]]</div>Davmonhttps://docs.moodle.org/22/en/index.php?title=Adobe_Connect_block&diff=69866Adobe Connect block2010-03-18T13:10:21Z<p>Davmon: </p>
<hr />
<div>The Adobe Connect block is contributed code that provides single sign on (SSO) with an Adobe Connect server, it also creates Adobe Connect rooms and users from Moodle courses and users. As web conferencing software, Adobe Connect has audio/video, screen sharing, text chat and conferencing tools. <br />
<br />
<br />
==Features==<br />
<br />
Simple one-way synchronization from Moodle to Adobe Connect. It creates the course room the first time a course user accesses, as well as the user-room assignment and the user itself.<br />
<br />
There are two capabilities, one for Adobe Connect "host" role, usually a teacher, and another for Adobe Connect "view" role.<br />
<br />
The block uses the Adobe Connect web services to create rooms, create users, assigns users to rooms and login users into Adobe Connect from Moodle, in order to do that, Adobe Connect administrator credentials must be configured on the block settings page.<br />
<br />
The Adobe Connect rooms names are the Moodle course id, and the users are created with the Moodle email as Adobe Connect username and the username in md5 as password.<br />
<br />
For a more suitable integration with Adobe Connect see [[Remote learner adobe connect pro]]<br />
<br />
<br />
==Usage==<br />
* After the block installation and configuration, users with edition course privileges can add a block instance at course level (not at site level) as usual.<br />
* Once the logged user clicks on the block link, a new window will be opened and he/she will be redirected to the Adobe Connect room of the course.<br />
<br />
==Requirements==<br />
* Adobe Connect Server, version >= 6<br />
* PHP Curl library installed<br />
* Optional but highly recommended, Adobe Connect application server with SSL<br />
<br />
==Installation==<br />
* Copy to Moodle blocks/ folder<br />
* Click "Notifications" link, on frontpage admin settings tree<br />
* Go to the frontpage admin tree, "Modules" -> "Blocks" -> "Adobe Connect" to configure the block, setting the host and an Adobe Connect admin user to allow the block to create rooms, user...<br />
* Define which roles can use the integration in the frontpage admin settings tree, "Users" -> "Permissions" -> "Define roles". By default it's only enabled for Moodle 'admin' role<br />
<br />
==Other information==<br />
* Supported languages: English, Español and Català<br />
* Moodle supported versions: 1.9 and 1.9.x<br />
<br />
==See also==<br />
* [http://moodle.org/mod/data/view.php?d=13&rid=3594 Adobe Connect Block in Modules and Plugins Database]<br />
* [http://download.moodle.org/download.php/plugins19/blocks/adobeconnect.zip Download for Moodle 1.9]<br />
* [http://tracker.moodle.org/browse/CONTRIB/component/10610 Tracker Component]<br />
*[[Remote learner adobe connect pro]] - a contributed code activity module<br />
<br />
<br />
<br />
[[Category:Contributed_code]]</div>Davmonhttps://docs.moodle.org/22/en/index.php?title=Adobe_Connect_block&diff=69239Adobe Connect block2010-03-03T08:17:33Z<p>Davmon: /* See also */</p>
<hr />
<div>Provides SSO with an Adobe Connect server, it also creates Adobe Connect rooms and users from Moodle courses and users.<br />
<br />
<br />
==Features==<br />
<br />
One-way synchronization, from Moodle to Adobe Connect. It creates the course room the first time a course user accesses, as well as the user-room assignment and the user itself.<br />
<br />
There are two capabilities, one for Adobe Connect "host" role, usually a teacher, and another for Adobe Connect "view" role.<br />
<br />
The block uses the Adobe Connect web services to create rooms, create users, assigns users to rooms and login users into Adobe Connect from Moodle, in order to do that, Adobe Connect administrator credentials must be configured on the block settings page.<br />
<br />
The Adobe Connect rooms names are the Moodle course id, and the users are created with the Moodle email as Adobe Connect username and the username in md5 as password.<br />
<br />
<br />
==Usage==<br />
* After the block installation and configuration, users with edition course privileges can add a block instance at course level (not at site level) as usual.<br />
* Once the logged user clicks on the block link, a new window will be opened and he/she will be redirected to the Adobe Connect room of the course.<br />
<br />
==Requirements==<br />
* Adobe Connect Server, version >= 6<br />
* PHP Curl library installed<br />
* Optional but highly recommended, Adobe Connect application server with SSL<br />
<br />
==Installation==<br />
* Copy to Moodle blocks/ folder<br />
* Click "Notifications" link, on frontpage admin settings tree<br />
* Go to the frontpage admin tree, "Modules" -> "Blocks" -> "Adobe Connect" to configure the block, setting the host and an Adobe Connect admin user to allow the block to create rooms, user...<br />
* Define which roles can use the integration in the frontpage admin settings tree, "Users" -> "Permissions" -> "Define roles". By default it's only enabled for Moodle 'admin' role<br />
<br />
==Other information==<br />
* Supported languages: English, Español and Català<br />
* Moodle supported versions: 1.9 and 1.9.x<br />
<br />
==See also==<br />
* [http://moodle.org/mod/data/view.php?d=13&rid=3594 Adobe Connect Block in Modules and Plugins Database]<br />
* [http://download.moodle.org/download.php/plugins19/blocks/adobeconnect.zip Download for Moodle 1.9]<br />
* [http://tracker.moodle.org/browse/CONTRIB/component/10610 Tracker Component]<br />
<br />
<br />
[[Category:Contributed_code]]</div>Davmonhttps://docs.moodle.org/22/en/index.php?title=Adobe_Connect_block&diff=69234Adobe Connect block2010-03-03T07:52:09Z<p>Davmon: </p>
<hr />
<div>Provides SSO with an Adobe Connect server, it also creates Adobe Connect rooms and users from Moodle courses and users.<br />
<br />
<br />
==Features==<br />
<br />
One-way synchronization, from Moodle to Adobe Connect. It creates the course room the first time a course user accesses, as well as the user-room assignment and the user itself.<br />
<br />
There are two capabilities, one for Adobe Connect "host" role, usually a teacher, and another for Adobe Connect "view" role.<br />
<br />
The block uses the Adobe Connect web services to create rooms, create users, assigns users to rooms and login users into Adobe Connect from Moodle, in order to do that, Adobe Connect administrator credentials must be configured on the block settings page.<br />
<br />
The Adobe Connect rooms names are the Moodle course id, and the users are created with the Moodle email as Adobe Connect username and the username in md5 as password.<br />
<br />
<br />
==Usage==<br />
* After the block installation and configuration, users with edition course privileges can add a block instance at course level (not at site level) as usual.<br />
* Once the logged user clicks on the block link, a new window will be opened and he/she will be redirected to the Adobe Connect room of the course.<br />
<br />
==Requirements==<br />
* Adobe Connect Server, version >= 6<br />
* PHP Curl library installed<br />
* Optional but highly recommended, Adobe Connect application server with SSL<br />
<br />
==Installation==<br />
* Copy to Moodle blocks/ folder<br />
* Click "Notifications" link, on frontpage admin settings tree<br />
* Go to the frontpage admin tree, "Modules" -> "Blocks" -> "Adobe Connect" to configure the block, setting the host and an Adobe Connect admin user to allow the block to create rooms, user...<br />
* Define which roles can use the integration in the frontpage admin settings tree, "Users" -> "Permissions" -> "Define roles". By default it's only enabled for Moodle 'admin' role<br />
<br />
==Other information==<br />
* Supported languages: English, Español and Català<br />
* Moodle supported versions: 1.9 and 1.9.x<br />
<br />
==See also==<br />
* [http://tracker.moodle.org/browse/CONTRIB/component/10610 Tracker Component]<br />
<br />
[[Category:Contributed_code]]</div>Davmonhttps://docs.moodle.org/22/en/index.php?title=Adobe_Connect_block&diff=69233Adobe Connect block2010-03-03T07:50:57Z<p>Davmon: New page: Provides SSO with an Adobe Connect server, it also creates Adobe Connect rooms and users from Moodle courses and users. ==Features== One-way synchronization, from Moodle to Adobe Connect...</p>
<hr />
<div>Provides SSO with an Adobe Connect server, it also creates Adobe Connect rooms and users from Moodle courses and users.<br />
<br />
==Features==<br />
<br />
One-way synchronization, from Moodle to Adobe Connect. It creates the course room the first time a course user accesses, as well as the user-room assignment and the user itself.<br />
<br />
There are two capabilities, one for Adobe Connect "host" role, usually a teacher, and another for Adobe Connect "view" role.<br />
<br />
The block uses the Adobe Connect web services to create rooms, create users, assigns users to rooms and login users into Adobe Connect from Moodle, in order to do that, Adobe Connect administrator credentials must be configured on the block settings page.<br />
<br />
The Adobe Connect rooms names are the Moodle course id, and the users are created with the Moodle email as Adobe Connect username and the username in md5 as password.<br />
<br />
<br />
==Usage==<br />
* After the block installation and configuration, users with edition course privileges can add a block instance at course level (not at site level) as usual.<br />
* Once the logged user clicks on the block link, a new window will be opened and he/she will be redirected to the Adobe Connect room of the course.<br />
<br />
==Requirements==<br />
* Adobe Connect Server, version >= 6<br />
* PHP Curl library installed<br />
* Optional but highly recommended, Adobe Connect application server with SSL<br />
<br />
==Installation==<br />
* Copy to Moodle blocks/ folder<br />
* Click "Notifications" link, on frontpage admin settings tree<br />
* Go to the frontpage admin tree, "Modules" -> "Blocks" -> "Adobe Connect" to configure the block, setting the host and an Adobe Connect admin user to allow the block to create rooms, user...<br />
* Define which roles can use the integration in the frontpage admin settings tree, "Users" -> "Permissions" -> "Define roles". By default it's only enabled for Moodle 'admin' role<br />
<br />
==Other information==<br />
* Supported languages: English, Español and Català<br />
* Moodle supported versions: 1.9 and 1.9.x<br />
<br />
==See also==<br />
* [http://tracker.moodle.org/browse/CONTRIB/component/10610 Tracker Component]<br />
<br />
[[Category:Contributed_code]]</div>Davmon