Custom Query (1174 matches)
Results (217 - 219 of 1174)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #226 | FIXED | Small code picks | ||
| Description |
pre word¶While reviewing the late changes, I found some things, I would like to be considered. edit_media() references attachments.¶edit_media() in edit/view.py references some attachment stuff. Is that still valid? delete_media_files() might use itervalues¶- for handle, listpath in media['media_files'].items(): + for listpath in media['media_files'].itervalues(): import export code: Use the init/ code¶- setup_global_and_app_config(args.conf_file) + global_config, app_config = setup_global_and_app_config(args.conf_file) ... - config, validation_result = read_mediagoblin_config(args.conf_file) - connection, db = setup_connection_and_db_from_config( - config['mediagoblin'], use_pymongo=True) + connection, db = setup_connection_and_db_from_config(app_config, use_pymongo=True) final word¶These are UNTESTED suggestions to consider. They might break everything, be completely wrong, or just useful. Take your one and comment on it. Or create branch and add it here for merging. |
|||
| #228 | FIXED | Text changes to Delete confirmation page | ||
| Description |
Attached is a screenshot of the current Delete confirmation page. This is the page you see after clicking "Delete" on a media page. The whole thing is kind of a stop gap solution, but for now I'd like to suggest these changes:
|
|||
| #229 | no-action | import from flickr -> mediagoblin | ||
| Description |
What does the glorious future hold for sucking the life out of existing centralized saas and then breathing it into free alternatives? Okay, specifically, how do we handle this use case:
|
|||
