)

Was returning email instead of apikey. Fixes #1393

* We didn't actually do the database query in related_list if we
  didn't pass a dataset. This commit fixes that.
* Share the dictize function for both cases.

The controller relied on the output of related_list being a
Query object. Updated them to use the list.

The tests also relied on related_list being a Query instead of
a list. Updated them and added new asserts.

The related_list function should not need an id or dataset
parameter. We use it ourselves in the related dashboard
without an id or dataset parameter.

related_items is already sorted from the database query.
Adding another sorting at the model_dictize level looks
unnecessary and overrides the one from the query.

* Fix the test broken because it expects results from sorted.
* Correct the PEP8 change in related controller.

The related_list dictization changes returned them as returned by
the database. This change gives it a default order if they're not
previously sorted.

…ong words

This is needed as the ``user add`` command is supposed to accept a variable number
of arguments.

Needed an automated way to get the latest version number, so I added
functions to doc/conf.py for this, and then used them in the source and
package install docs.

Stop Sphinx from hyperlinking part of the URL in pip install commands.

The current logic was unclear. If a user belongs to at least one
organization, the dropdown will be displayed, both on the created and
edit forms. Same for the visibility one.

If the "create_unowned_dataset" is set to True and you are not a
sysadmin and select the "No organization" option on the dataset form,
you get a validation error.

There is certain logic, albeit a bit flacky, in hiding the organization
dropwdown, in that if shown, any user belonging to an organization could
take ownership of any unowned dataset in the instance. We need to
properly define the auth rules and enforce them at the validator level
as well. For the time being, showing the dropdown only to sysadmins
makes sense (and of course fixing the original bug on the visibility
field validator, which is done on the next commit)

This reverts commit f366ba6.

To not rely on owner_org being present, when the validator gets a value
of private and there is no owner_org, we request the dataset anyway and
check if it actually has an owner_org.

Added new validation tests

The who.ini file has a secret key used during authentication. To make sure
users don't forget to update it we can use the beaker session secret which
is generated randomly when creating the ckan ini file.

If users define a secret in the who.ini file, this one will be used.

To do this, we use a small custom plugin that checks the secret key and
calls the core repoze plugin afterwards.

Otherwise when disabling the activity streams the action returned before
calling the auth function, which made the auth audit fail

This was caused by removing the "This resource has no description"
message in #1302.

Match dataset ordering options with those on the main search

…nse.

This reverts commit 129aec8.