Update admin_migrate for ownCloud 6. #1546
Conversation
| @@ -1,12 +1,9 @@ | |||
| <form id="export" action="#" method="post"> | |||
| <fieldset class="personalblock"> | |||
| <h2><?php p($l->t('Export data'));?></h2> | |||
| <h2><?php p($l->t('Admin Export'));?></h2> | |||
There was a problem hiding this comment.
The title should be »Config export« to be the same as in the app list. :)
|
@tomneedham what’s the status on this? |
|
@jancborchardt We need a decision on what we are going to finally do with both of these apps, and when we make the change. Following our discussion with @DeepDiver1975 in Stuttgart, I think we agreed the user_migrate app is fairly redundant. Most apps provide methods to export data individually, and file data is usually too large, but can already be zipped and streamed to the user in the files app. Admin_migrate is affected by the majority of problems mentioned above. It's only real use case is to allow admins with owncloud instances on shared hosting to download a copy of the config file if they don't have access. TL;DR IMO we depreciate user_migrate, admin_migrate and instead create a new config_export that exports the admin config. Possibly in the future we could create an app to export the database for users of shared hosting. |
|
@tomneedham good plan, I think I agree on that. @DeepDiver1975 what do you think? |
|
@DeepDiver1975 Ping. We should fix this before OC7 right? |
yes - that's the way to go from my point of view - what we should think about: |
|
Thanks. I'll put together a pull request. |
Change UI to show just one button for exporting the config file.
This pull request is complete, but must wait for another request to be completed in the core repo.