Closed artorious83 closed 2 years ago
Thanks for the nice words but I didn't create it. Just picked it up and tried to maintain it. ☺️ Which is why I find your comment interesting. Last time I checked it was working fine in current indesign versions. Let me check again to be sure. Cheers, Mike
I am having the same problem. When you run the script it hangs when you select the PDF to be imported.
Ok, will take a look tomorrow.
Just checked - works fine for me in 14.03. @matt21218 @artorious83 : can you please run a basic test?
%appdata%\Adobe\InDesign\Version 14.0\en_US\Scripts\Scripts Panel
Hi Mike, I just tried it again and it still doesn't work. I just get spinning beach ball and it doesn't take me to the dialog box anymore. I specifically tried using one of the PDF files that had worked in the past, and for some reason it now refuses to work, which doesn't make any sense.
Matt
I am using the same version of indesign that you are using.
Just wondering whether this might be related to Mac OS... Did you run any updates in between? I could very well imagine that there were changes to access models or so. Hard to test on my side as I'm on windows. Cheers, Mike
Just wondering whether this might be related to Mac OS... Did you run any updates in between? I could very well imagine that there were changes to access models or so. Hard to test on my side as I'm on windows. Cheers, Mike
@mike-edel, I am running this on macOS, in InDesign 2021. It doesn't even initiate.
I am looking at in in ExtendScript Toolkit and trying to run it there. it immediately errors, giving me "Cannot execute script in target engine 'main'. The details of which are "Cannot execute script in target engine 'main'! (#1116) Can't start debug session." if that is helpful?
When I click okay, it takes me to line 87 of the script which is:
prefsFile = File((Folder(app.activeScript)).parent + "/MultiPageImporterPrefs2.5.txt");
Not sure if this is helpful, but there you go ;-)
Looking at this again it might be a permissions issue on Mac. The code on line 87 requests read/write file access to the config file where the last used settings are stored.
I only have Windows and I always run the script in my user profile folder so every application will have write permission even without running as admin. @cdaters where do you store and run the script - user folder or somewhere in the application folder?
I am loading it into my user profile folder. I will revisit this again soon and let you know what I discover. macOS is getting more "security" minded with everything with their latest "Big Sur" update, so I would not be surprised. I have yet to try it on my PC, that would require installing everything over there, lol and I had been in a rush that day.
@cdaters I just stumbled over a thread in the Adobe forums that might help explain this. The user pointed out that he had issues on his system and was able to narrow it down to the #target indesign
line in the script. That line normally makes the ExtendScript editor run the script inside the latest version of InDesign when debugging but is not important otherwise.
So I removed it in the latest version - can you pleas test this?
Love this script! Thank you so much for creating it! Glad I kept my ID 2017 version because it runs fine there, but for some reason it doesn't want to run in 2019. Thanks again!