After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 716712 - Picasa Web Album -> Albums
Picasa Web Album -> Albums
Status: RESOLVED FIXED
Product: shotwell
Classification: Other
Component: general
unspecified
Other All
: High normal
: ---
Assigned To: Jim Nelson
Shotwell Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-10-26 03:42 UTC by Adam Dingle
Modified: 2013-05-01 06:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Charles Lindsay 2013-11-25 21:47:03 UTC


---- Reported by adam@yorba.org 2010-10-26 08:42:00 -0700 ----

Original Redmine bug id: 2730
Original URL: http://redmine.yorba.org/issues/2730
Searchable id: yorba-bug-2730
Original author: Adam Dingle
Original description:

The list of services in the publishing dialog now includes “Picasa Web
Albumâ€. This used to be “Picasa Web Albumsâ€, but changed with changeset
[2311](http://trac.yorba.org/changeset/2311). We should change the name back
to “…Albumsâ€.



---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:40:00 -0700 ----

### History

####

#1

Updated by Jim Nelson about 3 years ago

  * **Status** changed from _Open_ to _5_
  * **Resolution** set to _fixed_
  * **% Done** set to _100_

####

#2

Updated by Charles Lindsay 7 months ago

  * **Status** changed from _5_ to _Fixed_



--- Bug imported by chaz@yorba.org 2013-11-25 21:47 UTC  ---

This bug was previously known as _bug_ 2730 at http://redmine.yorba.org/show_bug.cgi?id=2730

Unknown Component 
   Using default product and component set in Parameters 
Unknown version " in product shotwell. 
   Setting version to "!unspecified".
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.