Description of problem: I uploaded a Zip file of a book that had a main XML file named something other than Publican's default. Even though this file was specified with the mainfile: parameter in the Publican.cfg file, the Import Tool still asked me to specify it manually (ie, it did not default to the correct mainfile). Since this wasn't a book I created, I had to refer to the Publican.cfg myself and select the file manually. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create a book with Publican and rename its main file 2. Specify the new main file in the Publican.cfg file 3. Zip up the book and upload it with the PressGang Import Tool Actual results: PIT allows you to specify the mainfile, but does not default to the file specified in the Publican.cfg. Expected results: PIT defaults to the specified mainfile. It's still nice to be able to override that though. Additional info:
Actually, it ignores default main files too!
Created attachment 874205 [details] Alternate mainfile test
Fixed in 201403141239
Using the attached sample doesn't select the main file and instead adds a blank option that will allow you to continue. When clicking the "Start Import" it just appears to hang.
Fixed in 201403211230 The included sample sets mainfile to filename.xml, whereas it should only be set to filename (see http://jfearn.fedorapeople.org/en-US/Publican/2.6/html/Release_Notes/index.html). There is now a check for incorrectly adding the xml extension though.
Attempting to use a mainfile that doesn't exist results in the same behaviour as above. ie: mainfile: Blah or mainfile:
Created attachment 881558 [details] Incorrect main file
Fixed in 201404020907 When the mainfile option point to a file that does not exist, it is ignored.
Verified