Scott Reilly

Hi @louisapple: Could there be a conflict with another plugin that’s running on your production site but not your staging site, or a typo/difference between the two CSS statements you’ve written?

In general, if you know how to, I’d first view the page source and serach for some unique aspect of the CSS you added (such as “f98b8b”) to verify that the CSS was actually output by the plugin into your admin page. If so, then I’d use your browser’s inspector tool on the element (the note content) that you were trying to change to see if there is a CSS rule that may be more specific (and therefore takes precedence) over the rule you provided.

I did just release v2.0.1 of the plugin which fixes a bug some users were experiencing, but that was mostly related to the plugin page not appearing. But I’d recommend using the latest just to be absolutely sure things weren’t also affecting you.

Cheers!

@shirtguy72: Thanks for the report and providing the error message! I just released v1.8.3 of Disable Search that should fix the issue. Let me know if you encounter anything else.

Cheers!

@hothbricks: Thanks for the report and providing the error message! I just released v1.9.6 of Admin Commenters Comments Count that should fix the issue. Let me know if you encounter anything else.

Cheers!

Hi @hothbricks:

Did you encounter any specific issues running the plugin under PHP8? I haven’t specifically tested the plugin under PHP8 just yet, but I don’t see anything that stands out as being potentially problematic.

Thanks!

Hi @rudyodo,

Thanks for the kind words!

As for your inquiry, the checkbox has always been available in each user’s own profile. However, it was not possible for admins to edit the checkbox on another user’s profile. So logged in as an admin account, if you visited another user’s profile you wouldn’t see the checkbox. But if that user logged in and viewed their own profile, they would see the checkbox.

That was the case until just now. v1.4 of the plugin was just released, and its main change was to allow admins the ability to view and edit the checkbox for other users.

Does that address what you brought up, or did I misunderstand?

Hi @yodelice, do you have any specifics regarding what wasn’t working for you?

Or are you referring to the warning at the top of the plugin page here in the Plugin Directory? If so, it is true that the plugin hadn’t been updated in 6 months, which was long enough for the “This plugin hasn’t been tested with the latest 3 major releases of WordPress…” notice to appear at the top of the plugin’s page.

I’ve just released v4.4 of the plugin, which has the side effect of removing that notice. Please try it out and let me know what problems you encounter.

Cheers!

Hi @kittmedia!

Thanks for the report! I’ve just released v1.9.1 of the Remember Me Controls plugin, which incorporates your request to add a missing textdomain.

Cheers!

Hi @theblueli,

It is not within this plugin’s functionality or intent to remove the “/category/” path that is at the root of category permalinks.

However, it can be done. See the Remove Category URL plugin, whose whole purpose is this very thing. If you happen to be using Yoast SEO (and if you aren’t, the plugin might be overkill for doing just this one thing), it seems to have a “Strip the category base” setting.

I have not used either plugin for this purpose so I can’t personally vouch for them, but they seem to do what you want.

Best wishes!

@tech4eleven: Where is that sidebar content that includes links coming from? Is it a widget (if so, which one)? Or is it part of a template file?

By default the plugin only auto-links post content, post excerpt fields, and widget text. Plugins that create widgets in funky ways or text hardcoded in template files are examples of things that are not supported out-of-the-box. Some code customization may allow it to work with another plugin.

@theaonar: Hi, I’ve just released v4.0 of the Text Hover plugin which fixes the bug you reported about not being able to add hovertext to strings that begin and/or end in punctuation.

Thanks again for the report. Cheers!

@americanfreak: Hi,

Normally I would have said yes, though it would require adding a line of code into a file. But it turns out the library the plugin uses to handle time calculations doesn’t support timezone abbreviations.

So I have started work on a new version that will do two things:

1. Allow you to customize the time format via an input field on a settings page without needing to add code anywhere.
2. Add support for timezone abbreviations.

After which your request will be a 30 second change for you to make to get what you want.

I’ll follow up here to let you know when that version gets released.

Cheers!

@wpcursus: Hi,

The plugin is still actively maintained, but thanks for inquiring. It caused me to realize that a release meant for January didn’t get deployed so I’ve just done it. v3.9 of the plugin has been released.

It supports the use of Gutenberg, but doesn’t have any special blocks or block integrations (nor are any necessary).

As for your question about it working for post titles, it does not work on post titles by default as I don’t believe that is applicable to the majority of users. However, it can be made to work with a small bit of code. If you check out the documentation for the plugin (available on the plugin’s page here or its readme.txt file), look for documentation on the c2c_text_replace_filters filter in the “Hooks” section. There happens to be an example of the code to do just what you want.

I understand that may be a bit much to take on. In the next version of the plugin it will have a setting allowing you to add support like this without needing to add custom code. But for now, that is how it would need to be done.

I’ll follow-up once that feature gets released.

@staplefish: Hi,

Thanks for the bug report! And apologies about taking so long for the follow-up. I’ve just released v3.9 of the Text Replace plugin which fixes the issue, amongst other changes. (The update should have gone out in January but there was a deployment issue that I didn’t notice at the time, so it’s going out now.)

Cheers!

@galengidman: Hi Galen,

Thanks for the suggestion! I’ve just released v1.8 of the Disable Search plugin, which includes your request to disable output of SearchAction from the SEO schema (and have credited you for the recommendation in the plugin’s changelog).

Cheers!

@clrd: Thanks for the review and kind words!

I’d be interested in pursuing better support for languages without spaces, though I’m curious about your particular use-case or those you’ve seen.

Would having the option to ignore spaces as separators work in those languages? Obviously that wouldn’t work in something like English because defining hover text for something like “cat” would incorrectly match a word like “catch”, but for languages without spaces, would that not be a concern?

There are some further difficulties from just having a checkbox to turn on/off support for a space as a word delimiter if someone is making posts utlizing multiple language, e.g. English and Japanese. The safest approach in that case might be to have a second input field; the original input field defines hover text when a space should be used as a word delimiter (as it currently does) and the second input (the new one) defines hover text when a space shouldn’t be used.

Do those suggestions sound like they might help?