Scott Reilly

@malae: Hi,

The plugin only removes the notice that would appear at the very top of every admin page. The screenshot (seen on https://wordpress.org/plugins/no-update-nag/) shows the thing that this plugin removes.

I described above two instances where the newer version of WordPress is mentioned, and those are unchanged (since those aren’t “nags”):

* The Update to 5.1.1 button in the admin dashboard (as seen in the screenshot you linked to)
* The Get WordPress 5.1.1 link in the bottom-right of the admin footer

Those sound like they cover the 2nd and 3rd cases you mentioned. And the 1st case you mentioned is also not affected by the plugin (as intended): the “WordPress Updates” page will still tell you there is a new version of WordPress. I’m considering adding more comprehensive disabling of WordPress updates in a future release.

@bjf2000: Hi,

Just so we’re on the same page, are you referring to the notice that appears at the top of every admin page that (currently) says WordPress 5.1.1 is available! Please update now.? (Check out the screenshot included on the plugin’s page here: https://wordpress.org/plugins/no-update-nag/ to see an example.)

There are other places in the admin where you will still be notified about a new release even when this plugin is active:

* The Update to 5.1.1 button in the admin dashboard (as seen in the screenshot you linked to)
* The Get WordPress 5.1.1 link in the bottom-right of the site footer

The plugin does not attempt to remove the latter two, just the notice at the very top of admin pages.

@jpc101: Hi,

Thanks for the report! I’ve just released v3.9.1 of the plugin which addresses this error (a WP 5.x function was being used without first checking to see if it existed, which it doesn’t pre-5.0). Let me know if you encounter any other problems.

Cheers!

Hi,

Could you please clarify your claim about how this plugin is for programmer’s only? There is nothing that needs to be done for the plugin to function except to activate it. There are no settings and there is no need to write any custom code.

The plugin does provide certain hooks that could be used by someone writing code to customize the plugin’s behavior, but most people wouldn’t need to do so.

@the-muffin-top: Hi Gayatri,

Since you sought to add a search bar in the first place, it seems that you aren’t using my Disable Search plugin (which, as the name indicates, seeks to disable search entirely).

I’m not familiar with the Foodie Pro theme so I can’t advise too much on the specifics of how the search field is implemented. Have you tried asking for support from StudioPress?

This might help:
https://stackoverflow.com/questions/46363358/remove-search-form-from-menu-in-wordpress-genesis

Or this looks to be an improvement of the menu bar search field:
https://sridharkatakam.com/responsive-menu-with-inline-search-in-foodie-pro/

Based on that last link, though info is hidden behind a paywall, it starts off with how to disable the search form in the menu.

It says to change:

$menu_search = sprintf( '%s</li>', __( genesis_search_form() ) );
return $menu . $social . $menu_search;

I imagine the hidden next step (which should be all you need to simply remove the menu bar search field) should be to replace that with:

return $menu . $social;

If you want to implement the responsive menu bar search form (as shown in that video) which will allow it to show up on the mobile version, you’ll have to sign up for that site to get the code.

That’s about all I can do for you. No guarantees about any of the above. Hope that helps!

@scollonp: Hi Paul, thanks for the report.

v1.9.1 of Linkify Text was just released, which includes a fix to ensure multibyte functions (those that start with “mb_”) aren’t used if they are not available.

After updating to it, can you report back on the flakey behavior if it persists? If it does, could you elaborate on what you mean by flakey (with examples if possible)? Do the affected post(s) make use of multibyte characters?

Cheers!

@saschinger: Hi Sascha, thanks for the suggestion! I have just released v1.9 of Linkify Text which introduces a setting for links to be opened in a new tab. Just update the plugin and then visit the plugin’s settings page to enable the feature.

Also, a new filter has been added (“c2c_linkify_text_link_attrs”) which could be used programmatically for finer-grained control of link attributes.

Cheers!