A problem with this is instead of the html export using the 'raw' theme's information under /theme/raw/ it actually uses the 'raw' theme information under /export/html/theme/raw/.
So the first step for this would be to refactor how it currently works so that the html export uses resources under /theme/ directory instead. This will cut out some duplication and confusion. Also it will allow us to check for the resources under a particular theme and then fallback to the 'raw' if the resources are not found. And also allow the export html to incorporte css / image changes easier. I suspect the template/css/image files under /export/html/theme/raw/ will differ slightly to their main counterparts at the moment. So there will be some merging/renaming of things needed. -- You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it! https://bugs.launchpad.net/bugs/739528 Title: Export to HTML doesn't use selected theme Status in Mahara ePortfolio: Triaged Bug description: When a view or views is/are exported, the default "raw" style sheet (theme) is used for display. The export should use the selected theme instead. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/739528/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
