GitLab

More work on profile views and three new blocktypes (myfriends/mygroups/myviews) to emulate current profile page TODO: - write wall blocktype - change install default profile view hook to add blocks - upgrade path (xmldb & migration) - blocktype and category and singleblockperview implementation

    - TESTING

this is meant to simplify both the creation of config.php (still from
config-dist.php) and the addition of new config variables that don't
have UI.  they now get added to config-defaults.php which is loaded
after config.php and database.

Perform validation on the parameters while we're in the area.

Get the information about where an MNET user has come from, from the database rather than hackily storing it in the session when they log in.

Add a link to the profile sideblock that says where you came from if you're an MNET user, and gives you the ability to jump back there.

Conflicts:

	htdocs/auth/xmlrpc/lang/en.utf8/auth.xmlrpc.php

* Remove a couple of functions from the group libs that are only used in one or two places:
 - get_owned_groups was only used on user/view and for the sideblock showing the groups you owned. We're going to show more than that now, meaning the function is wasted indirection for the one remaining place it would be used.
 - get_tutor_groups was only used on user/view, and has been broken by the group schema changes.
* Fix adding users to controlled communities. Still have to provide the ability to do this by dropdown.
* Fixed a bug caused by my misunderstanding of how (array) false works - it seems to make an array with 'false' as one value.

This is quite an expensive operation. I guess one day large installs will have problems with it, but it can probably be re-implemented in a more performant manner when needed.

Conflicts:

	htdocs/lib/version.php

Remove the last remnants of the myportfolio theme, and fix a bug that causes a crash when choosing themes without a config.php

Now it is expected that all themes have a config.php.
(cherry picked from commit ed48e680)

This makes it easy to tell when you are doing this on all pages - not just on pages where the sidebar is visible.
(cherry picked from commit ba080c55)

The XML extension is needed by the RSS blocktype to parse RSS feeds. To be honest, I'm surprised it wasn't needed before to parse the install.xml files.
(cherry picked from commit d49f1ab0)

This image can be sent with a long expires header, so given that it is on every page this makes sense.

Even if the user changes their profile icon, the image shown to them will still be correct, because it will be at a different URL now.

If a user has checked out a language pack repository, they can add the path of it to a new configuration variable, 'langpacksearchpaths', which is an array of paths to search.

Helpfiles are not handled yet.

This can be tested by checking out the en_AR.utf8 language pack and adding it to langpacksearchpaths. You should get an option to use language 'Avast!'.

This patch makes most blocktypes have no title set by default when created. For those that used to set their own titles, if no title is set after the configuration form is submitted, then they get the chance to set the title.

So for example, the RSS block will start with an empty title, but if the user doesn't set it, the title will be the title of the feed that is being syndicated.

Blocks like 'textbox' still keep their defaults, because they don't have any special case way of setting their own titles.

Use it in check_dir_exists, to set the permissions of directories created in dataroot.

Directories used to be created 0777, which is unnecessary unless the user is on shared hosting and needs to download their dataroot at some point later (which they will do for backup purposes).

Add support in pieform_configure to have the theme say which form renderer it wants to use. Also enable a configuration option, 'descriptionintwocells', which makes positioning descriptions under form inputs easier.

Add a new function, plugin_types_installed(), which returns only those plugin types that are installed.

Use this function when handling events so we don't attempt to send events to plugins that aren't available.

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

 * Give authentication plugins titles and descriptions, which are used by the authlist pieform element so people see an easier name
 * Add a new API method to the PluginAuth class, is_usable(). This can be used by auth plugins to check that required extensions are available. The authlist element will tell the user what they need to do to enable a plugin.