I'm trying to figure out if this is a new 3.2 feature/bug or a quirk of my installation.

I upgraded to 3.2, and now MT won't let me create or edit a template link (to an existing template file) unless that file is world-writable. If I change it to world-readable only, I get the error
CODE
Saving object failed: Opening linked file '/[...]/file.tmpl' failed: Permission denied

I'm only trying to get MT to read from an existing template file, not write to it. Like this:
  1. From MT, open an existing index template OR create a new one
  2. Template Body: If it's an existing template, empty this field (in a new template: already empty)
  3. Link this template to a file: Enter a valid path to an existing template file
  4. Save.
If the template file is world-writable, the save is successful and MT puts the contents of the file into the Template Body field. (This is how it always worked in 3.15 with read-only template files.) But now, if the template file is world-readable only, I get the "Opening linked file failed: Permission denied" error -- even though all MT should be doing is pulling the file contents into the template.

Is this "normal" for 3.2? I'm really confused and wondering if I should switch back.