I got an email tonight from a reader. He’s been trying to post comments and it has been failing. This is not something that inspires me to happiness.
I spent a lot of time during the migration fiddling with Disqus. Even now I’m sure not all the comments were imported successfully but I’m just tired of it after this last screw up.
So I did another sync between Disqus and WordPress tonight and then switched it back over to the internal commenting system. If anyone has trouble please let me know.
TMM is the owner, editor, and principal author at The Minuteman, a competitive shooter, and staff member for Boomershoot. Even in his free time he’s merging his love and knowledge of computers and technology with his love of firearms.
Many know his private name and information however due to the current political climate, many are distancing themselves due to the abandonment of Due Process.
Raw Feed
FeedBurner Feed
Subscribe by Email
I’m a big fan of Disqus on my blog, but their 2012 version is full of suck and fail. I reverted back to the old version after a day.
Yup that seems to be the consensus. I’m sick of futzing around with it. I can’t think of anything that Disqus actually gives me anymore though since Jetpack allows WordPress, Twitter, and Facebook account usage for commenting.
Yeah it would be nice if Google SSO was in there too, but honestly it doesn’t matter much. In the end it was starting to cost me time instead of saving me time, that is when it failed and went to the bit bucket.
Hello, I’m sorry to hear of the issues you are having with Disqus! We’d love to help you out and apologize for the experience you’ve had. You can send us a support request through http://disqus.com/support/ and we can further look into the problems you are having with importing. In addition, if the user that was having trouble posting comments sends us more information in a support request as well, we’d be more than happy to look into it.
Thank’s for the reply Christina. The issues I’m having though seem to be with readers accessing and posting comments. I haven’t personally had issues that the readers have described though this is not the first time I’ve heard about them.
I could revert back to the earlier form of Disqus, however I do not feel it is worth me spending the time to do so. I am not paid to do this, I actually currently spend my hard earned money to run the blog. I am willing to spend the money because the costs are relatively low, however when I start spending time on technical aspects as opposed to content, the costs of running the blog go up exponentially. My hourly wage makes this quickly not worth my time even though I enjoy making content.
When I migrated from Drupal to WordPress in June Disqus was handy in that once I got the redirects straightened out the content was tied together correctly. However I began spending more time at the admin panel and there were other odd idiosyncrasies I spent my time fixing, much of them from the migration. Again I just considered that the cost of moving. However once readers started saying they had issues commenting I got tired of spending my time on it. Disqus had gone from a benefit to a bane.
The built in comments provide all the features I originally got from Disqus. Heck even the original reason I moved was tied to the previous blog software. If at some point in the future I see a feature provided by Disqus that I think will benefit myself of my readers I will investigate it and think about turning it back on.
That is the key for me, there needs to be a reason it is worth my time and effort, right now I’m not seeing it.