GNOME Standards: The 'unable to publish' dialog doesn't have any 'headline' text.
Submitted by cli..@..ba.org
Assigned to cli..@..ba.org
Link to original bug (#717654)
Description
---- Reported by clinton@yorba.org 2011-04-01 15:03:00 -0700 ----
Original Redmine bug id: 3457
Original URL: http://redmine.yorba.org/issues/3457
Searchable id: yorba-bug-3457
Original author: Clinton Rogers
Original description:
To reproduce:
With at least one video in Shotwell's library, disable all publishing plugins that can accept video.
Highlight the video from step one and attempt to publish it.
Notice that the 'Shotwell cannot publish the…' alert doesn't contain any 'headline' text; per GNOME human interface guidelines, section 4.2, it should have a brief summary of the problem in larger type above the main message.
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:39:00 -0700 ----
History
Comment 1
Updated by Clinton Rogers over 2 years ago
- Status changed from Open to Review
- Assignee changed from Clinton Rogers to Adam Dingle
I propose the following:
Unable to publish¶
Shotwell cannot publish the selected items because you do not have a compatible publishing plugin enabled. To correct this, choose Edit ? Preferences and enable one or more of the publishing plugins on the Plugin tab.
Shall I do this?
Comment 2
Updated by Adam Dingle over 2 years ago
- Assignee changed from Adam Dingle to Clinton Rogers
Sounds good.
Comment 3
Updated by Clinton Rogers over 2 years ago
- Status changed from Review to 5
- Resolution set to fixed
- % Done changed from 0 to 100
Fixed in r2859
Comment 4
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:53 UTC ---
This bug was previously known as bug 3457 at http://redmine.yorba.org/show_bug.cgi?id=3457
Unknown Component Using default product and component set in Parameters Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Version: 0.10
Resolution: RESOLVED FIXED