GeoNode/geonode — pull request #1763 by capooti (2014-11-06 19:36:48+00:00)
Title: Publish/unpublish a resource

This PR adds a new boolean field on the ResourceBase model, is_published.

A GeoNode staff member should be able, using the Django admin interface, to publish/unpublish a layer/map/document if it is needed for any reason, regardless of the permissions on the content.
When the resource is unpublished, it will be not available to any user, including administrators, in the GeoNode site. It will be possible to publish it again by setting is_published to True still from the administrative interface.
At some point we may consider to provide an end user interface (maybe a checkbox in the permissions form?) that will be available to any user with the publish_resource base permission.

Tests and documentation are provided.

Two questions arise:
1. do we want this in standard GeoNode, or should we provide a settings to enable/disable it?
2. working on this I have realized that there is a SKIP_PERMS_FILTER settings that, when set to True, bypass the permission system. Do we really need this with the overhead of a more complicated code structure?