- 30 Sep, 2018 1 commit
-
-
To allow us to restrict things being shown for block when in older version. behatnotneeded Change-Id: I8d9ffe1e7b26a07fc84e3ce64e988b9d7babc396 Signed-off-by:
Robert Lyon <robertl@catalyst.net.nz>
-
- 31 Aug, 2018 1 commit
-
-
Robert Lyon authored
behatnotneeded Change-Id: I4b7b4d95bd17ff2fea81e3b750f9978471ec5d7a Signed-off-by:
Robert Lyon <robertl@catalyst.net.nz>
-
- 06 Nov, 2017 1 commit
-
-
Cecilia Vela Gurovic authored
similar to bug 1486763 behatnotneeded Change-Id: Iaa6e337434996303208a0445099825797e65ae3e
-
- 26 May, 2016 1 commit
-
-
in various places around Mahara to be more consistent with what people see on the interface. Change-Id: I83e088d39964ecd1d72945973fd0b4995b82da65
-
- 24 Nov, 2015 1 commit
-
-
Aaron Wells authored
Bug 1510421 Defines a new static PluginBlocktype method, get_css_icon(), which fetches the name of the CSS icon to use for this blocktype. It returns false by default, which tells the theme to "fall back" to the old thumbnail.png instead. 3rd-party plugins can override this to specify a particular icon to use. All the core blocktypes have been refactored to extend MaharaCoreBlocktype, which uses the blocktype name as the name of the CSS icon to use. I also deprecated the "SystemBlocktype" class while I was at it. PluginBlocktype::get_blocktypes_for_category() now returns both the results of get_css_icon() and the thumbnail.png path, so that themes can decide which they want to use. (And of course thumbnail.png is served via thumbnail.php, so 3rd party themes can provide their own custom image files if they wish.) behatnotneeded: Requires installing third-party plugins to test Change-Id: Idb1ecfc7b21175913708e695788906c11133b0c0
-
- 16 Sep, 2015 1 commit
-
-
Robert Lyon authored
Was a problem with the old delete button being an image and so passed the _x value, which was then checked for. Changed it so it checks that the submit param exists, which is more robust behatnotneeded : problem of finding the row that you just deleted as all deleted rows have the same 'Comment removed by the author' text Change-Id: Iea379badd2d364112d107977b8f53a62ac272428 Signed-off-by:
Robert Lyon <robertl@catalyst.net.nz>
-
- 24 Jun, 2015 1 commit
-
-
Change-Id: I21d4245ea468f733b08fc3e5b737d59697e45976
-
- 23 Jun, 2015 1 commit
-
-
Change-Id: I23ff972fc4721e00b319ac121a38dab4b1111f17
-
- 15 Jun, 2015 1 commit
-
-
Bug 1465107: Use Bootstrap CSS Framework Change-Id: I332f8f2ea0c317b5171fe9163912c760f6bc2c77
-
- 08 Feb, 2015 1 commit
-
-
Aaron Wells authored
Bug 1419399 Change-Id: Ia22577980bb67862f540a2ffc76dba54fc824aa5
-
- 04 Feb, 2015 1 commit
-
-
Robert Lyon authored
- Currently ordered as per this comment https://bugs.launchpad.net/mahara/+bug/1236102/comments/1 Change-Id: I95b5eac314dcbf2fef58e8b16836d4a6822b8b40 Signed-off-by:
Robert Lyon <robertl@catalyst.net.nz>
-
- 16 Nov, 2014 1 commit
-
-
Robert Lyon authored
As I'm adding in some new options and I notice that Bug #1326425 will also be adding options to get_comments so I thought it would be useful to make a default opbject of variables that one can call and alter with specific variables where needed rather than having to work out where in the function call list things need to go as that list would grow up to 10 options. Change-Id: I7111559c4d12a8de128b9526930729728a36555e Signed-off-by:
Robert Lyon <robertl@catalyst.net.nz>
-
- 22 Oct, 2014 1 commit
-
-
Aaron Wells authored
Theme files for plugins can now live under the plugin's directory or under the theme's directory. Moving the files for the core plugins to /theme should make life easier for theme developers by putting them all in one place. Change-Id: Icff863c46c80ed2d6be07cd49404bc0b7f5fc4c0
-
- 27 Mar, 2014 1 commit
-
-
Kristina Hoeppner authored
Small change to the text displayed on the edit screen in the feedback block to make it read easier and to avoid using the term "footer" as the feedback is not displayed in the footer but above it. Change-Id: Ib2cae7bae14df2a4b9d7079ad200fb8deb39fc3e Signed-off-by:
Kristina D.C. Hoeppner <kristina@catalyst.net.nz>
-
- 06 Nov, 2013 1 commit
-
-
Robert Lyon authored
- allow the feedback to display in a block. Things to note: 1) The feedback block is only to display view's comments on the view/view.php page and NOT on view/artefact.php page. 2) When in edit mode (view/blocks.php) the feedback block just displays a 'holder' message 3) When feedback block is on page the feedback does not display at base of page anymore and when one clicks the 'Place feedback' link the feedback form pops up over everything similar to how editing a block works. 4) As the feedback block only works/displays on the view page I have not fully integrated all the stuff that feedback creates ie js/form into the blocktype. I have left the view/view.php to do the js and render form - and simply position the form on the page with js. This means that if js is off the edit form will still be in it's old place. I felt this was ok because if js is off and the form was in the block it could mean things been too squashy if there was lots of columns. Change-Id: I1edaa886c5a0df1f6feb24bcdd6d8878a833d673
-