mbeasi

It is still not working for me. I’ve tried it in both Safari 6.0.2 and Firefox 17.0.1. I just replicated this issue moments ago. I also tested it while logged in on one browser and logged out on the other, in case it was some kind of plugin conflict that only occurred when logged in, but the result is the same for me in both cases. Searching a term without quotes yields results, with quotes gives me a white page.

Here’s a screencap of what I get: https://mangabookshelf.com/images/whitescreen.png

ETA: Weirdly, it may be working differently for different searches? When I do the same search you did (presumably, according to my statcounter) “flying guillotine” it works for me. But my search, “banana fish” yields a white screen (though searching that same term without quotes works–there are definitely plenty of results for that search). Does that help at all?

Additionally:
“please save my earth” works
“black bird” white screen
“age called blue” works
“tokyo babylon” white screen

There are multiple results for all of these terms, but some of them don’t work if you put the words in quotes.

Primeweb: I just ended up switching to co-authors plus. It was a pain initially, but worth it in the end.

So fast! Thanks! Looks like it works perfectly.

Let me know if you’d like a list of plugins we’re running. There are a lot of them. Also, I should let you know that I’m running Genesis 1.8.

Yes, sorry for not thinking to do that sooner! Here’s the error:

PHP Fatal error: __clone method called on non-object in /home/username/public_html/wp-content/plugins/advanced-access-manager/model/accesscontrol.php on line 178

Update: I believe I have solved this problem myself. I am using the Genesis Framework on all of my network’s sites, and this comes with built-in SEO settings, including one that sets canonical archives for paginated pages. The default setting for this is “on.” I realized just now that the blog that was having the issue is the only one on my network that just uses the blog archive (list of latest posts) as its homepage, rather than a special widgeted front page, so I thought (based on what the Facebook debugger was saying) that perhaps it was considering that to be the canonical archive for the whole blog. So I turned the setting off, updated one of the posts, “Liked” it, and suddenly it all worked!

Since people are talking about this again… Ron, I installed the development version when we were originally talking in this post, and I’m sorry to say that it didn’t fix the problem at Manga Bookshelf at all. I still have to go in weekly and delete duplicate categories, or they quickly multiply into the hundreds.

Will the newest version of the official version work where the dev version doesn’t?

Flackshack, can you tell me how you got the upgrade script to run? I am trying to do the same thing, if possible.

Thank you!

I tested for that and didn’t have that issue. Is it possible that the ones this is occurring on are ones that were updated between when you upgraded to 3.1.3 and when you had the version with the fix.

Ah yes, that’s likely the case, since it was recent posts I was testing. That’s nice to know, since that means a relatively small number of posts were affected by the problem.

Ron’s fix in the development version works, or at least it did for me. You can download that from this page.

One note: the fix applies to all new posts, but I found that if you go back and edit posts that were made before the fix, they still reproduce, so just keep an eye out for that.

Oh, wonderful news! Thank you!

Just an update: performed a test as suggested by Ron above, submitting a post from a test blog with all plugins off. The problem still occurred. The post appeared as usual in the main blog, and then when I updated the post, it generated a new, duplicate post in the main blog.

Yes, I am using the development version, and I believe it is the most recent, though I will double-check. Should I assume from what you are saying that it has been tested with the latest WP upgrade and has caused no problems for anyone else? is it likely that another plugin is at fault when I haven’t updated or changed any of them? I can test that, I am just unclear in why that would be the case when they all worked together nicely up until today.

Thank you, in any case, for responding!

I should be clear, too, this is happening with new posts created after the update as well as with older ones. One post made today had five duplicates appear in the main blog, just from being updated at its source.

Nope, the only change is the WP update.