Youtube, Publishing: It's possible to attempt publication of non-video content with only the Youtube plugin enabled.
Submitted by cli..@..ba.org
Assigned to cli..@..ba.org
Link to original bug (#717428)
Description
---- Reported by clinton@yorba.org 2011-02-28 13:46:00 -0800 ----
Original Redmine bug id: 3268
Original URL: http://redmine.yorba.org/issues/3268
Searchable id: yorba-bug-3268
Original author: Clinton Rogers
Original description:
The application will currently let the user press the 'Publish' button with a photograph chosen and a video-only publishing service plugin enabled.
To reproduce:
With Shotwell running, on the main collection page, highlight one or more photographs, but do not highlight any videos.
Edit->Preferences->Plugins.
On the Plugins tab, disable all services except Youtube and dismiss the Preferences box.
In the main window, click Publish and observe the results.
Notice that the application aborts immediately.
---- 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
This is related to #3253 in that it has to do with how the default publishing service finder determines the capabilities of the default publishing service.
Comment 2
Updated by Adam Dingle over 2 years ago
- Status changed from Open to Review
- Assignee changed from Anonymous to Clinton Rogers
Good catch.
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
r2689 (as part of the fix for #3253)
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:51 UTC ---
This bug was previously known as bug 3268 at http://redmine.yorba.org/show_bug.cgi?id=3268
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.9
Resolution: RESOLVED FIXED