Hey Steve,

There is something that the module is doing when the blog post is saved. I believe they are probably fiddling around with the "document" object. I am not too sure what their scripts are doing.

Since the saving process is "ajax" based, this will often cause errors if the module / plugin is trying to perform some actions relating to the document object.

ok ... are you saying that when the "post" is "being saved" in the backend, the "loadposition" code is actually being "executed" as opposed to the text just being saved?

Yes, because when EasyBlog saves the blog post, it actually triggers Joomla's trigger before saving a post just like what Joomla article does. However, the difference is that in EasyBlog, the "save" request are made via "AJAX" (not a page refresh) and if the module tries to do something extraordinary like manipulating with the "Document" object in Joomla without first testing the document type, it'll hit errors.