kevine

Actually, I take back what I wrote 2 days ago. You can still use this plugin and add new shared items.

The trick is not to use the Google Reader website but a 3rd party Google Reader app instead.

For example, I’m using the iOS app, MobileRSS on my iPhone and iPad and it still allows sharing of articles on Google Reader.

In other words, the back end of Google Reader still supports sharing items, they just removed the front end user interface on the website.

I wouldn’t count on this lasting, but hopefully this helps some who are stuck right now.

Yes, I believe it is unusable now. Technically, the plug-in works, but there’s no way to update your shared items feed, so it can’t really be used.

A lot of people are really pissed at Google over this and other features they suddenly removed in order to promote Google+

That’s the ticket!

Thanks again. This is wonderful!

Thanks again for helping!

I’m working with a copy of my database so I can play around and mess it up (and also have a backup).

What you posted mostly worked, but I got an error:
#1062 – Duplicate entry ‘2106-8044’ for key 1

Oddly, it still put some of the posts into the Audio category, but stopped in chronological order, but not on post ID 2106

When I went to post ID 2106 in WordPress I see there are two enclosure fields, which was an error made by the person who made the post. I deleted one of the enclosure fields and ran the query again. The second time I get:
#1062 – Duplicate entry ‘7-8044’ for key 1

Post ID 7 didn’t have a second enclosure, but it was already in the Audio category from having run the query the first time. When I delete the category and recreate it (clearing all posts from the category) it then runs without error.

Is there any way of modifying this query so that it won’t have an error if the post is already in the category?

If not, it’s still very useful, and I can assign this as Resolved.

This is working!!!

Thank you so much vtyzzy! I searched all over the place for this, but couldn’t find an example anywhere. I’ll be sure to share the info.

Ok,

I found a better way, but it requires editing functions.php. See:
https://kevinjedwards.com/51/how-to-stop-wordpress-28-from-deleting-enclosures/

Just delete or comment out lines 1164-1168

Thanks MJAYAS,

This is seriously messed up behavior, and very sloppy in terms of putting the URL in the body.

What I’m confused now about is whether this is now considered a bug, and will be fixed, or should we figure out a way of engineering around the sloppiness of having a redundant URL and also figure out how to add these to the thousands of posts we have…grrrr.

I never understood the desire for the auto-enclosure thing. I’ve always thought it was annoying, restrictive and problematic.