Piwigo publisher doesn't persist user settings
Submitted by Jim Nelson
Assigned to Lucas Beeler
Link to original bug (#718074)
Description
---- Reported by jim@yorba.org 2011-08-12 05:33:00 -0700 ----
Original Redmine bug id: 3972
Original URL: http://redmine.yorba.org/issues/3972
Searchable id: yorba-bug-3972
Original author: Jim Nelson
Original description:
When I attempt to publish to http://demo.piwigo.com, my user settings (URL, username, etc.) are not persisted.
I'm having trouble publishing to Piwigo, but the code looks like the settings should be saved when I press the Login button and the session is authenticated, and the Piwigo error is happening after that.
Related issues:
- related to shotwell - Feature #4006: Save the publish login settings (Fixed)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:39:00 -0700 ----
History
Comment 1
Updated by Jonas Bushart over 2 years ago
No error if I upload to my piwigo site.
But where in the code is the real save function which writes the data to gsetting or gconf?
The set_persistent_* functions in PiwigoPublish.vala are using host.set_config_string. host is Spit.Publishing.PluginHost which is only a interface without real code and it inherits from Spit.HostInterface which has also no real code. The set_config_string method is defined in the Spit.HostInterface interface. Where is the implementation of those abstract methods?
The only implementation I found is Plugins.StandardHostInterface.
Comment 2
Updated by Lucas Beeler over 2 years ago
- Assignee set to Lucas Beeler
Comment 3
Updated by Lucas Beeler over 2 years ago
- Status changed from Open to 5
- Resolution set to fixed
Fixed in 340a84c9
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:55 UTC ---
This bug was previously known as bug 3972 at http://redmine.yorba.org/show_bug.cgi?id=3972
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.11
Resolution: RESOLVED FIXED