Flight Crew Error

[Moonraker]

Since Sigil v1.0.0 I get the following flight crew error when I add an additional page:

"Invalid Book Path Provided"

I copy the correct DOCTYPE header from another page which I have always done.

When I check with Sigil's "Well-formed epub check"

I do not get the error.

[KevinH]

That error message means the plugin itself did not supply the proper path with its validation message it was reporting. That message does not mean the book necessarily has an issue, it means the plugin itself has an issue.

The Well-formed check in Sigil only checks for broken xhtml. It is not like running FlightCrew or the epubcheck plugins.

Please attach a screen capture of the Validation Report error message so we can see exactly what that message is related to.

[Moonraker]

Thank you KevinH, I guessed that was the case because I know FlightCrew has not been updated for a long time. I like to use it because it does find unused images and pages which I prefer to delete in order to keep the epub smaller in size.

For your info I am attaching screenshot:

[Turtle91]

Originally Posted by Moonraker

... I like to use it because it does find unused images and pages which I prefer to delete in order to keep the epub smaller in size.

You can perform the same function by running a report (Tools/Reports or Ctr+Shift+R) select Image Files in the list on the left. The right pane lists all kinds of info about all your images: dimensions, file size, and how many times it is used in the epub. You can get similar info for the different files by selecting the different reports on the left.

I use it regularly to get rid of unused images by sorting by "Times Used" (click on the column header) then multi-selecting all the images with a zero....then hit the delete key.

You can also double click on the image in the list and it will take you to the location that uses that file.

[JSWolf]

Originally Posted by Moonraker

Thank you KevinH, I guessed that was the case because I know FlightCrew has not been updated for a long time. I like to use it because it does find unused images and pages which I prefer to delete in order to keep the epub smaller in size.

For your info I am attaching screenshot:

epubcheck also finds unused images and pages. I suggest you give the epubcheck plugin a try and see how you get on. epubcheck does find more errors becuase it's maintained. It's the standard used tor checking ePub for errors.

[Vroni]

Originally Posted by Turtle91

You can perform the same function by running a report (Tools/Reports or Ctr+Shift+R) select Image Files in the list on the left. The right pane lists all kinds of info about all your images: dimensions, file size, and how many times it is used in the epub. You can get similar info for the different files by selecting the different reports on the left.

Thats true for images, but FC finds a little bit more...

[JSWolf]

Originally Posted by Vroni

Thats true for images, but FC finds a little bit more...

And epubcheck finds even more.

[Turtle91]

Originally Posted by Vroni

Thats true for images, but FC finds a little bit more...

Originally Posted by JSWolf

And epubcheck finds even more.

True, but the stated purpose for the OP was:

Originally Posted by Moonraker

... I like to use it because it does find unused images and pages which I prefer to delete in order to keep the epub smaller in size...

Reports does that very well...AND...allows you to DO something with the info, not just get a list of problems.

[KevinH]

Please no fc vs epubcheck religious wars. They are only in competition for epub2 and even then they do check different things. Flightcrew has been maintained (this year we added code to prevent malicious epubs from taking over your system) but all in all the epub2 spec has not changed and there really is not anything that fc needs to change.

epubcheck needs to keep updating as the epub3 spec is constantly in flux.

[KevinH]

That is an actual error. It basically is saying that your epub has a link to a resource that is not listed in the manifest itself. Could the html page you added have had a link to an external resource?

It also indicates that fc needs include either the name of the opf file or better yet a name of the file that has the strange link to it.

I will look into fixing that.

Kevin

Originally Posted by Moonraker

Thank you KevinH, I guessed that was the case because I know FlightCrew has not been updated for a long time. I like to use it because it does find unused images and pages which I prefer to delete in order to keep the epub smaller in size.

For your info I am attaching screenshot:

[JSWolf]

Originally Posted by Turtle91

True, but the stated purpose for the OP was:



Reports does that very well...AND...allows you to DO something with the info, not just get a list of problems.

I know what the OP wants to do. epubcheck finds the same things as well.

[JSWolf]

Originally Posted by KevinH

Please no fc vs epubcheck religious wars. They are only in competition for epub2 and even then they do check different things. Flightcrew has been maintained (this year we added code to prevent malicious epubs from taking over your system) but all in all the epub2 spec has not changed and there really is not anything that fc needs to change.

epubcheck needs to keep updating as the epub3 spec is constantly in flux.

So just to be clear, FC doesn't work well with ePub3 and eoubcheck should be used. Is this correct?

[DiapDealer]

Originally Posted by JSWolf

So just to be clear, FC doesn't work well with ePub3 and eoubcheck should be used. Is this correct?

Moderator Notice
Just to be even more perfectly clear: drop this right now, Jon. Further irrelevant comments from you about epubcheck will be deleted from here on out.

[KevinH]

Okay, that is an actual error in the epub.
You have either an href attribute or a src attribute or a css url that points to something that is not part of the epub manifest.

Unfortunately the *** Invalid Book Path Provided *** message is overwriting the exact path that does not seem to exist. So either the missing resource path should have been part of the error message itself, or we will need to change Sigil to not step on flightcrew filepaths that it does not recognize as these may be the exact string to help you find where the error is actually located.

I will fix this in Sigil right now.

Sorry about that.

Thank you for your bug report!

KevinH

ps. This is now fixed in master.

Originally Posted by Moonraker

Thank you KevinH, I guessed that was the case because I know FlightCrew has not been updated for a long time. I like to use it because it does find unused images and pages which I prefer to delete in order to keep the epub smaller in size.

For your info I am attaching screenshot:

[odamizu]

Did FlightCrew 0.9.3 ever get released?

On the GitHub release page, a tag or something in prep for 0.9.3 is shown dated July 21, 2019, but I can't find the actual download link.

The Latest Release shown is 0.9.2, released in Dec 20, 2016.

Thank you