Hi again Mike,
First things first, I am working on a pretty revamped version of this plugin that will provide numerous fallbacks to avoid timeouts and other issues that have been throwing errors. I know it's hard to wait when things aren't working right, but I did want to let you know this was in the works.
Secondly, I'm really sorry for the trouble, I've no clue what's going on as the latest version of the plugin works fine for me (even with WP_DEBUG on as well).
The weird thing about the error you're seeing is that it's referencing a file path that doesn't make any sense - the path includes "null" and "null-content", which don't seem right at all. I'm wondering if something went wrong server-side during the install process by some chance. Any chance you'd be willing to try reinstalling? Just for reference, the one line of code that is throwing this error is from an embedded framework in the plugin that I didn't touch at all:
defined( 'TF_PATH' ) or define( 'TF_PATH', trailingslashit( dirname( __FILE__ ) ) );
Essentially, the basic php function
dirname( __FILE__ ) is returning a path that appears to be broken, which makes me wonder if the plugin install just didn't quite work correctly. If you could try re-installing, that would clarify this one.</p>
<p>That said, the problem may be something else entirely - it's just hard for me to debug when I don't see the issue on my side. Can you explain if there were any steps you took other than just clicking the update link for the plugin? Is there actually a "null-content" directory on your install? If not, any idea why
trailingslashit( dirname( __FILE__ ) ) would be returning that directory?
I truly appreciate your patience and understand your frustration. I'll do my best to get to the bottom of this and fully test our new update to assure that it resolves these issues. Would love to give you an acknowledgment in the plugin about page as well, for all your help, if you're okay with that.