It appears that the special character kludge is causing SQL insert/update problems.
e.g. problem starts with a blog post that uses special characters to represent '
When BIM goes to insert/update this post into the database it runs the special character kludge which converts the special character representing ' into an actual '. Which causes problems with the SQL.
I still need to confirm this. It's a suspicion, but a strong one.
The fix will be to move the special character processing back into the RSS processing so that the normal escaping of SQL isn't bypassed by the kludge being done after it.
It appears that the special character kludge is causing SQL insert/update problems.
e.g. problem starts with a blog post that uses special characters to represent '
When BIM goes to insert/update this post into the database it runs the special character kludge which converts the special character representing ' into an actual '. Which causes problems with the SQL.
I still need to confirm this. It's a suspicion, but a strong one.
The fix will be to move the special character processing back into the RSS processing so that the normal escaping of SQL isn't bypassed by the kludge being done after it.