The error message was caused by a browser extension. I’ve removed it, but the plugin still doesn’t show the duplicates. Must be something else.
Hello @wattaman
Thank you for trying it out – This is a browser error/notice. Please try to disable your extensions in your browser and try the plugin again, or try to use a different browser?
Ok, so far so good, the first thing was an extension error. Regarding not seeing any duplicates:
- Have you selected the right post types to check for duplicates? Per default the plugin would only check posts and pages.
- Do you have a LOT of duplicates? Ie. so many that the plugin crashes? Try setting to a lower “find this amount of duplicates”, that can help on large sites.
- Perhaps you do not have any identifiable duplicates? The free plugin compares the title of the post/page, nothing else.
- Also, duplicates across same post type. If you have a page called “About”, but also a post called “About” – it is not considered a duplicate. One is a page, another is a blogpost.
I hope that can help guide you.
Thanks for the suggestion. Nothing worked, I’m afraid:
- yes
- Find how many duplicates: 10
- there are posts identical by title (content as well)
- only posts
What’s even stranger, I have installed the plugin on another site on the same server, and there it works. I’ve also tried to copy the php/nginx/wp (incl other plugins) settings from the working site to the other, without luck though.
There’s another duplicate posts plugin that I am trying, and it behaves the same. So there has to be something different between these 2 WP sites.
I’m out of ideas 🙁
OK, I’ve found out the issue. The plugin doesn’t work with the automated posts by Wpematico. But it does work with my manually published posts.
So just an incompatibility issue.
Thank you for letting us know – we have not tested with that particular plugin, but I have made a note to check it out.
Is this compatibility issue related to the error message that you first mentioned? “Unchecked runtime.lastError: The message port closed before a response was received. tools.php:1”
I don’t think so. Or at least there are no more errors in the console.
