AlbCoWebMgr

Thanks, but I found the problem. It’s the limitations of the free Aspose Cloud service that you have to sign up for to get the required SID & Key. Free accounts get a certain amount of “Credits” that are used up as DOCX files are exported and uploaded to cloud storage.

My credits were used up after the first 40 documents, even though there was plenty of storage available.

We would need to pay $99 and provide credit card authorization to continue exporting docs. You should state this in your plugin page!

Since we only need this as one-time use for one small blog, we’re unwilling to pay that fee. I just copied the remaining 45 posts to Word manually.

Thanks anyway.

I tried it, and it does work with Active Directory Integration!

Wow, this is awesome!

Thanks for the response — and for the plug-in!

posts > post_content collation is also utf8_general_ci. Content of the email itself is UTF. Client doesn’t make any difference. Same in Apple Mail, MSOutlook, smartphone, & webaccess.

In any case, again, the posts themselves in WordPRess don’t display this problem — only some of the HTML email versions.

The emails are not stored in the DB as far as I can tell. Where are they processed? If in a temp folder on the server, could something in the SERVER’s file structure be corrupting the content?

I’m thinking it’s not encoding per se, but some corruption in the plug-in scripts. I just deleted and reinstalled the plug-in for the second time. I don’t expect it will help, but we’re pretty desperate.

If another email gets corrupted, my next step will be to create a new blog site for the School and start over with fresh data.

I’d welcome any further suggestions.

Thanks.

The blogs were all created with UTF8 as the default collation.

Thanks for the rapid response, mattyrob!

Both the email sent by Subscribe2HTML and the database are using utf-8. The database is UTF8_general_ci, specifically.

The odd thing is that the Posts as displayed by WordPress do not have the issue. Only the email version.

All the post emails are authored by one person, using Internet Explorer. Some are messed up, others are fine.

Other suggestions, please!