Restore group categories site option form on group categories page
Internationalise a couple of strings on manage groups page
Add manage groups section to admin home page
Signed-off-by: Richard Mansfield <richardm@catalyst.net.nz>

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

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

- Move group config options back to site options
- Remove search plugin option & search fieldset
- Move group category management to a group categories page (still to be placed in menu)
- Don't display 'item saved' every time a category is added or edited
Signed-off-by: Richard Mansfield <richardm@catalyst.net.nz>

Signed-off-by: Dan Marsden <dan@catalyst.net.nz>

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

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

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

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

Allow admins to disable T&C agreement on register page; disable for new installs due to default T&C text.
Signed-off-by: Richard Mansfield <richardm@catalyst.net.nz>

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

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

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

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

Signed-off-by: ¨Lorena <lorena.paoletti@gmail.com>
(cherry picked from commit 3fccdaa6ddb13526084b195e7fcf9b8ec12bf01e)

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

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

These parameters were already sanitised.
Signed-off-by: Francois Marier <francois@catalyst.net.nz>

(based on http://www.petefreitag.com/tools/sql_reserved_words_checker/

)
Signed-off-by: Francois Marier <francois@catalyst.net.nz>

(cherry picked from commit 664d41d66afcf8be768f7e17634c187195e73768)

All HTML output (i.e. all echo/print statements going to the browser) should
now be in this file.

This is so that we can easily review all areas of Mahara where XSS bugs could
hide (other than templates and PHP pieforms).

Note that lib/errors.php echo statements can't be moved here since we want
that file to always work and can't include other code/files.
Signed-off-by: Francois Marier <francois@catalyst.net.nz>

A global admin option allows site administrators to disable the
information entirely, though it is enabled by default for all new and
existing sites.

Users can opt not to show the information, and an account setting is
present if they wish to have it shown again. The information is shown
between the home page text set by the admin, and the user's dashboard
view.
Signed-off-by: Evan Goldenberg <evang@catalyst.net.nz>

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

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

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

Signed-off-by: Evan Goldenberg <evang@catalyst.net.nz>

This is a pluggable anti-spam infrastructure for protecting forms in
Mahara again spam.

The contact and register forms have been modified to include the
following anti-spam features:
    - hashed field names
    - honey pot (invisible) fields
    - submission time monitoring

Additionally, content checking is provided by the following spam traps:
    - NoneSpamTrap: the base class for other spam traps, does no
      checking on its own
    - SimpleSpamTrap: provides basic checks that don't require an
      internet connection
    - AdvancedSpamTrap: provides better checks that require an internet
      connection, including checking for the existence of mailservers
      and the presence of blacklisted URLs

New spam traps can easily be created by adding a file to lib/antispam
with the name MyTrapNameSpamTrap.php. Added spam traps will be
automatically detected and available for selection in the site options
page.
Signed-off-by: Evan Goldenberg <evang@catalyst.net.nz>

Signed-off-by: Evan Goldenberg <evang@catalyst.net.nz>

The Leap2A specification has rebranded and thus we should reflect that
change in the next Mahara release.

I also updated a few URLs.
Signed-off-by: Francois Marier <francois@catalyst.net.nz>

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

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

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

I'd made a call to $user->get when $user is a StdClass object.
Corrected to use $user->email and $user->id

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

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

It turns out that the import code assumes that only one user will be imported
at a time and uses static variables in a few places.

By importing only one user per page load and redirecting back to the import
page, we can work-around this problem.
Signed-off-by: Francois Marier <francois@catalyst.net.nz>