Title: Scott Reilly's Replies - page 8 | WordPress.org --- # Scott Reilly [ ](https://wordpress.org/support/users/coffee2code/) * [Profile](https://wordpress.org/support/users/coffee2code/) * [Topics Started](https://wordpress.org/support/users/coffee2code/topics/) * [Replies Created](https://wordpress.org/support/users/coffee2code/replies/) * [Reviews Written](https://wordpress.org/support/users/coffee2code/reviews/) * [Topics Replied To](https://wordpress.org/support/users/coffee2code/replied-to/) * [Engagements](https://wordpress.org/support/users/coffee2code/engagements/) * [Favorites](https://wordpress.org/support/users/coffee2code/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 106 through 120 (of 409 total) [←](https://wordpress.org/support/users/coffee2code/replies/page/7/?output_format=md) [1](https://wordpress.org/support/users/coffee2code/replies/?output_format=md) [2](https://wordpress.org/support/users/coffee2code/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/coffee2code/replies/page/3/?output_format=md)… [7](https://wordpress.org/support/users/coffee2code/replies/page/7/?output_format=md) 8 [9](https://wordpress.org/support/users/coffee2code/replies/page/9/?output_format=md)… [26](https://wordpress.org/support/users/coffee2code/replies/page/26/?output_format=md) [27](https://wordpress.org/support/users/coffee2code/replies/page/27/?output_format=md) [28](https://wordpress.org/support/users/coffee2code/replies/page/28/?output_format=md) [→](https://wordpress.org/support/users/coffee2code/replies/page/9/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Stealth Update] QuickEdit UI](https://wordpress.org/support/topic/quickedit-ui/) * Plugin Author [Scott Reilly](https://wordpress.org/support/users/coffee2code/) * (@coffee2code) * WordPress & Plugin Developer * [10 years ago](https://wordpress.org/support/topic/quickedit-ui/#post-6748676) * [@ecdltf](https://wordpress.org/support/users/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! * Forum: [Reviews](https://wordpress.org/support/forum/reviews/) In reply to: [[Add Admin JavaScript] crashed WordPress 4.5](https://wordpress.org/support/topic/crashed-wordpress-45/) * Plugin Author [Scott Reilly](https://wordpress.org/support/users/coffee2code/) * (@coffee2code) * WordPress & Plugin Developer * [10 years ago](https://wordpress.org/support/topic/crashed-wordpress-45/#post-8088789) * [@reuterpl](https://wordpress.org/support/users/reuterpl/): Hi, * A support thread would have been more appropriate for us to discuss looking into the issue together (and given me the chance to rectify the issue if was indeed caused by this plugin). * That said, how were you able to deduce that this plugin is at fault? The line of code referenced by the error message is for WordPress’s `get_user_option()` function which is not used directly or indirectly by the plugin. * Add the error is complaining that the function `get_userdata()` is undefined, but that’s defined in `wp-includes/pluggable.php` and should be available. Sounds like something else is going on. * Can you provide more details? Was it a specific page on your site causing the error? Have you tried switching to one of the default themes and deactivating all plugins and then activating *only* Add Admin JavaScript and testing things?( And then activate each other plugin in succession and test as you go). * Thanks. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Auto-hyperlink URLs] Thank you for updated version!](https://wordpress.org/support/topic/thank-you-for-updated-version/) * Plugin Author [Scott Reilly](https://wordpress.org/support/users/coffee2code/) * (@coffee2code) * WordPress & Plugin Developer * [10 years ago](https://wordpress.org/support/topic/thank-you-for-updated-version/#post-7278905) * [@neotrope](https://wordpress.org/support/users/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! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Stealth Update] Lock icon](https://wordpress.org/support/topic/lock-icon/) * Plugin Author [Scott Reilly](https://wordpress.org/support/users/coffee2code/) * (@coffee2code) * WordPress & Plugin Developer * [10 years, 1 month ago](https://wordpress.org/support/topic/lock-icon/#post-7274308) * [@rhialto](https://wordpress.org/support/users/rhialto/): Hi, * On its own, WordPress only has a “Date” column for posts which shows either “ Published”, “Scheduled”, or “Last Modified” depending on the status of the post, so it’s the only date-based column to attach to. * Are you by chance using a plugin that adds a “Last Modified” column? If so, I would agree that that would be the more appropriate column to attach to, but I’d have to make special provisions for such a plugin since not everyone will have that activated. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Get User Custom Field Values] Multiple field output in widget](https://wordpress.org/support/topic/multiple-field-output-in-widget/) * Plugin Author [Scott Reilly](https://wordpress.org/support/users/coffee2code/) * (@coffee2code) * WordPress & Plugin Developer * [10 years, 1 month ago](https://wordpress.org/support/topic/multiple-field-output-in-widget/#post-7223671) * [@joe1977](https://wordpress.org/support/users/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! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Published By] Feature request: Person who FIRST edited the post](https://wordpress.org/support/topic/feature-request-person-who-first-edited-the-post/) * Plugin Author [Scott Reilly](https://wordpress.org/support/users/coffee2code/) * (@coffee2code) * WordPress & Plugin Developer * [10 years, 1 month ago](https://wordpress.org/support/topic/feature-request-person-who-first-edited-the-post/#post-6996662) * [@thearcturian](https://wordpress.org/support/users/thearcturian/): Hi, * Thanks for the feedback! * Unfortunately, there isn’t a universally successful approach to guessing the actual publishing user of a post from before this plugin was activated. * WordPress on its own tracks who last edited a post, which is the first fallback for this plugin. WP does not track the first (or any other) editor of the post. Even if it did, the first person (or any Nth person) can’t be assumed to be the publishing user either (it may be the original author or any number of other editors who didn’t actually press the publish button). Granted, the last user to edit the post isn’t guaranteed to be the publishing user either, but I feel its a reasonable and straightforward fallback assumption. * And while a post may have post revisions, any guesses made from those won’t apply for all people or all posts. I can definitely envision a post getting drafted with numerous revisions by the original author, while the publishing editor does a quick read and publish with fewer revisions. So in this case the user with the most revisions isn’t the publishing user. I don’t think’s it’s viable to assume the publishing user will work on a post more often (in terms of revisions) than any non-publishing users. * However, I’ve made a note to investigate if it’s viable to infer the publishing author from the revisions. * In the meantime, if the plugin’s guessing is more wrong for your site than it is right, you can use the documented line of code to disable all guessing. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Hide Broken Shortcodes] Does not catch FD Footnotes shortcode](https://wordpress.org/support/topic/does-not-catch-fd-footnotes-shortcode/) * Plugin Author [Scott Reilly](https://wordpress.org/support/users/coffee2code/) * (@coffee2code) * WordPress & Plugin Developer * [10 years, 3 months ago](https://wordpress.org/support/topic/does-not-catch-fd-footnotes-shortcode/#post-6955179) * [@gahapati](https://wordpress.org/support/users/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! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Admin Post Navigation] Next button disappears on publish](https://wordpress.org/support/topic/next-button-disappears-on-publish/) * Plugin Author [Scott Reilly](https://wordpress.org/support/users/coffee2code/) * (@coffee2code) * WordPress & Plugin Developer * [10 years, 3 months ago](https://wordpress.org/support/topic/next-button-disappears-on-publish/#post-6957391) * [@ruralinfo](https://wordpress.org/support/users/ruralinfo/): Hi, * Thanks for the report! * Is this a change in behavior after updating to v2.0? Presumably you were using v1.9.2 previously without any problems? * When you publish a post, isn’t it usually the most recently published post and thus there is no next post to navigate to? * Or put another way, what post would you expect to be “next” after this post? ( Not the title or anything specifically, but what about the “next” post should make it next? You created it after the newly published post, even though this next post isn’t published yet or was published earlier?) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Disable Search] Plugin is not working after the update to 1.5 (2016-01-14)](https://wordpress.org/support/topic/plugin-is-not-working-after-the-update-to-15-2016-01-14/) * Plugin Author [Scott Reilly](https://wordpress.org/support/users/coffee2code/) * (@coffee2code) * WordPress & Plugin Developer * [10 years, 4 months ago](https://wordpress.org/support/topic/plugin-is-not-working-after-the-update-to-15-2016-01-14/#post-6947015) * [@timtaller](https://wordpress.org/support/users/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! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Disable Search] Just updated to 1.5 on two sites and both produce the following…](https://wordpress.org/support/topic/just-updated-to-15-on-two-sites-and-both-produce-the-following/) * Plugin Author [Scott Reilly](https://wordpress.org/support/users/coffee2code/) * (@coffee2code) * WordPress & Plugin Developer * [10 years, 4 months ago](https://wordpress.org/support/topic/just-updated-to-15-on-two-sites-and-both-produce-the-following/#post-6947014) * [@craig-damon](https://wordpress.org/support/users/craig-damon/): Thanks for reporting and sorry about that. I’ve just updated the plugin to v1.5.1 to fix the newly introduced bug. Cheers! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Disable Search] Does not work after update](https://wordpress.org/support/topic/does-not-work-after-update-3/) * Plugin Author [Scott Reilly](https://wordpress.org/support/users/coffee2code/) * (@coffee2code) * WordPress & Plugin Developer * [10 years, 4 months ago](https://wordpress.org/support/topic/does-not-work-after-update-3/#post-6947529) * [@pvwylick](https://wordpress.org/support/users/pvwylick/), [@madpauly](https://wordpress.org/support/users/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! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Disable Search] status header 200 OK](https://wordpress.org/support/topic/status-header-200-ok/) * Plugin Author [Scott Reilly](https://wordpress.org/support/users/coffee2code/) * (@coffee2code) * WordPress & Plugin Developer * [10 years, 4 months ago](https://wordpress.org/support/topic/status-header-200-ok/#post-6942719) * [@esemlabel](https://wordpress.org/support/users/esemlabel/): Thanks! I’ve just updated the plugin to v1.5.1 to fix the newly introduced bug. Cheers! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Disable Search] status header 200 OK](https://wordpress.org/support/topic/status-header-200-ok/) * Plugin Author [Scott Reilly](https://wordpress.org/support/users/coffee2code/) * (@coffee2code) * WordPress & Plugin Developer * [10 years, 4 months ago](https://wordpress.org/support/topic/status-header-200-ok/#post-6942664) * [@esemlabel](https://wordpress.org/support/users/esemlabel/): Hi, * Thanks for the suggestion! I just released v1.5 of Disable Search which implements your request. * Cheers! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Admin Post Navigation] Add Support For Media As Well?](https://wordpress.org/support/topic/add-support-for-media-as-well/) * Plugin Author [Scott Reilly](https://wordpress.org/support/users/coffee2code/) * (@coffee2code) * WordPress & Plugin Developer * [10 years, 4 months ago](https://wordpress.org/support/topic/add-support-for-media-as-well/#post-5729156) * [@perfectreputationsnowadmin](https://wordpress.org/support/users/perfectreputationsnowadmin/), [@mydiskdriveonline](https://wordpress.org/support/users/mydiskdriveonline/), [@emcarnahan756](https://wordpress.org/support/users/emcarnahan756/): * Hi all! Thanks for the suggestion! The just-released v2.0 of the plugin introduces the ability to navigate media as well (when in the “list” view). * The “grid” view for media, as [@mydiskdriveonline](https://wordpress.org/support/users/mydiskdriveonline/) noted, already had its own navigation. * Cheers! * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Admin Post Navigation] Updating Draft to Schedule takes me out of Drafts](https://wordpress.org/support/topic/updating-draft-to-schedule-takes-me-out-of-drafts/) * Plugin Author [Scott Reilly](https://wordpress.org/support/users/coffee2code/) * (@coffee2code) * WordPress & Plugin Developer * [10 years, 4 months ago](https://wordpress.org/support/topic/updating-draft-to-schedule-takes-me-out-of-drafts/#post-6697611) * [@myheadithurts](https://wordpress.org/support/users/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? Viewing 15 replies - 106 through 120 (of 409 total) [←](https://wordpress.org/support/users/coffee2code/replies/page/7/?output_format=md) [1](https://wordpress.org/support/users/coffee2code/replies/?output_format=md) [2](https://wordpress.org/support/users/coffee2code/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/coffee2code/replies/page/3/?output_format=md)… [7](https://wordpress.org/support/users/coffee2code/replies/page/7/?output_format=md) 8 [9](https://wordpress.org/support/users/coffee2code/replies/page/9/?output_format=md)… [26](https://wordpress.org/support/users/coffee2code/replies/page/26/?output_format=md) [27](https://wordpress.org/support/users/coffee2code/replies/page/27/?output_format=md) [28](https://wordpress.org/support/users/coffee2code/replies/page/28/?output_format=md) [→](https://wordpress.org/support/users/coffee2code/replies/page/9/?output_format=md)