Moodle plugins directory: Lesson PDF Export | Moodle.org
Lesson PDF Export
General plugins (Local) ::: local_lessonexport
Maintained by Adam King
This plugin allows lesson modules to be exported to PDF documents with optional protection.
Latest release:
453 sites
298 downloads
64 fans
Current versions available: 2
This plugin visually displays the option to output lesson modules as PDF documents.
There are many settings that come with the PDF export plugin including custom font, footer texts, document protection, cover colours, password protection, strict exporting and more.
Document pages are ordered the same as each lesson and question pages are also supported, although some answers are not shown (such as short answer questions).
This plugin was developed for use on the SHEilds eLearning platform. If this plugin does not match your use-case, please open a ticket on Github detailing what you require for this to become a useful addition to your Moodle plugins.
Useful links
Contributors
Adam King (Lead maintainer)
Please login to view contributors details and/or to contact them
I have a problem with special (national) characters in pdf exports, but in epub format is OK. Charset is UTF-8, czech language. In pdf file, there's symbol ? instead of the local letters ř, č or š.
Can you help me ?
Thanks
i am working with Arabic lessons , when i want to export the lesson, i get it all ????? , i tried different fonts , but did not work out, is there a way to fix it or add Arabic fonts to use in the Plugins?
Thanks.
About the $settingsnav issue, I think it's related to the configuration of "Navigation block".
You can read my contribution in the Github forum thread about this issue.
Thanks
TCPDF is a programming library and, as such, shall never replace any project that uses it; it's not something you can use on it's own as somebody needs to write code that incorperates it.
Regarding your issue, do you want the PDF to include the answers the student submitted? This could prove problematic, given how TCPDF writes HTML but it's not impossible, I imagine it might cause some issues if I start writing code that touches more Moodle internals though as it will date the plugin (make it very easy for it to become incompatible with older or newer versions).
As it stands, the plugin uses some outdated functionality that will not be there in future versions (YUI, for example), but I want to support as many versions as possible before I have to re-write to use AMD modules and JQuery, among other standards. I'll have to see what needs to change for it to work with 3.2 and 3.3 (if it doesn't already), but I am definitely going to support it as Moodle is moving forward fast and great. It may already work, it may not, I haven't set up a development platform for it yet sadly.