New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rethink how we do exports (Trac #5017) #5017
Comments
cash wrote on 43084404-06-03 As an example of the confusion generated by this, see #440 |
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) |
Personally I think I'd like to drop the export APIs. They give out too much information by default... |
Very very much agreed |
2.0 is our opportunity for this |
PR #8427 |
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.
The text was updated successfully, but these errors were encountered: