I'm so fortunite to have my Indesign update to the 2020 version today.
It's nice to know that this new version can't see the multipage importer script.
Does anyone know why this version of Indesign can't see this script?
Is it possible need newer version of the multipage importer script?
Is there a newer version of the multipage importer script?
Thanks in advance.
Are you referring to the Place Multiple PDF script that has been included as a sample script with the last several versions of InDesign? Or are you talking about a third party script? If it is a third party script then it will need to be updated to be compatible with 2020. In this case check with the developers website for a compatible update.
How did you install the script file?
What's your operating system?
When in doubt where to store the script file invoke the Scripts panel from InDesign.
Select the User folder inside the Scripts panel. Do command Show in Finder or Show in Explorer.
Store your script file in that folder.
Go back to your Scripts panel in InDesign.
The script file should be visible in the User folder of the panel.
( ACP )
do you refer to the MultiPageImporter script initially developed by Scott Zanelli and that was updated over the years by different developers?
A quick search on the web reveals that recent versions can be found here:
Most current version is 2.6.2 maintained and released by Mike Edel.
Thank you, Mike!
Did not test Mike's version yet, but my 2.5.1 version of the script, adapted by Jim Birkenseer, is still working with InDesign 2020 on Windows 10.
Had one bug with 2.5.1 when placing a 40 pages PDF with page size of 315 x 470 mm.
Pages were done in Letter size, but I could correct that after the PDF pages were placed by selecting all the pages with the Page Tool ( Select All keyboard shortcut ) and then resize to my format 315 x 470 mm without any issues.
Sure, I will test Mike Edel's 2.6.2 version as well.
Now the question is:
What version of the script are you trying to use?
On what operating system?
( ACP )
found a possible bug with the script!
All tests done with InDesign 2020 version 220.127.116.11 on Windows 10.
Script file was installed in the Scripts Panel under the User folder.
First the symptom of the bug:
A double-click to the installed and visible script file in the Scripts Panel did exactly nothing.
No dialog for selecting a PDF is coming up. All the same with a right-click and doing the execute menu command.
Now the solution:
Open the jsx file in e.g. ExtendScript Toolkit app or a text editor that is able to read and write pure text.
Go to the line where the script code is saying:
Make InDesign ignore that line of code. To do that you can remove the whole line or you can make it a comment like that:
// #target indesign;
Save the script file with a new name and Text-Only like this:
FWIW: The code line #target indesign is not needed if you are executing the script from your InDesign Scripts Panel.
If the script file is installed there InDesign does always know that InDesign itself is the target of execution.
Hope this helped!
And now have fun with the MultiPageImporter-EDITED.jsx file.
( ACP )
Does that line make *any* script stop working?
in this case I think yes. Don't ask me why. Tested this with and without the line yesterday to the effect that the dialog came up where you are able to select a PDF, every time the line was commented or removed. Have no real explanation right now.
( ACP )
Here a screenshot from my German InDesign 2020 on Windows after I selected a 40 pages PDF showing the main dialog:
Note: This dialog is showing "Crop to: Media" that I selected after the first successful run of the script.
That's not the default. The script is memorizing my selection in the dialog in a file that will automatically be created: MultiPageImporterPrefs2.5.txt. Do not rename this file if you want to use the old settings.
( ACP )
after some extensive tests I think that issue is the following:
If InDesign CC 2020 is running along with a different version of InDesign like CC 2019 the target statement:
#target indesign will not work as expected with InDesign CC 2020. Nothing will be executed. If I run the same script with the same target statement from InDesign CC 2019 while InDesign CC 2020 is also running, the script code will be executed.
Must be a bug with InDesign CC 2020 version 18.104.22.168.
To prevent this bug, one could comment out the target statement.
Or one could use a target statement specific to InDesign CC 2020 like that:
If no other version of InDesign is running along with CC 2020 the statement #target indesign will work.
All tests done on Windows 10. Cannot tell if this bug is also on Mac OS X.
All test scripts were stored either in the User folder or in the Application folder of InDesign's Scripts Panel.
( ACP )
Hi @Laubender, I just stumbled over this thread when searching for an unrelated MultiPageImporter issue somebody reported on GitHub. I would generally recommend raising an issue on GitHub as it's near impossible for me to track posts such as yours down. That at least gives you a better chance of having it fixed. 😉
Other than that I just wanted to say that I have never come across any issue with the #target indesign entry despite frequently having multiple versions of ID installed myself. This is also kind of hinted at by the documentation:
If a specifier does not supply specific version and locale information, the framework tries to find the most appropriate available installation. It tries to match to available applications in this order: Peer applications (from the same suite) Applications with the highest available version number Applications that are currently running Applications that match the current locale Applications for any locale
But as far as I remember the #target code is really only useful when debugging the script in the extendscript editor. So let me go ahead and remove that in the "official version".
"I just wanted to say that I have never come across any issue with the #target indesign entry"
first let me thank you very much for going forward with that fantastic script adding features, fixing the bugs.
I was very surprised to see the issue with the #target statement. Never had this before. And I don't know if it is still an issue with your 2.6.3 version of the script. Have to do more tests running 2.6.3 when two or more versions of InDesign running side by side. Removing the #target statement will do no harm, because the script is always started from InDesign's Scripts panel.
( ACP )
You are very welcome.
I took it over by necessity: my designer colleagues ran into a (rather obscure) bug and there was no maintainer. It was rather critical for us at that time and I had done some Adobe scripting before - so I tracked the issue down and fixed it.
These days I'm not even sure how many of my colleagues still use it to be honest. But I try to keep it in a working state. There have been surprisingly few issues so far related to InDesign version updates - luckily those aspects of the scripting interface seem to stay fairly stable.
I just read another thread on the #target code and one point in there was that this may depend on the windows registry entries for the respective application being correct. If those entries are broken there may be difficulties finding the correct application. But you are right, the script itself doesn't actually need that code.
Mike said: "… I just read another thread on the #target code and one point in there was that this may depend on the windows registry entries for the respective application being correct. If those entries are broken there may be difficulties finding the correct application. …"
Aha! This is a very interesting point of view. Thank you very much!
Well, it could be that I will not be able to reproduce that bug, because of all the updates of InDesign and CC Cleaner actions, Windows updates and so forth…
( ACP )
It's not working with my InDesign CC 2021. Will there be an update that's compatible? I love it!
It works. The secret is to make sure you download the entire folder - not just the script itself. It needs to create a file within that folder when it runs. No folder and it will fail. Put the whole folder inside the ID Scripts panel folder. Done. Hope that helps someone.
what's your version of the script?
And what's the version of your operating system?
( ACP )
I see no issue with MultiPageImporter version 2.6.2 and my German InDesign 2021 version 22.214.171.124 on Windows 10.
Just tested it. Can you show a screenshot of an error message? Did you try the script on a PDF that you exported from InDesign?
( ACP )