Quote:
Originally Posted by SigilBear
NOTE: This issue has been solved.
I don't know how the container.xml error popped up in the first place, but when I was first trying to fix the problem, I created a file named container.xml or container.xhmtl in the Text files folder, which I later forgot about. I simply created a new epub and imported all my files EXCEPT that one. I no longer get an error message and, even better, there's no longer a container.xml file anywhere in my epub. 
* * * * *
|
Sure there's still a container.xml file in your epub. It's required. Sigil just doesn't let you see, create, or edit it. The one you created and ultimately eliminated was extraneous. You didn't have to go to the trouble importing all the files into a new epub. All you had to do was delete the fake container.xml file and save the epub. Sigil would have made sure the real one (the one Sigil will never let you see) was present.