[Tim Wood]

Are you running your scripts in Script Editor or another scripting tool? At least one other tool has problems with our change to 'activate' taking a direct object parameter, so maybe that is related.

If the 'display dialog' calls aren't working, your script might be hitting an error before it gets there. If you have a 'try' block, it might be eating the error.

As far as breaking things -- running simple scripts shouldn't break the existing terminology. It could be that your scripting tool has cached the scripting dictionary incorrectly or otherwise gotten confused. If that's the case, restarting it should hopefully fix the problem.

As a side note, though it isn't published in the scripting suite (as it is a standard command), OmniFocus supports the "log" command, taking a string. This will go to /Applications/Utilities/Console.app and the Event Log in Script Editor (and presumably the equivalent in other tools). This can be a useful and less annoying alternative than 'display dialog'.

For example:

tell application "OmniFocus"
	log "hi!"
end tell