Extendscript Toolkit debugger fails: Can't start debug session
Not a programming problem per se, but rather a programming environment problem that I have been unable to find a solution to.
The problem relates to Adobe's Extendscript Toolkit (both 3.5 and 4), but so far I haven't been able to solve the problem, so here I am...
The error I get has appeared more or less over night. I didn't experience this problem yesterday, nor this morning. But exactly WHAT has happened is beyond me. I have removed preferences, I have uninstalled, reinstalled, created a new user, restored old preferences from Time Machine and I'm now pretty much lost for options.
Basically, nothing works in ESTK anymore. Just opening ESTK and entering alert('Hello') won't work. Neither will $.writeln(). Everything running from within ESTK seems to give the same error;
Cannot execute script in target engine 'main'
With details:
Cannot execute script in target engine 'main'!
(#1116) Can't start debug session.
Below is a screenshot taken from the new user I created to test, same problem.
The "funny" thing is that all the scripts (InDesign CS5, still hanging on to it for reasons) still work perfectly in the applications' script panels. So there is nothing wrong with the scripts (heck, they haven't changed one bit, and still refuses to run in ESTK).
As mentioned, I've tried installing the ESTK CC (version 4) as well, but the very same problem occurs there. Which leads me to think the problem lies somewhere else, but I do not know where, and why.
So, if anyone can shed any light on this issue, at all, I would be very happy. Debugging is basically the only thing ESTK is good for in my book, but now that even that functionality is gone, I don't know how to efficiently debug the scripts which is kind of hampering the workflow.
For reference, I'm running InDesign CS5 (from the old Creative Suite) on a 2008 Mac Pro with 10.11.6 (El Capitan) installed. Well aware that it's pretty out of date, but that is beside the point here.
debugging adobe extendscript toolkit
asked Nov 20 at 9:54
Bornhall
335
add a comment |
Not a programming problem per se, but rather a programming environment problem that I have been unable to find a solution to.
The problem relates to Adobe's Extendscript Toolkit (both 3.5 and 4), but so far I haven't been able to solve the problem, so here I am...
The error I get has appeared more or less over night. I didn't experience this problem yesterday, nor this morning. But exactly WHAT has happened is beyond me. I have removed preferences, I have uninstalled, reinstalled, created a new user, restored old preferences from Time Machine and I'm now pretty much lost for options.
Basically, nothing works in ESTK anymore. Just opening ESTK and entering alert('Hello') won't work. Neither will $.writeln(). Everything running from within ESTK seems to give the same error;
Cannot execute script in target engine 'main'
With details:
Cannot execute script in target engine 'main'!
(#1116) Can't start debug session.
Below is a screenshot taken from the new user I created to test, same problem.
The "funny" thing is that all the scripts (InDesign CS5, still hanging on to it for reasons) still work perfectly in the applications' script panels. So there is nothing wrong with the scripts (heck, they haven't changed one bit, and still refuses to run in ESTK).
As mentioned, I've tried installing the ESTK CC (version 4) as well, but the very same problem occurs there. Which leads me to think the problem lies somewhere else, but I do not know where, and why.
So, if anyone can shed any light on this issue, at all, I would be very happy. Debugging is basically the only thing ESTK is good for in my book, but now that even that functionality is gone, I don't know how to efficiently debug the scripts which is kind of hampering the workflow.
For reference, I'm running InDesign CS5 (from the old Creative Suite) on a 2008 Mac Pro with 10.11.6 (El Capitan) installed. Well aware that it's pretty out of date, but that is beside the point here.
debugging adobe extendscript toolkit
asked Nov 20 at 9:54
Bornhall
335
I've tried in a VM running 10.11 with only ESTK CC installed, and it gives the same error message with alert() with ESTK as target. For clarification, I'm not looking to get the alert() or $.writeln() to work, but they produce the same error as shown in the image above. So, it is mainly for showing the error, which is the same for scripts KNOWN to work in ESTK earlier.
– Bornhall
Nov 20 at 10:15
Same here. I had a few security Updates and now i've got the message. I can run scripts, but the message is annoying.
– grefel
Nov 20 at 10:35
Also getting the same problem with Photoshop CS5 when trying to use ESTK. Just doing:#target "Photoshop"#targetengine "session"...switches the engine to "session", but the error still occurs.
– Bornhall
Nov 20 at 10:40
2
posted on the adobe forum to enhance visibility forums.adobe.com/message/10761172#10761172
– grefel
Nov 20 at 10:43
1
This seems to be the case for all users and computers, regardles of versions! Setting back the computer clock helps. Probably a certificate problem.
– Hauke
Nov 20 at 13:07
add a comment |
Not a programming problem per se, but rather a programming environment problem that I have been unable to find a solution to.
The problem relates to Adobe's Extendscript Toolkit (both 3.5 and 4), but so far I haven't been able to solve the problem, so here I am...
The error I get has appeared more or less over night. I didn't experience this problem yesterday, nor this morning. But exactly WHAT has happened is beyond me. I have removed preferences, I have uninstalled, reinstalled, created a new user, restored old preferences from Time Machine and I'm now pretty much lost for options.
Basically, nothing works in ESTK anymore. Just opening ESTK and entering alert('Hello') won't work. Neither will $.writeln(). Everything running from within ESTK seems to give the same error;
Cannot execute script in target engine 'main'
With details:
Cannot execute script in target engine 'main'!
(#1116) Can't start debug session.
Below is a screenshot taken from the new user I created to test, same problem.
The "funny" thing is that all the scripts (InDesign CS5, still hanging on to it for reasons) still work perfectly in the applications' script panels. So there is nothing wrong with the scripts (heck, they haven't changed one bit, and still refuses to run in ESTK).
As mentioned, I've tried installing the ESTK CC (version 4) as well, but the very same problem occurs there. Which leads me to think the problem lies somewhere else, but I do not know where, and why.
So, if anyone can shed any light on this issue, at all, I would be very happy. Debugging is basically the only thing ESTK is good for in my book, but now that even that functionality is gone, I don't know how to efficiently debug the scripts which is kind of hampering the workflow.
For reference, I'm running InDesign CS5 (from the old Creative Suite) on a 2008 Mac Pro with 10.11.6 (El Capitan) installed. Well aware that it's pretty out of date, but that is beside the point here.
debugging adobe extendscript toolkit
asked Nov 20 at 9:54
Bornhall
335
Not a programming problem per se, but rather a programming environment problem that I have been unable to find a solution to.
The problem relates to Adobe's Extendscript Toolkit (both 3.5 and 4), but so far I haven't been able to solve the problem, so here I am...
The error I get has appeared more or less over night. I didn't experience this problem yesterday, nor this morning. But exactly WHAT has happened is beyond me. I have removed preferences, I have uninstalled, reinstalled, created a new user, restored old preferences from Time Machine and I'm now pretty much lost for options.
Basically, nothing works in ESTK anymore. Just opening ESTK and entering alert('Hello') won't work. Neither will $.writeln(). Everything running from within ESTK seems to give the same error;
Cannot execute script in target engine 'main'
With details:
Cannot execute script in target engine 'main'!
(#1116) Can't start debug session.
Below is a screenshot taken from the new user I created to test, same problem.
The "funny" thing is that all the scripts (InDesign CS5, still hanging on to it for reasons) still work perfectly in the applications' script panels. So there is nothing wrong with the scripts (heck, they haven't changed one bit, and still refuses to run in ESTK).
As mentioned, I've tried installing the ESTK CC (version 4) as well, but the very same problem occurs there. Which leads me to think the problem lies somewhere else, but I do not know where, and why.
So, if anyone can shed any light on this issue, at all, I would be very happy. Debugging is basically the only thing ESTK is good for in my book, but now that even that functionality is gone, I don't know how to efficiently debug the scripts which is kind of hampering the workflow.
For reference, I'm running InDesign CS5 (from the old Creative Suite) on a 2008 Mac Pro with 10.11.6 (El Capitan) installed. Well aware that it's pretty out of date, but that is beside the point here.
debugging adobe extendscript toolkit
debugging adobe extendscript toolkit
asked Nov 20 at 9:54
Bornhall
335
asked Nov 20 at 9:54
Bornhall
335
asked Nov 20 at 9:54
Bornhall
335
asked Nov 20 at 9:54
Bornhall
335
asked Nov 20 at 9:54
Bornhall
335
335
I've tried in a VM running 10.11 with only ESTK CC installed, and it gives the same error message with alert() with ESTK as target. For clarification, I'm not looking to get the alert() or $.writeln() to work, but they produce the same error as shown in the image above. So, it is mainly for showing the error, which is the same for scripts KNOWN to work in ESTK earlier.
– Bornhall
Nov 20 at 10:15
Same here. I had a few security Updates and now i've got the message. I can run scripts, but the message is annoying.
– grefel
Nov 20 at 10:35
Also getting the same problem with Photoshop CS5 when trying to use ESTK. Just doing:#target "Photoshop"#targetengine "session"...switches the engine to "session", but the error still occurs.
– Bornhall
Nov 20 at 10:40
2
posted on the adobe forum to enhance visibility forums.adobe.com/message/10761172#10761172
– grefel
Nov 20 at 10:43
1
This seems to be the case for all users and computers, regardles of versions! Setting back the computer clock helps. Probably a certificate problem.
– Hauke
Nov 20 at 13:07
add a comment |
I've tried in a VM running 10.11 with only ESTK CC installed, and it gives the same error message with alert() with ESTK as target. For clarification, I'm not looking to get the alert() or $.writeln() to work, but they produce the same error as shown in the image above. So, it is mainly for showing the error, which is the same for scripts KNOWN to work in ESTK earlier.
– Bornhall
Nov 20 at 10:15
Same here. I had a few security Updates and now i've got the message. I can run scripts, but the message is annoying.
– grefel
Nov 20 at 10:35
Also getting the same problem with Photoshop CS5 when trying to use ESTK. Just doing:#target "Photoshop"#targetengine "session"...switches the engine to "session", but the error still occurs.
– Bornhall
Nov 20 at 10:40
2
posted on the adobe forum to enhance visibility forums.adobe.com/message/10761172#10761172
– grefel
Nov 20 at 10:43
1
This seems to be the case for all users and computers, regardles of versions! Setting back the computer clock helps. Probably a certificate problem.
– Hauke
Nov 20 at 13:07
I've tried in a VM running 10.11 with only ESTK CC installed, and it gives the same error message with alert() with ESTK as target. For clarification, I'm not looking to get the alert() or $.writeln() to work, but they produce the same error as shown in the image above. So, it is mainly for showing the error, which is the same for scripts KNOWN to work in ESTK earlier.
– Bornhall
Nov 20 at 10:15
I've tried in a VM running 10.11 with only ESTK CC installed, and it gives the same error message with alert() with ESTK as target. For clarification, I'm not looking to get the alert() or $.writeln() to work, but they produce the same error as shown in the image above. So, it is mainly for showing the error, which is the same for scripts KNOWN to work in ESTK earlier.
– Bornhall
Nov 20 at 10:15
Same here. I had a few security Updates and now i've got the message. I can run scripts, but the message is annoying.
– grefel
Nov 20 at 10:35
Same here. I had a few security Updates and now i've got the message. I can run scripts, but the message is annoying.
– grefel
Nov 20 at 10:35
Also getting the same problem with Photoshop CS5 when trying to use ESTK. Just doing:
#target "Photoshop" #targetengine "session" ...switches the engine to "session", but the error still occurs.– Bornhall
Nov 20 at 10:40
Also getting the same problem with Photoshop CS5 when trying to use ESTK. Just doing:
#target "Photoshop" #targetengine "session" ...switches the engine to "session", but the error still occurs.– Bornhall
Nov 20 at 10:40
2
2
posted on the adobe forum to enhance visibility forums.adobe.com/message/10761172#10761172
– grefel
Nov 20 at 10:43
posted on the adobe forum to enhance visibility forums.adobe.com/message/10761172#10761172
– grefel
Nov 20 at 10:43
1
1
This seems to be the case for all users and computers, regardles of versions! Setting back the computer clock helps. Probably a certificate problem.
– Hauke
Nov 20 at 13:07
This seems to be the case for all users and computers, regardles of versions! Setting back the computer clock helps. Probably a certificate problem.
– Hauke
Nov 20 at 13:07
add a comment |
3 Answers
3
active
oldest
votes
In the above mentioned forum, Adobe has published a stable workaround!You just have to correct a setting inside the estk application:
- Open the file(Mac): “/Applications/Adobe ExtendScript Toolkit CC/ExtendScript Toolkit.app/Contents/SharedSupport/Required/cdic/11BTBackend.jsx”
- Search for the value: 604800000 (line reads bt.timeout = 604800000)
- Replace that value with 604800 and save
- Quit ExtendScript Toolkit and relaunch.
I can confirm that it works.
answered Nov 22 at 8:28
Hauke
1316
Yes, I can confirm that this fix works in ESTK 3.5 as well, so we're all good to go!
– Bornhall
Nov 22 at 9:40
add a comment |
From the adobe Forum :
"we have found a first workaround: just change your date to any date before 20-nov-2018"
https://forums.adobe.com/message/10761440#10761440
Seems like a date issue :(
answered Nov 20 at 13:34
Tristan G.
413
add a comment |
I just published a quick update about this on the Adobe Tech Blog.
For the time being, if you dismiss the dialog, you can still run your script via ESTK and step through code as usual.
Alternatively, if you really want to avoid the dialogs, and you don’t mind setting your clock back, you can sidestep the issue by setting your system clock back to November 19, 2018 or before. On most systems, changing the system time can have unintended side effects, so this isn’t recommended unless you’re really certain about it.
answered Nov 20 at 22:06
Ash Ryan Arnwine
1,2311725
As @tristan-g notes above, you should follow this thread on the Adobe forums for updates on the issue: forums.adobe.com/message/10761440
– Ash Ryan Arnwine
Nov 20 at 22:07
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53390355%2fextendscript-toolkit-debugger-fails-cant-start-debug-session%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
In the above mentioned forum, Adobe has published a stable workaround!You just have to correct a setting inside the estk application:
- Open the file(Mac): “/Applications/Adobe ExtendScript Toolkit CC/ExtendScript Toolkit.app/Contents/SharedSupport/Required/cdic/11BTBackend.jsx”
- Search for the value: 604800000 (line reads bt.timeout = 604800000)
- Replace that value with 604800 and save
- Quit ExtendScript Toolkit and relaunch.
I can confirm that it works.
answered Nov 22 at 8:28
Hauke
1316
Yes, I can confirm that this fix works in ESTK 3.5 as well, so we're all good to go!
– Bornhall
Nov 22 at 9:40
add a comment |
In the above mentioned forum, Adobe has published a stable workaround!You just have to correct a setting inside the estk application:
- Open the file(Mac): “/Applications/Adobe ExtendScript Toolkit CC/ExtendScript Toolkit.app/Contents/SharedSupport/Required/cdic/11BTBackend.jsx”
- Search for the value: 604800000 (line reads bt.timeout = 604800000)
- Replace that value with 604800 and save
- Quit ExtendScript Toolkit and relaunch.
I can confirm that it works.
answered Nov 22 at 8:28
Hauke
1316
Yes, I can confirm that this fix works in ESTK 3.5 as well, so we're all good to go!
– Bornhall
Nov 22 at 9:40
add a comment |
In the above mentioned forum, Adobe has published a stable workaround!You just have to correct a setting inside the estk application:
- Open the file(Mac): “/Applications/Adobe ExtendScript Toolkit CC/ExtendScript Toolkit.app/Contents/SharedSupport/Required/cdic/11BTBackend.jsx”
- Search for the value: 604800000 (line reads bt.timeout = 604800000)
- Replace that value with 604800 and save
- Quit ExtendScript Toolkit and relaunch.
I can confirm that it works.
answered Nov 22 at 8:28
Hauke
1316
In the above mentioned forum, Adobe has published a stable workaround!You just have to correct a setting inside the estk application:
- Open the file(Mac): “/Applications/Adobe ExtendScript Toolkit CC/ExtendScript Toolkit.app/Contents/SharedSupport/Required/cdic/11BTBackend.jsx”
- Search for the value: 604800000 (line reads bt.timeout = 604800000)
- Replace that value with 604800 and save
- Quit ExtendScript Toolkit and relaunch.
I can confirm that it works.
answered Nov 22 at 8:28
Hauke
1316
answered Nov 22 at 8:28
Hauke
1316
answered Nov 22 at 8:28
Hauke
1316
answered Nov 22 at 8:28
Hauke
1316
1316
Yes, I can confirm that this fix works in ESTK 3.5 as well, so we're all good to go!
– Bornhall
Nov 22 at 9:40
add a comment |
Yes, I can confirm that this fix works in ESTK 3.5 as well, so we're all good to go!
– Bornhall
Nov 22 at 9:40
Yes, I can confirm that this fix works in ESTK 3.5 as well, so we're all good to go!
– Bornhall
Nov 22 at 9:40
Yes, I can confirm that this fix works in ESTK 3.5 as well, so we're all good to go!
– Bornhall
Nov 22 at 9:40
add a comment |
From the adobe Forum :
"we have found a first workaround: just change your date to any date before 20-nov-2018"
https://forums.adobe.com/message/10761440#10761440
Seems like a date issue :(
answered Nov 20 at 13:34
Tristan G.
413
add a comment |
From the adobe Forum :
"we have found a first workaround: just change your date to any date before 20-nov-2018"
https://forums.adobe.com/message/10761440#10761440
Seems like a date issue :(
answered Nov 20 at 13:34
Tristan G.
413
add a comment |
From the adobe Forum :
"we have found a first workaround: just change your date to any date before 20-nov-2018"
https://forums.adobe.com/message/10761440#10761440
Seems like a date issue :(
answered Nov 20 at 13:34
Tristan G.
413
From the adobe Forum :
"we have found a first workaround: just change your date to any date before 20-nov-2018"
https://forums.adobe.com/message/10761440#10761440
Seems like a date issue :(
answered Nov 20 at 13:34
Tristan G.
413
answered Nov 20 at 13:34
Tristan G.
413
answered Nov 20 at 13:34
Tristan G.
413
answered Nov 20 at 13:34
Tristan G.
413
413
add a comment |
add a comment |
I just published a quick update about this on the Adobe Tech Blog.
For the time being, if you dismiss the dialog, you can still run your script via ESTK and step through code as usual.
Alternatively, if you really want to avoid the dialogs, and you don’t mind setting your clock back, you can sidestep the issue by setting your system clock back to November 19, 2018 or before. On most systems, changing the system time can have unintended side effects, so this isn’t recommended unless you’re really certain about it.
answered Nov 20 at 22:06
Ash Ryan Arnwine
1,2311725
As @tristan-g notes above, you should follow this thread on the Adobe forums for updates on the issue: forums.adobe.com/message/10761440
– Ash Ryan Arnwine
Nov 20 at 22:07
add a comment |
I just published a quick update about this on the Adobe Tech Blog.
For the time being, if you dismiss the dialog, you can still run your script via ESTK and step through code as usual.
Alternatively, if you really want to avoid the dialogs, and you don’t mind setting your clock back, you can sidestep the issue by setting your system clock back to November 19, 2018 or before. On most systems, changing the system time can have unintended side effects, so this isn’t recommended unless you’re really certain about it.
answered Nov 20 at 22:06
Ash Ryan Arnwine
1,2311725
As @tristan-g notes above, you should follow this thread on the Adobe forums for updates on the issue: forums.adobe.com/message/10761440
– Ash Ryan Arnwine
Nov 20 at 22:07
add a comment |
I just published a quick update about this on the Adobe Tech Blog.
For the time being, if you dismiss the dialog, you can still run your script via ESTK and step through code as usual.
Alternatively, if you really want to avoid the dialogs, and you don’t mind setting your clock back, you can sidestep the issue by setting your system clock back to November 19, 2018 or before. On most systems, changing the system time can have unintended side effects, so this isn’t recommended unless you’re really certain about it.
answered Nov 20 at 22:06
Ash Ryan Arnwine
1,2311725
I just published a quick update about this on the Adobe Tech Blog.
For the time being, if you dismiss the dialog, you can still run your script via ESTK and step through code as usual.
Alternatively, if you really want to avoid the dialogs, and you don’t mind setting your clock back, you can sidestep the issue by setting your system clock back to November 19, 2018 or before. On most systems, changing the system time can have unintended side effects, so this isn’t recommended unless you’re really certain about it.
answered Nov 20 at 22:06
Ash Ryan Arnwine
1,2311725
answered Nov 20 at 22:06
Ash Ryan Arnwine
1,2311725
answered Nov 20 at 22:06
Ash Ryan Arnwine
1,2311725
answered Nov 20 at 22:06
Ash Ryan Arnwine
1,2311725
1,2311725
As @tristan-g notes above, you should follow this thread on the Adobe forums for updates on the issue: forums.adobe.com/message/10761440
– Ash Ryan Arnwine
Nov 20 at 22:07
add a comment |
As @tristan-g notes above, you should follow this thread on the Adobe forums for updates on the issue: forums.adobe.com/message/10761440
– Ash Ryan Arnwine
Nov 20 at 22:07
As @tristan-g notes above, you should follow this thread on the Adobe forums for updates on the issue: forums.adobe.com/message/10761440
– Ash Ryan Arnwine
Nov 20 at 22:07
As @tristan-g notes above, you should follow this thread on the Adobe forums for updates on the issue: forums.adobe.com/message/10761440
– Ash Ryan Arnwine
Nov 20 at 22:07
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53390355%2fextendscript-toolkit-debugger-fails-cant-start-debug-session%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I've tried in a VM running 10.11 with only ESTK CC installed, and it gives the same error message with alert() with ESTK as target. For clarification, I'm not looking to get the alert() or $.writeln() to work, but they produce the same error as shown in the image above. So, it is mainly for showing the error, which is the same for scripts KNOWN to work in ESTK earlier.
– Bornhall
Nov 20 at 10:15
Same here. I had a few security Updates and now i've got the message. I can run scripts, but the message is annoying.
– grefel
Nov 20 at 10:35
Also getting the same problem with Photoshop CS5 when trying to use ESTK. Just doing:
#target "Photoshop"#targetengine "session"...switches the engine to "session", but the error still occurs.– Bornhall
Nov 20 at 10:40
2
posted on the adobe forum to enhance visibility forums.adobe.com/message/10761172#10761172
– grefel
Nov 20 at 10:43
1
This seems to be the case for all users and computers, regardles of versions! Setting back the computer clock helps. Probably a certificate problem.
– Hauke
Nov 20 at 13:07