Univention Bugzilla – Bug 42800
Add extra action to edit the META file of an app
Last modified: 2016-11-25 10:01:08 CET
We will need the possibility to edit the corresponding meta file of an app. As there exists only 1 meta file per app and UCS version, it would make sense to offer via the context menu an additional action which opens a page with a form containing all fields of the meta file.
Added appcenter-selfservice/get_meta and appcenter-selfservice/save_meta. Don't know which format for save_meta. But adjusting that should be no problem.
We still need the frontend part.
The frontend part has been committed in a first version. TODOs: * Saving does not seem to work? * Saving of logos does not work yet... @Dirk: Can you have a look? univention-management-console-module-appcenter-selfservice (1.0.0-80): r74421 | Bug #42800: add action for editing the app's meta file
Fixed
The [de] section is currently not respected...
Fixed handling of logos as base64 encoded strings. univention-management-console-module-appcenter-selfservice (1.0.0-84): r74431 | Bug #42800: parse logos as base64 strings TODOs: * A meta file cannot be created for a new App: (1) create new App (2) edit meta information + save (3) get_meta still returns empty dict * When saving a new logo, a traceback is shown * The form is not reset when loading a new app. This is important as only the values which are given in the meta file are transmitted.
(In reply to Alexander Kläser from comment #5) > The [de] section is currently not respected... The only translated elements are currently not in use, I removed them (In reply to Alexander Kläser from comment #6) > TODOs: > [...] > * The form is not reset when loading a new app. This is important as only the > values which are given in the meta file are transmitted. Done. univention-management-console-module-appcenter-selfservice (1.0.0-86): r74436 | Bug #42800: adjust layout + remove unneeded elements + reset form
@Dirk: ATM, I can upload a new logo and the file is created, however, the meta file does not contain an entry pointing to the file. Thus, re-opening the meta file, the logo will not be shown. Otherwise, the behavior (with UCS 4.1-4 + staging errata scope) looks fine to me.
(In reply to Alexander Kläser from comment #8) > @Dirk: ATM, I can upload a new logo and the file is created, however, the > meta file does not contain an entry pointing to the file. Thus, re-opening > the meta file, the logo will not be shown. Works for me. Maybe temporary bug during development.
The new version of the App Provider Portal has been released and this bug will thus be closed.