So got some help here months ago and had a great working set of scripts attached to folders and everything was converting and working perfectly on a weekly basis. Then for some reason this week stuff just stopped working without me changing a thing. When files are sent to the folders with Carbon Copy Cloner, Numbers opens, starts a conversion, the progress bar hits 100% and then nothing happens. No file is saved out, the original is not deleted from the conversion folder and the process does not finish and close the folder/app. Can anyone help me out as to what has changed/broken? Script is below.
on adding folder items to this_folder after receiving added_items
repeat with this_file in added_items
tell application "Finder"
set theInfo to properties of this_file
set theName to name of theInfo
set theName to (characters 1 through -9) of theName as text
set thePath to "Macintosh HD:Users:jt😀ropbox:Students:16-17 Students:Mustapha, Curran😛arents Stipend:" as string
end tell
tell application "Numbers"
activate
open this_file
set thisDoc to document 1
export thisDoc to file (thePath & theName & ".pdf" as string) as PDF
quit
end tell
tell application "Finder"
delete this_file
end tell
end repeat
end adding folder items to
[doublepost=1485181408][/doublepost]Might have solved this by disabling and re-enabling the accessibility services, go figure. Fingers crossed.
on adding folder items to this_folder after receiving added_items
repeat with this_file in added_items
tell application "Finder"
set theInfo to properties of this_file
set theName to name of theInfo
set theName to (characters 1 through -9) of theName as text
set thePath to "Macintosh HD:Users:jt😀ropbox:Students:16-17 Students:Mustapha, Curran😛arents Stipend:" as string
end tell
tell application "Numbers"
activate
open this_file
set thisDoc to document 1
export thisDoc to file (thePath & theName & ".pdf" as string) as PDF
quit
end tell
tell application "Finder"
delete this_file
end tell
end repeat
end adding folder items to
[doublepost=1485181408][/doublepost]Might have solved this by disabling and re-enabling the accessibility services, go figure. Fingers crossed.
Last edited: