Thread Starter
Amie
(@sunburntkamel)
welp, i guess i’ll just recommend people use the links block widget then, since it respects $before_widget and $before_title.
it would still be nice to solve this, though.
The reason your code failed is because you don’t have $wpdb defined. You need to declare it global at the start of the function in order to get access to it. Just stick a “global $wpdb;” at the very beginning of the widget_linkslist() function.
Other than that, your code is fine, but you do need to stick ul> and /ul>
tags around the call to wp_get_links(). Why? Because wp_get_links will stick the li> tags around each link. Well, that’s not entirely true, it will use the correct “Before Link”, “Between Link and Description”, and “After Link” settings defined for the Link Categories in the Links Manager, but these are usually li> and such and there’s no reason for most people to ever change them. No themes change them that I’m aware of.
The better fix for this is in the widget plugin itself. Changing that to use the code similar to the codex linked to above really makes more sense than using get_links_list().
Thread Starter
Amie
(@sunburntkamel)
thanks muchly. i thought it might be something like that.
i’m actually ok with people breaking the functionality by changing the ‘before link’ and ‘after link’ fields.
it’s always annoyed me that most themes make those fields pointless.
Thread Starter
Amie
(@sunburntkamel)
i agree that this should be fixed in widgets.php, it’s bizarre that they would go too such lengths to make the widget format customizable, and then ignore that on the blogroll widget.
to be bulletproof(er), you’d need to discover whether or not the ‘before link’ and ‘after link’ are set to ‘
li>’, and if they are, put in ‘ul’ tags, and if not, put in a ‘<div>’
Thread Starter
Amie
(@sunburntkamel)
and for the love of god, in a forum where we’re talking about code, there should be a more reliable method of posting code.
