This seems to be a bug that was introduced in the latest CC 2015.4 release. Someone complained on the site already: https://creativepro.com/topic/indesign-cc-2015-4-form-issue

I’m afraid you’ll have to use regular radio buttons.

2. I believe this is the best workflow. Why go through the hassle of moving pages, turning on the ‘do not shuffle’ option, and inviting mistakes when you can leave everything as is and the printer does the work for you.

3. You can make a tri-fold with guides and columns but since InDesign added support for multi-sized pages it’s a shame not to use it. As I said, what if you decide that the center-panel has to be an inch wider, but the right or left panel should stay the same as before. That would be a lot of work with guides. But with multi-sized pages it’s a breeze. I don’t create so much tri-folds so I don’t have a ‘standard procedure’.

I haven’t looked at the templates, but I’m going to try to guess the answers.

1. It’s probably a template for a digital book in which facing pages does not make sense.

2. Do not totally understand your question.

3. Do you have a better way to do it? What if you decide that the center panel has to be an inch wider?…

This can definitely be scripted. I’m afraid I don’t have the time now, but maybe one of the fine scripters on this site can write something for you (“Peter, Kai, Jongware, can you hear me?…”).

But this is only another indication on why you should always use styles. If you would have used consistent styles throughout the book then changing the broken font would’ve been a breeze. You just update the paragraph style with the broken font in one document, sync all the documents’ styles to this document, and everything would be fixed instantly.

But I believe it’s not your fault anyway, because if any fonts are missing then it makes sense to think that someone else created the document and not you…

Maybe you have similar situation like this: https://creativepro.com/topic/images-in-overset-text/#post-85980

Skemicle, you can use a separate loop for that, but it has to be nested in the outer document loop, and the variables has to be different.

To export individual pages is a bit more involved. So here it is:

var myFilePath;
var myFile;
var allDocs = app.documents;
var myDoc;
var myPages;
var myPage;
var myPageNum;

app.jpegExportPreferences.jpegQuality = JPEGOptionsQuality.high;
app.jpegExportPreferences.exportResolution = 200;
app.jpegExportPreferences.jpegExportRange = ExportRangeOrAllPages.EXPORT_RANGE;

for (var i = 0; i < allDocs.length; i++) {
  myDoc = allDocs[i];
  myPages = myDoc.pages;
  for (var j = 0; j < myPages.length; j++) {
      myPage = myPages[j];
      myPageNum = myPage.name;
      var myFilePath = "/Users/kcote/Desktop/TEST update/JPG/" + myDoc.name.replace(/indd$/, "") + " page " + myPageNum + ".jpg";
      var myFile = new File(myFilePath);
      app.jpegExportPreferences.pageString = myPageNum;
      myDoc.exportFile(ExportFormat.jpg, myFile, false);
      } 
  }