Link Library removed WordPress Link Manager

I am sorry you feel this way. I had a 6-month beta cycle, asking users for feedback on the new version. When I had not received any negative feedback for 2 months, I released the new version.

You can bring back the original Link Manager plugin by installing the plugin called Link Manager from the repo. That being said, that widget will no longer work with link modifications made in Link Library, since Link Library now uses custom post types.

It is great that you did the major update to Link Library. But I agree with JohnJohn that 4 updates in 1 week is at minimum irritating to those of us who work hard to keep our blogs updated. I understand critical fixes but perhaps consider doing the other less urgent updates once a week or once a month.

As it is I get notifications from multiple blogs that I manage several times a week just for this plugin.

The problem is that at this stage, every update is a critical fix for someone, since it usually means that something is not working right on their blog.

Had I had more feedback from beta testers trying this over more of their sites over the past six months, we would not be in this situation.

All I can suggest is that you look for an alternative plugin or write filters in your e-mail application to hide these notifications. There will likely be multiple updates a day for the next few weeks.

The new Link library widget does not give me the possibilit to chose among all the linkcategories I have so even if I work with the new version I can not remake my old widgets.

You can choose the categories to be displayed when you create a configure a library configuration under the Link Library section.

If all you were using from Link Library was the links editor and the links widget, then you were actually not using link library but only using the core WordPress Link Manager. In that case, you can actually delete Link Library from your site and install the plugin called Link Manager (https://www.ads-software.com/plugins/link-manager/). This will give you back the legacy link editor and the legacy widget, if that is all you need.

For the record, I understand the frustration with the multiple updates–but I’m also grateful to Yannick for doing them. He had a lengthy beta testing period. But the very people most likely to break the plug-in–people like me who have extremely complicated libraries and who can’t risk having those libraries go down–were the ones least likely to install the beta. So problems with complicated libraries just couldn’t be caught at the beta stage, no matter how much he tried.

So when the first non-beta version came out, and I installed it, lots of things broke. Yannick was careful to allow for an easy way to downgrade, so that I could keep my libraries up until the weekend (when it was less critical that they be up, and when I had more time to work on them). This was particularly a help because there were some things Yannick wasn’t going to be able to fix–the fact that my site map plug-in required me to include all custom post types or none, so I suddenly had no way to show other custom post types without showing every single link in my library. (This one required me to search for and install a site map plug-in that would allow me to select which custom post types to include.)

When the weekend arrived, and I had a chance to start working with the update, I was peppering him with support requests. He responded to each one within a few hours, and quickly updated the plug-in to fix the problem.

So yeah, it was a lot of updates–and my support questions were probably the cause of half of them. But anyone who didn’t want to update the often had the option of going back to the last 5.9x version until the bugs were worked out. And there really weren’t a lot of good options to figure out the problems ahead of time, or to fix them once they arose without multiple updates.