Steven Zahm@ Mark
Well, I got lucky, real lucky I think. I have it working. What I did was comment out (so it does not run) the code the reads the template directory looking for legacy templates. I do not mean legacy template the same way as legacy template like the ones that the Legacy Template extension adds… I mean really old templates. “Modern” template are really different and one of those major differences is that Connections needed to search for legacy templates. This search seems to be triggering the error. My best guess is that the folder permission are somehow preventing this quick search of the templates folder and triggering the error for some reason.
I’ve been slowly removing support for these really older template. The next bugfix release, I’ll skip doing this scan. And for those that are, for some reason, still using one of these old templates, I’ll have a plugin ready that’ll re-enable the scan for the.
Apologies for the trouble.