Error message is still emitted if metadata has no artist (which shouldn't happen for artist query)
E: 17:27:06 Album Artist Website: u'2451caed-5d09-456f-b640-5880b6060a64': MusicBrainz artist xml result not in correct format - {'attribs': {}, 'text': u'', 'children': {u'metadata': [{'attribs': {}, 'text': u'', 'children': {u'artist': [{'attribs': {u'type': u'Group', u'id': u'2451caed-5d09-456f-b640-5880b6060a64'}, 'text': u'', 'children': {u'name': [{'attribs': {}, 'text': u'Sir Frankie Crisp', 'children': {}}], u'sort_name': [{'attribs': {}, 'text': u'Sir Frankie Crisp', 'children': {}}]}}]}}]}}
Traceback (most recent call last):
File "picard\webservice.pyo", line 285, in _process_reply
File "C:\Program Files (x86)\MusicBrainz Picard\plugins\albumartist_website.py", line 95, in website_process
log.debug("%s: %r: Artist Official Homepages = %s", PLUGIN_NAME, artistId, url)
NameError: global name 'url' is not defined
- modify set_statusbar_message(): drop hacky %s replacement, it shouldn't be needed anyway
- add named arguments echo and translate to it, to cover all needs
- rewrite translatable strings to use named place holders
- fix up some messages, add plural forms if needed
http://tickets.musicbrainz.org/browse/PICARD-597
Since there is no PluginPriority on previous Picard versions, this plugin will
raise an exception, better catch it and emit a warning.
Sophist said:
"It will work in most cases at normal priority, but any other plugins that run before it will get the old performers rather than the standardized performers.
Recordings don't support sub-second time precision, so the
track.metadata.length used for the two Add...AsRelease classes will
cause an error on /recording/create's "length" field.
track.metadata["~length"] contains the time converted to mm:ss format
and will not cause the error on /recording/create, so this commit
changes AddFileAsRecording to use that.
Adds a plugin to get the artist homepage MB relationship and insert into
website (ID3 WOAR tag).
Note: I used this plugin as a trial for using a Picard xml module to
handle MB WS2 xml response. See PICARD-581.
It's been almost 3 years since they were moved to the old/ folder, and
apparently they've not been needed enough by anyone to get an update
to current plugin API. If ever they're deemed useful again, they can
be pulled back via Git and updated.
