Bootstrap Elements
Maintained by
Jez H, Mike Grant, Manoj Solanki
Bootstrap Elements gives you the ability to add modal and toggles to your courses, helping to improve the layout of courses.
Comments
Comments are no longer open for new posts. Existing comments remain available to read.
Your plugin is very useful, especially because it allows you to produce pop-up labels with buttons with symbols. That is progress. Looking forward to Moodle 3.5 release.
Greetings...
We'll endeavour to release a 3.5 version soon as we're able to and review the feature requests for Moodle Mobile support and optional font awesome support.
Regards,
M
Your plugin is not available for Moodle 3.5.1 (errors)
Thank you
Daniel
Codes errors:
XML database file errors found
×Debug info: Errors found in XMLDB file: PATH attribute does not match file directory: mod/bootstrapelements/db
Error code: ddlxmlfileerror
×Stack trace:
line 352 of /lib/ddl/database_manager.php: ddl_exception thrown
line 368 of /lib/ddl/database_manager.php: call to database_manager->load_xmldb_file()
line 770 of /lib/upgradelib.php: call to database_manager->install_from_xmldb_file()
line 512 of /lib/upgradelib.php: call to upgrade_plugins_modules()
line 1857 of /lib/upgradelib.php: call to upgrade_plugins()
line 694 of /admin/index.php: call to upgrade_noncore()
fontawesome-iconpicker.min.js:1 Uncaught ReferenceError: jQuery is not defined
at fontawesome-iconpicker.min.js:1
at fontawesome-iconpicker.min.js:1
modedit.php?sr=0&add=bootstrapelements§ion=3&course=7&theme=boost:370 Uncaught ReferenceError: $ is not defined
at modedit.php?sr=0&add=bootstrapelements§ion=3&course=7&theme=boost:370
See: https://moodle.org/mod/forum/discuss.php?d=367041
Does anyone know if this will become compatible with Moodle Mobile? At present the mobile page just shows 'bootstrapelements33' or a different number. I'm guessing this is a mobile/desktop app issue rather than the plugin.
Any thoughts? Thanks!
Plugin service info: For the record, I just made Jeremy (one of the two current maintainers) the lead maintainer of this plugin. I tried to contact Mike (the previous lead maintainer) via email and personal message on 15 December 2017 to get his explicit agreement. Mike has not replied. His last access to this site was 3 months ago. Given that Jeremy has already been a maintainer and he is the author of the recent update, I believe that changing the lead maintainer make sense and is in a public interest. In case Mike re-appears, we can communicate further with how to deal with the ownership of the plugin. Thanks.