Peter Temple said
I’m just implementing Simple Press and I’m having an issue with comments. I have one regular visitor who today got the message, “Duplicate comment detected; it looks as though you’ve already said that!” and the comment doesn’t show up. I have other visitors that are able to comment, as can I.

This particular message comes from the WordPress commenting system and is not coming from Simple:Press. If SP was involved I really need you to explain how and in what way.

While simple press is live, I haven’t started using it live yet, so this is in my regular blog post.

So does that mean this WAS a comment on a blog post? If so then that really is not with the province of Simple:Press…?

I have deinstalled Post Blog Linking, which is where I guessed the problem might be. Now this same commenter still can’t comment, but doesn’t get the message any more.

Sorry but still unsure what the connection here is to SP..?

I’m on a Thesis 2.2 site with nothing really exotic other than that.

I also had a problem with the Tags plugin last week, that completely locked up the reply and quick edit functions and I had to physically remove it using ftp, so don’t know it there’s something left over from that.

There was an issue with out Tags plugin in an update that was put out the night before last – which has been corrected in a follow-up update now available. But this was, as I say, just a couple of nights back… not last week. 

Just using deductive reasoning. I haven’t made any other changes to the site in the last two months and today, I have a regular contributor to comments on my blog post (it’s daily trading site blog) that is unable to post a comment. Could a week ago but can’t today and get’s the message I cited.

I only added the Post Blog Linking plugin on Sunday. Have had no comments issues at all before I did that, or had the issue with the Tags plugin.

The problem I had with the Tags plugin as on Saturday or Sunday, which to me, was last week.

So, it seems to me that since this issue has happened in the past couple of days, and the only thing I’ve changed in the last two months or so is to add Simple Press this past weekend, maybe I’m completely out of my mind, but I’m focussed on Simple Press as the issue. If I’m out of my mind, then I’ll uninstall Simple Press and be done with it.

There was also a recent WordPress update but I think that was longer ago than the past few days. Peter

> On Jan 26, 2016, at 12:47 PM, Simple:Press Support wrote: > >

Well if I apply the same reasoning then I can see a way that a comment could be duplicated…

• IF you had Blog Linking turned on
• AND you were copying topic posts to the blog comments
• AND the user tried to save the same text they entered into a topic post into a new blog comment…

But that is about the only way. And I think you’d would agree  that would, indeed, duplicate content and the message from WP would thus be correct.

But if you have turned off the blog linking plugin as you said then there is absolutely NO connection between Simple:Press and WordPress blog comments. So I am unsure why your user can not create a comment now, Although you have not actually said what happens when they try now…

The issue with that is that Simple Press isn’t being used. It’s live but not linked to anything and I’ve only added in a couple of groups, forums, and topics as a test.

I’ve just realized that I didn’t remove the tags tables from the database, which I can do, to see if that’s an issue. Because physically removing the tags plugin had a direct impact on my comments area unfreezing. I simply removed it altogether without uninstalling … I take it these are the sf tables in the database, although I don’t see one called “tags” …

I had been playing with the duplicate hiding function in the Blog Post Linking plugin on Sunday. And deactivating the plugin changed the status of the commenter’s interaction with the blog post – he stopped receiving that message – so there’s obviously something going on there.

The other alternative is to uninstall Simple Press, all the relevant tables, test with this commenter and then start all over again … I was hoping for a better clue before I travelled down that path.

Actually, I had said what happens when they try to comment after uninstalling the Blog Post Linking plugin: They don’t get any message. Rather, the comment simply doesn’t show up. I have nothing on in discussions that should affect it. And nothing else has changed. Peter

> On Jan 26, 2016, at 1:19 PM, Simple:Press Support wrote: > >

The previous comment from that same person was Jan 20 … he had no issues then – that was last Wednesday. So I guess I’m heading to an uninstall and start over (if I have the energy) scenario … P

> On Jan 26, 2016, at 1:19 PM, Simple:Press Support wrote: > >

if blog linking is uninstalled, then clearly we have no interaction with the comment system of wp…  any other plugins that deal with comments?  the last couple of wp releases have restructured how comments works and moved stuff into classes… generally working, but a few open tickets to correct…  maybe it tripped up a plugin?  but with simple press blog linking uninstalled, if still an issue, something else at play…

I finally figured out the issue, but I don’t know what caused it. It would have helped greatly to know that the alert, (( Duplicate comment detected; it looks as though you’ve already said that! )) was not a Simple Press alert. That little bit of knowledge would have saved me a couple of hours of work. That’s what I was ultimately looking for-not a cat and mouse game. As it turned out something had wiped out that user’s comments status, so that his messages were headed to spam. I have no idea what caused the issue, but I’m deeming it solved. Simple Press has been removed completely. I’m deciding whether I want to even go there.

> On Jan 26, 2016, at 7:15 PM, Simple:Press Support wrote: > >

sorry, but back in post #2, Andy stated that it was NOT a simple press message but from WP itself…

Let me must say this: In my 25 years of coding, I have NEVER had a more antagonistic reply. Not to worry. I will not darken your screen again. P > On Jan 26, 2016, at 9:07 PM, Simple:Press Support wrote: > >

antagonistic?  interesting..  was just trying to point out after you rather pointed comment about how hours could have been saved, that Andy had already pointed it out…  apologies if my comment was misinterpreted…

HIS comment was antagonistic. Just leave it alone. My solution is a win-win solution. This is not a helpful place.

> On Jan 26, 2016, at 9:28 PM, Simple:Press Support wrote: > >

good luck in your endeavors…  we are here to help if needed…

Well – if anyone can explain to me how my reply at post #2 can in any way be considered ‘antagonistic’ then I would really like to know… I sat up later at night than usual seeing if I could work out what this guys problem might be – from scant and basically unhelpful information – and I just get insulted. That was a waste of an evening.

Thanks for illustrating, but now you’re being just plain rude and spamming me, so I will drop a line to Simple Press and blacklist you. Goodbye. Peter

> On Jan 27, 2016, at 1:28 AM, Simple:Press Support wrote: > >