Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Rethink how we do exports (Trac #5017) #5017
Original ticket http://trac.elgg.org/ticket/5017 on 43084402-06-08 by cash, assigned to unknown.
Elgg version: 1.8
Right now a lot of information is available if someone wants to make arbitrary requests on the export endpoint. We need to develop some use cases for export.
If exporting is primarily about giving users control over there data, only that user should be able to export the data. If it is about supporting migrating data to a new site/platform, doing it through http calls is tremendously inefficient.
trac user srokap wrote on 43084724-08-06
Let's add plugin hook ('export', $entity->getType()) to export handler to allow blocking it.
Additionally we colud consider some profiles of enabling exportability (export disabled by default?), ie. no-export, admin-only, open (current logic).
Second question are exportable fields, but this is wider issue as it's used also in various viewtypes for fields selection. I've mentioned before problem with the view serving exportable output that serves metadata and relations - that shouldn't happen IMHO (dont mistake it with default /view/GUID page handler)