MobileRead Forums - View Single Post - Sigil 1.8 will only run in a specific folder

Domenick · 11-01-2021, 05:03 PM

I believe I have found the issue! All along I have telling myself, "It's got to be something simple--something basic."

First I checked my file permissions and verified Full Control up and down the folder tree.
Then I did as you suggested.

Created a test folder at every folder level up and down the folder tree and copied the same known working files into them all. The test folders worked in every case, even in the problematic folder.

To me, this narrowed the issue to the files in question, the one CSS and the one HTML.

The CSS file in the folder in which Sigil did not work,
C:\venezia\Personal\Fiction\Novels\LM\LM.02.Minido ka.Legacy\03.Compiled.Book\DOCX.to.HTML.EPUB.Conve rsion.ML\Amazon.KDP.Format\,
was set to read-only.

The working CSS file was NOT set to read-only.

Sigil generated the same, familiar errors with the ready-only CSS file loaded, but not with the read/write CSS file loaded.

All of Sigil's failure modes can be repeated with a read-only CSS file. Even the "poof" crash if the CSS file is loaded before the HTML. I tested this on other novels' manuscripts and can replicate and fix the failure at will in other subfolder trees.

I only ran into this issue because I was going back to create Edition 2 of existing manuscripts. I'll have to keep this in mind as I commonly set my files to read-only after publishing a manuscript.

If this truly is the issue, I am surprised I am the only report of this behavior.

Thank you!
Thank you for your patience, effort, and time spent tracking this down. I'll be needing Sigil sometime this month to publish another manuscript.

11-01-2021, 05:03 PM	#30
Domenick Member Posts: 16 Karma: 10 Join Date: Apr 2020 Device: none	I believe I have found the issue! All along I have telling myself, "It's got to be something simple--something basic." First I checked my file permissions and verified Full Control up and down the folder tree. Then I did as you suggested. Created a test folder at every folder level up and down the folder tree and copied the same known working files into them all. The test folders worked in every case, even in the problematic folder. To me, this narrowed the issue to the files in question, the one CSS and the one HTML. The CSS file in the folder in which Sigil did not work, C:\venezia\Personal\Fiction\Novels\LM\LM.02.Minido ka.Legacy\03.Compiled.Book\DOCX.to.HTML.EPUB.Conve rsion.ML\Amazon.KDP.Format\, was set to read-only. The working CSS file was NOT set to read-only. Sigil generated the same, familiar errors with the ready-only CSS file loaded, but not with the read/write CSS file loaded. All of Sigil's failure modes can be repeated with a read-only CSS file. Even the "poof" crash if the CSS file is loaded before the HTML. I tested this on other novels' manuscripts and can replicate and fix the failure at will in other subfolder trees. I only ran into this issue because I was going back to create Edition 2 of existing manuscripts. I'll have to keep this in mind as I commonly set my files to read-only after publishing a manuscript. If this truly is the issue, I am surprised I am the only report of this behavior. Thank you! Thank you for your patience, effort, and time spent tracking this down. I'll be needing Sigil sometime this month to publish another manuscript.