View Single Post
Old Today, 08:31 AM   #2
DiapDealer
Grand Sorcerer
DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.DiapDealer ought to be getting tired of karma fortunes by now.
 
DiapDealer's Avatar
 
Posts: 29,952
Karma: 212736643
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
In almost all cases, that error is a problem with the plugin. The plugin is failing before its results have successfully been reported to Sigil. I won't rule out a problem with Sigil, but it's more likely your plugin updated and behavior changed. Remember when others were having problems with epubcheck when it was trying to update to a mystery version, yet you were reporting no issues?

The epub errors being reported in the plugin runner window are that which were provided by python as a result of the plugin run. The "Success" message is simply that the plugin returned no error code. That does not mean the errors to report back to Sigil were not malformed in some way.

Last edited by DiapDealer; Today at 08:35 AM.
DiapDealer is offline   Reply With Quote