Help! Script Editor stopped opening old scripts on Yosemite 10.10.3!!!

Scripting Forums AppleScript | Mac OS X
#1

Since I updated to 10.10.3, Script Editor (from Apple) will no longer open any of the hundreds of old AppleScripts I have on my computer. It seems like it “tries” to open them - but only blinks a window for a fraction of a second, then closes it.

The scripts never appear in the “Recents” submenu. I can still create new scripts, compile and run them, and also save them. Such new scripts created in Script Editor on 10.10.3 CAN be opened by Script Editor. only old scripts fail.

I tried cleaning up my machine (caches, permissions, you name it). I also deleted Script Editor’s preferences and state - in case they got broken.

I reduced my security settings to run software from “Anywhere”

— to no avail.

  1. It’s a little panicking does anyone know what happened?
  2. Is there another tool that could open my old scripts, at least for re-saving them as text, so I won’t lose them?

Thanks!

P.S, the same behavior if I drop an old script onto Script Editor, double-click the script, or use the File Open menu from Script Editor to open the old script.

#2

Hi

sounds bizarre, can you supply a link to an old script maybe, and ill see if I can open it here, i’m running 10.10.3, script editor v2.7

#3

I have had similar issues in the past (not with Yosemite), and resorted to pulling in scripts from Time Machine backups. That worked great, but I am completely clueless about why.

#4

Hello.

It hasn’t happened to me, but I’d try the terminal command

to check if maybe some quarantine attribute or other have been set during the upgrade.

#5

I got this odd behavior.
As I had an other boot volume, I ran from it and open every scripts and export them as .applescript.

What is “funny” is that when I re-booted from my standard volume the .scpt files were opening flawlessly.
I have no explanation to that, just describe what I got.

Yvan KOENIG (VALLAURIS, France) mardi 5 mai 2015 10:07:30

#6

Hey There,

Well, that’s freaky.

You have rebooted your system and all that jazz?

Yeah, install Smile. It should open them without issue. If not then something is really screwy.

See if this works on an AppleScript file selected in the Finder:


tell application "Finder"
	set fSel to selection as alias list
	if fSel ≠ {} then
		set _file to first item of fSel
	end if
end tell
set _file to quoted form of (POSIX path of _file)

set scriptSource to do shell script "osadecompile " & _file

tell application "AppleScript Editor"
	activate
	make new document with properties {text:scriptSource}
end tell

If it does then you have a number of options. If it doesn’t then again there’s something really wrong.

#7

Hello.

First of all I’d check for “funny” extended attributes like quarantine, and such with the ls command. Then I’d really start to do the following.

Shut down the machine

I’d hold down shift during start up, when you hear the chime and keep it pressed until you see the logo, so that you boot into safe mode.

Then I’d run disk utility, with repair permissions, and do all the repairs, if any.

Then I’d try to run a script, to see if it works in safe mode

Then I’d reboot, and try again.

I have no idea if this will work, but those are the steps I’d try.