Me too after last update:
“WordPress Link Manager is inactive. To take full advantage of Link Library in WordPress 3.5 or higher, please install and activate the Link Manager Plugin.”
Same here, but dumb*** decided to add an admin wide notification message.
the same , i hope in the next release this issue be fixed
edit this:
link-library/link-library.php
find:
function link_manager_missing_msg() {
echo “<div id=’link-library-warning’ class=’updated fade’><p>” . __(‘WordPress Link Manager is inactive. To take full advantage of Link Library in WordPress 3.5 or higher, please install and activate the Link Manager Plugin.’, ‘link-library’) .”</p></div>”;
}
and replace with:
function link_manager_missing_msg() {
}
message is gone ;-D
Thanks for the fix, xad, but is this the best way to proceed?
Perhaps the Link Library devs need to fix something instead.
BTW, WP 3.5 isn’t the latest version. Interesting it should even display that message.
– MWM
Sorry for the annoying message folks. The latest update removes it if you are running 3.4.x.
The reason for this message is that the Links section will be disabled on new installations of WordPress starting in version 3.5, which is due to be released soon. To activate it, new users will need to install a plugin called Link Manager. The purpose of this message is to let people know that they installed and activated Link Library without having an active Link Manager.
For users upgrading, the Links section should remain visible, and that message will not appear.
As for having made the message displayed across the whole admin, I followed queue from the way other plugins display admin wide messages when an important thing is missing (e.g. akismet key).
dave111223 => When using free open source plugin, calling the author names when he/she spends countless hours developing a plugin is no way to thank someone for the hard work that they put in their work.
Sorry my comment was harsh, I had assumed this added code was in an attempt to coerce users into buying some kind of “Pro” upgrade for the plugin….whereas it appears it was just a genuine coding mistake. My apologizes.
