GitLab

On the basis of my profiling and testing over the last week,
all of the scripts affected by this patch don't need their
raise_memory_limit calls. Ensure_sanity currently sets the
memory limit to 128MB, which has been seen to be more than
sufficient for each of these use cases.

Tests have involved at least 1000 records being imported in
each case, and sometimes as many as 20,000. I would have
liked to have tested with some really full profiles (eg
lots of pictures and content), but am satisfied that there's
enough margin to cover those cases. In any case, such files
are often handled using external apps and therefore won't
be counted toward PHP's memory use anyway. Finally, the
limit can easily be increased by the user if necessary for
a particular case.

Change-Id: Ifecc83fd47da51268bae6cbd6960735eb91f9403
Signed-off-by: Nigel Cunningham <nigelc@catalyst-au.net>

Change-Id: I724a844fc9e4fbae9e58834082279b4f3f21995c

Fix an issue wherein HTML in a warning about the no reply
email setting is displayed as plain text.

Change-Id: I8bdf8325db93dc3a2bea4e040effdb641909e8eb
Signed-off-by: Nigel Cunningham <nigelc@catalyst-au.net>

When you request that check_upgrades() checks for upgrades in all
components, the return data now includes a false component called
"settings". I've moved "disablelogin", "newinstallcount" and "toupgradecount" into that settings component.

Change-Id: I57e26e0e05848da607b8a44089c92547ebda078b

Help alert admin users to the fact that there are new core Mahara plugins available in the release upgrade.

Change-Id: I85e52d925d35328e27c8785ccf4ea851cad09cd8
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

To allow for systems where the installation takes longer than their
phpini max_execution_time setting.

Made the changing of the limit pass thru a function for sanity checking

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

update of the plugin. Caught exception InstallException results in the
error-message being presented to the user and the plugin not being installed
while the installation process continues

Change-Id: Iba04bbfebe7b192409cd2e943d7449f0ec258eca
Signed-off-by: Tobias Zeuch <tobias.zeuch@kit.edu>

On doing upgrade from v1.1 to v1.8rc

Currently if a plugin does not need upgrading it displays
a message like this:
artefact.internal   1.1.0   1.1.0   Successfully upgraded to version ?

The json returned however has message : 'Nothing to upgrade' in it

So I've altered the displaying of messages so that if nothing needs
upgrading it shows the message returned in the json.

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

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

Here are all the UI changes that were made by Evonne

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

Bug1195489

Change-Id: I3d567f85bedfb92e0105e969d1770cd4e38413b5

When an upgrade is running, prevent requests for admin/upgrade.php
from immediately starting up a second unwanted upgrade by inserting
a record in the config table.  Nothing is done on fresh installs,
because the config table won't exist.

Change-Id: Ib82505d04fcb90b0ccbb461acd0d0b4646460498
Signed-off-by: Richard Mansfield <richard.mansfield@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>

Remove log_environ calls for those warnings from ensure_sanity, so they don't appear on every page
Move all the admin warnings into a single function
Display warnings on the home page after the redirect from a successful site upgrade

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

Reduce log noise from html filter & mime type messages

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

This can be used for installation as well.

Change-Id: I8eb01d792123ad70c14de59f6d245cfc96452a17
Signed-off-by: Ruslan Kabalin <ruslan.kabalin@luns.net.uk>

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

Stop the admin upgrade page from hanging when a core upgrade upgrades a plugin which is waiting to be upgraded
Signed-off-by: Richard Mansfield <richard.mansfield@catalyst.net.nz>

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

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

Use 'install' or 'upgrade' on upgrade page title/heading depending on whether it's an install or an upgrade (bug 3371)
Signed-off-by: Richard Mansfield <richardm@catalyst.net.nz>

Now Mahara will actually crash and burn if the database isn't UTF8, rather than just bitching about it.

It's time we put an end to the madness.

This gives the theme a chance to not suck and fail when theme-related changes are made that wouldn't otherwise be picked up by smarty's mtime check.
(cherry picked from commit 18f3fe7d64d7438495f6c824fdfb5f30ecc79a66)

* Valid HTML with the raw theme
* Tidyups to CSS in raw theme
* Make it more obvious you can't run the installer without JS

removing it for good this time.

This reverts commit 5780e905.

I'm going to fix installs now!

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

Signed-off-by: Andrew McMillan

- Fixed a bug in the view_layout install.xml definition
- Added view layouts to core_data