Scott Reilly

@ecdltf: Hi Tom,

Thanks for the contribution! 🙂 I meant to circle back and follow-up with this thread after the plugin’s latest release, so I’m glad you noticed the update.

For anyone else seeing this later, support for the quick edit box was added in v2.5 of the plugin.

Cheers!

@neotrope: Hi Chris,

Glad to hear the plugin has been of use to you! But yeah, it has been long overdue for an update, though it hasn’t really had any issues in the meantime. Now that I’ve finally gotten it up to date, it’ll be less of an effort to maintain going forward.

Now that you mention it, I just updated the Donate link on the plugin page to go directly to Paypal. But my site would get someone there eventually as well.

Cheers!

@joe1977: Hi,

The “Between text” field is meant to kick in if the user happens to have multiple instances of a given custom field. For instance, a user could have multiple “sibling” custom field keys defined (e.g. one with a value of “Anna”, one with “Peter”, etc). This setting would be the text to join those values.

The plugin is geared towards the display of a given field and not multiple fields at once. So you’d have to use multiple widgets (or shortcodes, or template tag calls), one for each user custom field you want to display.

I can see some merit in supporting the output of multiple fields via a single widget, shortcode, or function (e.g. output a “Family” list that includes the values of the custom fields “parent”, “sibling”, and “children”).

I’ve made note of the request to consider in a future release. Thanks for the suggestion! I’ll follow up if it gets implemented. But in the meantime, it’s not currently possible in just one widget.

Cheers!

@gahapati: Hi,

Thanks for the suggestions!

As for the issue with FD Footnotes, I just looked over its code and it doesn’t actually use shortcodes. It just uses a syntax that has square brackets around it, like shortcodes. But they aren’t officially registered or handled as shortcodes by WP. That plugin does custom scans and handling to do its thing. Unfortunately, that prevents it from being something Hide Broken Shortcodes can affect.

To your second request, there is indeed a way to hide the text between broken shortcodes, but it’s via code. There’s an example in the readme, which I’ll reproduce here:

/**
 * Don't show broken shortcodes or the content they wrap.
 *
 * @param string $default The output the plugin would normally show.
 * @param string $shortcode The name of the shortcode.
 * @param string $content The text between the opening and closing "tags" of the shortcode, if any.
 * @return string
 */
function hbs_handler( $default, $shortcode, $content ) {
	return ''; // Don't show the shortcode or text bookended by the shortcode
}
add_filter( 'hide_broken_shortcode', 'hbs_handler', 10, 3 );

That would hide all broken shortcodes as well as the text they wrap. If you wanted only certain broken shortcodes to be handled this way, the function can be modified to check $shortcode for the desired shortcode names.

Hope that helps!

@timtaller: Thanks for reporting and sorry about that. I’ve just updated the plugin to v1.5.1 to fix the newly introduced bug. Cheers!

@pvwylick, @madpauly: Thanks for reporting and sorry about that. I’ve just updated the plugin to v1.5.1 to fix the newly introduced bug. Cheers!

@esemlabel: Hi,

Thanks for the suggestion! I just released v1.5 of Disable Search which implements your request.

Cheers!

@myheadithurts: Hi,

Thanks for the suggestion! Just so I’m clear about what you’re requesting, how would you envision the navigation to work only for drafts?

Now, if you are purely navigating drafts that is pretty straightforward (it just goes to the prev/next draft relative to the draft you’re looking at).

In your specific example though, once you change a draft to another status, it obviously is no longer a draft. So should the draft-only navigation disappear entirely? Should it now switch to navigating the same status as the post you’re now looking at? Or should it ALWAYS navigate only drafts, even if you are editing a published post?