The default temp folder is the default <SIGIL_DEFAULT_TEMP_HOME>. On a hunch I looked in <user>/AppData/Local/Temp and found a Sigil-xxxxxx folder.
There is also the expected <user>/AppData/Local/sigil-ebook folder.
Thinking perhaps a computer shutdown/restart cycle might help:
I uninstalled the program.
Deleted both <user>/AppData/Local/sigil-ebook and all <user>/AppData/Local/Temp/Sigil-xxxxxx.
I shutdown (not restart) then started the computer.
Invoked Sigil and:
"Add Existing Files" starts in Sigil's Program Files dierctory.
The HTML file from the NEW manuscript's folder loads, as does the CSS file and the two JPGs (author photo and cover photo).
For grins I assigned the cover photo, and the author photo incorporates correctly.
"Save as" opens in my profile folder, shows the previous "may need to close" message, identical details, and closes.
Once again, invoked Sigil and:
"Add Existing Files" starts in Sigil's Program Files dierctory.
The HTML file from the PREVIOUS manuscript's folder loads, as does the CSS file and the two JPGs (author photo and cover photo).
For grins again, I assigned the cover photo, and the author photo incorporates correctly.
"Save as" opens in my profile folder. Moving into the PREVIOUS manuscript's folder correctly saves "untitled.epub."
I own the folders in question and run with Admin privileges.
Despite all of this fussing and farting about, Sigil is still passionately in love with that one folder.
I am at a loss. Sigil worked perfectly for 5 e-books now in the Kindle store and one just about ready to go, then suddenly version 1.7 began showing this behavior which continued into version 1.8.
|