GitLab

needed to pass the js to render the expander post ajax load

Change-Id: Ia5d962aae9108ef751c120b9c89ddf18c85b0017
Signed-off-by: Robert Lyon <robertl@catalyst.net.nz>

- 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>

This was causing some problems with tagged posts
- also hiding the 'add comment' link on page edit screen.

And making the comments info show when no comments were on item and
allow comments for artefact was enabled. This is an issue with newer
versions of php.

Also placing some of the template files in the new correct location

Change-Id: I599e16b0899559a3ebcdf68cff53220b1d83f2d6
Signed-off-by: Robert Lyon <robertl@catalyst.net.nz>

Son Nguyen authored Jan 09, 2015 and Robert Lyon committed Jan 12, 2015

- Filter out draft posts when editing the blogpost block
- Don't display the post's content if it is unpublished

Change-Id: Iaaf92f29383e2f3997e214b052dd116005a971dd
Signed-off-by: Son Nguyen <son.nguyen@catalyst.net.nz>

Son Nguyen authored Nov 17, 2014 and Aaron Wells committed Dec 03, 2014

... in order to silence all the E_ALL notices

Change-Id: I0fdc9fc68ae7ffd2fa2dffe68dfbd79ee9599c06

Getting the rendering of the blogpost comment count to be done by the
block instance in a similar fashion as the other artefact blocks.

Change-Id: I67805ac33a9850c1fded17b32873e5ad90c7489f
Signed-off-by: Robert Lyon <robertl@catalyst.net.nz>

As vetted in the May 2014 dev meeting
http://meetbot.mahara.org/mahara-dev/2014/mahara-dev.2014-05-01-08.01.log.html

Change-Id: I353ed74d69a5346fbe4e8e521e5c349dbe8dcbac

- have updated copyright for the pages that had existing copyright
notices (except for the lib/pieforms/ section as i'm not too sure if
that needs changing as it is a different Catalyst IT product)

Change-Id: I11c65ad26cb9cd856cf16b1dccbd4223ba086645
Signed-off-by: Robert Lyon <robertl@catalyst.net.nz>
Signed-off-by: Aaron Wells <aaronw@catalyst.net.nz>

These closing tags are unnecessary and against our coding
guidelines. Let's get rid of them all in one go.

Change-Id: Ia94f103e525185597ee3780a3839d7577cdd0c29
Signed-off-by: Francois Marier <francois@catalyst.net.nz>

Change-Id: I2809e1042e3c07835d594e58d3922dfd6bb12d10
Signed-off-by: Richard Mansfield <richard.mansfield@catalyst.net.nz>

Signed-off-by: Richard Mansfield <richardm@catalyst.net.nz>

This was not exploitable, but will reduce the risk that a SQL injection
will be accidentally introduced in the future.
Signed-off-by: Francois Marier <francois@catalyst.net.nz>

Remove use of istemplate argument in blocks' instance_config_form and artefactchooser_element functions
Signed-off-by: Richard Mansfield <richardm@catalyst.net.nz>

Signed-off-by: Richard Mansfield <richardm@catalyst.net.nz>

Don't base block configuration on template status, apart from showing blog advanced copy options for templates only
Signed-off-by: Richard Mansfield <richardm@catalyst.net.nz>

If a blog or post is put into a View via reference, you now can't
configure that block (other than to change its title). There is a note
that points out the block has been copied, which explains this for
users.

Fixed up a couple of other problems with the blocktype configuration
forms, which should hopefully mean users won't see options they can't
use.

Now they do things like not making it compulsory to choose an artefact
if it's a template (as the creator might just want to put the block
there), and removing some options that only make sense in Views.

There's a parameter for instance_config_form and artefactchooser_element
to allow the Blocktype to detemine whether it's in a template easily.

Allow blog, blogpost and textbox blocktypes having links or manually created <img> tags to artefacts to have those artefacts counted as being within the blocktype, and thus within the view.

This is so if people manually link to or source artefacts within textual content, those artefacts will be downloadable when the view is shown to others.

Not backporting to 1.0 although the problem will most certainly exist there - the patch is just too big to trust on a stable release.

copy_artefacts_allowed.

copy_artefacts_allowed is unnecessary as it's only called if the copy
type is 'full', and there's now no way that you would want to fully
copy a block and not copy the artefacts inside it.

Some other API tidyups have been done - default_artefact_config has been
renamed to rewrite_blockinstance_config and had a method signature
change to be a bit more flexible.

The copyconfig field of the View object is gone too, no longer required.

View.

This means that blog/profile/resume blocktypes don't show up in
group/institution/site Views.

This is controlled through a new Blocktype method - allowed_in_view.
Various code had to be changed to listen to this method, mostly around
the display of the category browser.

When making a template, all blocktypes are available.

Part 3 is to change the configuration forms to be more sensible when
editing a template, and then testing what happens when blocktypes are
rendered somewhere that they "shouldn't" be - e.g. a My Friends block in
a group View.

beginning of wall and another backwards compatibility break for blocktypes now we must pass $editing parameter to render_instance (default false)

The name is largely irrelevant as it's only the creator of the file.

Signed-off-by: Andrew McMillan

Changed all requires.
Also removed not used json/renderartefact.php

Implemented get_artefacts in the BlockType parent class, so that all children don't have to implement it.

The one exception thus far is the Profile Information blocktype, which needs to add the 'profileicon' field.

 * The element is set in artefactchooser_element()
 * artefactchooser_get_element_data() works out the blog the artefact is in, as well as a shortening for the description
 * artefactchooser_get_sort_order() sorts the blogposts by what blog they are in, then by their creation time descending

Added blogpost blocktype, first cut. The title of the blogpost is used for the title of any blockinstance made.

Currently, the artefact chooser for choosing a blogpost is stuffed, because the artefact chooser is still assuming that images and files are what is in it.