Does anyone have anything to say about this?
Besides not being able to open a file from explorer, Drag and drop into InDesign also doesnt work!
This is driving me crazy!
If anyone has some tips for me I would appreciate it
Ok, I figured this out! - But problem is not 100% solved... here goes:
The thing that was preventing explorer to interact with InDesign is the fact that I had InDesign running as Administrator!
When I ran InDesign regularly, everything behaved the way it was supposed to.
However, the problem is....
There is a reason why I had InDesign running as Administrator, and that is as follows:
(You can see the thread to the following issue here)
I script InDesign using Extendscript toolkit
Scripts are mainly stored in the InDesign folder which is in the Program Files folder
Therefore script files can't be edited in the normal fashion, and hence, extendscript will not allow to save the files there!
So, extendscript has to be run as Admin.
If extendscript is run as Admin but InDesign is not, Extendscript will not allow to run a script through it to InDesign!
So, we start InDesign as Admin also
But now, we have the problem with File explorer as mentioned above!!!
What am I supposed to do!??
The truth is, this seems to have changed now to pertain more to the scripting forum...
Any suggestions would be appreciated!
Does ID launch in the admin account and let you open from the File menu?
I am using the admin account
I open ID in that account - as Administrator
Open file from within ID works
Place from within ID works
Only interaction with explorer is broken
My recollection is that file associations in Windows are not user-specific, but it wouldn't hurt to check to see what is associated with .indd in the admin account.
Thanks Peter, but my account is the admin account
And .indd files are associated with InDesign
Then I think the only thing left is to reinstall.
Are you saying that you don't think the problem is that I suggested above?
If you run ID as admin (right click - run as administrator) you are able to drag into ID, and open files from explorer?
Please let me know
I run full time in the Administrator account on my two Win7 machines and have never had a problem double-clicking a file to open in nearly fifteen years that I've used the program. I don't drag and drop, so I can't say for sure if that works.
Hi Peter, thank you
But I just want to clarify - there is a difference between:
- running InDesign in an administrator account
- running InDesign as Administrator (i.e., right click on indesign, choose "run as administrator")
I understand that you've been doing #1 for many years, but have you ever tried #2?
In my situation also #1 works perfectly, while #2 does not.
I've never had a reason to do #2 with ID -- if I need admin rights I use an account that has them on my own machines. Is there a reason your account is not part of the administrators group? Or are you saying it is, but that's not sufficient to make ExtendScript work?
The latter is true, it is only because of extendscript
My account is the administrator account, and is in the administrator group (triple checked in "Computer Management" Window)
But seemingly, editing a file within the "Program Files" folder needs 'higher' authority, or at least another confirmation...
Therefore, the only way around editing a script which resides in the "Program Files" folder, is to run extendscript as admin, which in turn forces us to run ID as admin, which in turn causes this explorer issue!
Unless I have some misunderstanding here, this is the circumstance.
How about moving the script to the user profile?
The script location is:
C:\Program Files\Adobe\Adobe InDesign CC 2015\Scripts\Scripts Panel\
Do you mean to move it somewhere else?
It only needs to be there if it has to be accessible to ALL users. Any user can put scripts into their own Scripts Panel folder at C:\Users\<USER>\AppData\Roaming\Adobe\InDesign\<Version #>\<Language>\Scripts\Scripts Panel\
I did not know that! Sounds interesting!
I will try it out soon and post back
Reporting back.... this solution works perfectly!
Thank you very much!
In short, the main thing is that we dont want to have to run InDesign or Extendscript as Administrator
The way to get around having to do so is by using the user-level scripts folder rather than the application-level scripts folder
Thanks again Peter
All the best