Mahara 1.1 will just do this in config-defaults.php

The former controls whether Mahara should send any e-mail. If set to false, Mahara will never send email. Good for setting up a test system when you don't want to muck around with users' email addresses to prevent sending.

The latter allows you to have all email emerging from the system sent to some other e-mail address instead of where it is aimed for.

Add function raise_memory_limit from Moodle, and use it to raise Mahara's default working memory to 32M.

This comes after a few complaints that certain RSS feeds would cause the View editor to die. Noticed by Derrin, mjmontagne and myself (on biobrio).

http://www.mahara.org/node/406

It exists in the old repo, and anyone cloning from the new repo doesn't
need to know.

We need to upgrade phpmailer laterz.

The diff is noisy because upstream changed the line endings.

We are maintaining our patches to Snoopy, mostly centering around the Host header.

We never restrict profile icon viewing by what view the icon is in - at least in 1.0.X

Don't ignore exceptions without error code 704/404 when bootstrapping peers. Thanks to Dan Poltawski

[#3000] quote a string value in a query for 8.3 compliance. Chris Bandy and Piers Harding, patch doctored by me for readability.

Don't show 'release view' link when a view is being listed in a controlled group that it hasn't been submitted to.

[#2227] If we're decrypting a message and the signature doesn't validate, try grabbing a new public key from the remote host and verifying the message again.

This is the last bit of functionality required before all given cases of Moodle/Mahara keyswap work. Yay!

Renamed the SSO Peers block to Network Servers (in lieu of a better idea, this is what Moodle calls it anyway).

Moved the langauge string and help text to the XMLRPC authentication plugin, where it belongs.

When decrypting responses to our XMLRPC requests, consider an older key to be OK. This fixes keyswap when both hosts have different keys (!)

[#2227] When we receive a request using an old key, respond with a signed and encrypted message with our new key.

This makes it so that when Moodle and Mahara are set up to network, and Mahara's key expires, Moodle can successfully grab the new key.

Modify get_keypair so that it can be called from outside the class, and the regenerate parameter being true actually regenerates a key.

When an CryptException occurs when sending an XMLRPC request (because the response was using an old key for example), fail in a nicer manner.

Update the message for the primary cause of this (old key) so it's more obvious in the logs.

[#2987] Set default wantsurl so that the jump URL doesn't have to set it. This makes the SSO peers block work again.

Set the default remote application to 'moodle' when configuring an XMLRPC plugin, as this is by far and away the most popular choice.

Add a debug line to the logs when a user tries to SSO in from a remote app, we don't know about them and we won't create an account for them.