Project

General

Profile

Feature #115

Make LyricWiki errors more descriptive

Added by Artem S. Tashkinov almost 12 years ago. Updated almost 12 years ago.

Status:
Closed
Priority:
Minor
Assignee:
-
Category:
plugins/lyricwiki
Target version:
3.3
Start date:
May 27, 2012
Due date:
% Done:

100%

Estimated time:
Affects version:
3.2.3

Description

When you build audacious-plugins without Neon support, LyricWiki stops working but doesn't show any error messages.

Either
1) Don't allow building LyricWiki without libneon
or
2) LyricWiki should always show an error message "LyricWiki requires Neon support built-in" (in case neon support is not available)

History

#1 Updated by Ariadne Conill almost 12 years ago

not true, the lyricwiki plugin depends on any VFS provider which provides an http URI scheme. if you were to provide an alternative http plugin, it would work.

lyricwiki plugin does not use libneon directly.

#2 Updated by Artem S. Tashkinov almost 12 years ago

At least is it possible to update LyricWiki plugin so that it spitted an error saying no HTTP providers are compiled in, thus it cannot fetch remote data?

#3 Updated by John Lindgren almost 12 years ago

  • Tracker changed from Bug to Feature
  • Subject changed from LyricWiki doesn't work without Neon to Make LyricWiki errors more descriptive
  • Category set to plugins/lyricwiki

#4 Updated by John Lindgren almost 12 years ago

Artem S. Tashkinov wrote:

At least is it possible to update LyricWiki plugin so that it spitted an error saying no HTTP providers are compiled in, thus it cannot fetch remote data?

No, such details are hidden from plugins. All LyricWiki knows is whether vfs_fopen() succeeded or failed.

#5 Updated by John Lindgren almost 12 years ago

  • Status changed from New to Closed
  • Target version set to 3.3
  • % Done changed from 0 to 100

Better error reporting has been implemented in 3.3-devel.

Also available in: Atom PDF