Sky,
I'm sorry you've run into this. I'll revisit the code, but I'm aware of this issue and wrote a routine to add spaces before the script tag so that this wouldn't happen. It sounds like that code needs to be checked. Basically, the code looks at the max summary for the module settings.
Of course, having this code doesn't protect against changing the max summary length later and thereby introducing a whole new set of truncated HTML tags.
Honestly, I really struggled with this while developing the Blog provider and there was no good solution. The issue is that the summary shouldn't be truncated unless it's text. This same issue will arise if regular content image tags are truncated.
What I have done on my blog is set the max summary value to the maximum value for an integer. This solves the problem and also makes the blog look a little more like some of the more modern blogging platforms.
I considered placing the attribution link at the top, but I've noticed that for those who use the blog to show an aggregated listing of multiple blog authors, the shortened summary is popular (DNN Blogs, for example). This being the case, I didn't want to place the attribution div at the top of the page since it would be considered content by the blog module.
I'll check the code again to make sure the anti-truncation logic is correct, and this will certainly help minimize the chances of this happening again, but until the blog module is updated, I'm afraid we'll have to live with some level of HTML truncation if we want to let the blog module automatically truncate our summaries.
One approach that would work well for teams of people all using metaPost would be to use the Extended Entry feature to provide a summary and actual post with each blog entry. You would combine this with setting the max summary to a high number. Of course, the obvious disadvantage here is that you're left to the content provider's judgement regarding the length of the summary.
Do any of these solutions sound workable for you?
Thanks,
Don