There definitely seems to be a problem with 2.0.7.
Friday at noon I reverted the site to 2.0.5 and the problem is gone. To be completely clear, the ONLY thing I did was revert the software to an earlier release. I did NOT reload the database or anything else.
