Fidgety Lizard

Noted ??

I do see (and partly agree with) your point! I never feel that happy about changing a file in a fixed release.

On the other hand, frequent updates (especially ones that don’t actually provide any functionality benefits or fixes) really irritate some users. Additionally, if you maintain a lot of sites on behalf of clients and do diligent post-update tests, unnecessary plugin version bumps cause a lot of wasted effort. Swings and roundabouts!

Perhaps the best option would be some sort of external mechanism for specifying the tested-up-to (rather than keeping it within the plugin code repository) – but that would be a pretty significant infrastructure change…

Hi there,

This isn’t an error; the readme updates within v 1.1.0 are deliberate.

When a new version of WordPress is released, it’s necessary to adjust the readme to show the latest “Tested up to” value.

Best practice for WP plugins has been *not* to release a new stable version when you merely update the readme with a new “Tested up to” number: for example, see this WP release announcement for developers:
https://make.www.ads-software.com/plugins/2015/04/21/reminder-please-test-your-plugins-with-4-2/

This will cause issues with plugin checksumming (and e.g. fire off Wordfence alerts re changes to the readme file), but that will affect any plugins that follow this best practice advice, not just Forum Beginner Posts.

If there are any new official guidelines for plugins on this “Tested up to” issue, however, please do let us know and we’ll follow them – cheers!

That’s great, thanks for taking the time to let me know.

I’m assuming this issue was related to the Theme-my-login plugin – please start a new support thread if not.

Hi there,

Ah, yes, it’s quite likely that there might be a conflict with Theme-my-login, if it’s creating its own non-standard versions of the login and password reset pages. (The JavaScript for clearing the password relies on finding and adjusting the standard WordPress password reset form fields.)

If possible, could you try disabling Theme-my-login temporarily and see if that fixes the problem?

Cheers!

Hello there,

Just to be 100% clear, the password entry *box* will always appear on the password reset page – the plugins will simply remove the suggested password string from this box, so that the box shows up as empty.

If you’re not sure, then you’re very unlikely to have JavaScript disabled. If you could tell me what operating system and browser combination you’re using, I will try to recreate the problem.

Re being sensitive to browser type, I’ve tested in Firefox, Chrome, Safari, IE and Edge on platforms including Win10, Win7, Linux, OS X, iOS and Android, and haven’t found any where the password isn’t successfully cleared. (This is why I need to know what OS and browser you’re using).

Thanks!

Thanks for the report! I can’t duplicate this – could you let me know what operating system and browser you’re seeing the problem on? (I’m presuming you don’t have JavaScript disabled?)

Hi there,

This plugin doesn’t affect the ordinary login page.

When you request a password reset, you receive an email containing a link to the password reset page, where you can choose a new password.

It’s the behaviour of the password reset page that is changed by this plugin.

Hello there,

This is actually irritatingly difficult – or at least I haven’t found an elegant solution. (The WordPress function add_editor_style() can be used to change the editor appearance in the admin back end, but this function does not work in the front-end site.)

In bbPress, the editor panel appears in its own iframe, and loads its own styling. At the time of writing (bbPress 2.5.13), it’s created in bbpress/includes/common/template.php with a call to the WordPress function wp_editor(). You can supply editor styling as an extra parameter to this method – but bbPress doesn’t provide a “pluggable” way to do this, so to make changes there you’d need to hack the actual bbPress code.

If you do find a better solution than this, please let us know!

I’m closing this thread now, but do let me know if you have any further information.

Here it is:

https://www.ads-software.com/plugins/no-suggested-password/

Hi Namruf,

I’m not sure if this is even a configurable option in TinyMCE (the visual editor used by WordPress), but if it is, it would need to be configured in bbPress where the visual editor is created/initialised (same location as per the advice about bbPress in your previous query).

You can dig into the TinyMCE documentation on their website for more info about how the visual editor works and how it can be customized, if you’d like to.

Cheers!

You’re most welcome! It’s submitted to the repository now; I’ll let you know once it becomes available.

Hi there,

You would also need to tweak the add_action() call to reflect that fact that your function (in theme’s functions.php) is not a class member anymore.

I figured other people might find this simplified functionality useful too, so I’ve put together a plugin that will do just this, called “No Suggested Password”. I’ll submit it to the WordPress repository today, and hopefully it will become available within a day or two. If you need it urgently, send me a message with your email address via the Fidgety Lizard website, and I’ll send you a zip file.

Cheers!