Forum Replies Created

Viewing 15 replies - 16 through 30 (of 71 total)
  • Plugin Author Fidgety Lizard

    (@fliz)

    OK, in that case your best bet would be to disable all plugins, and also flush your browser cache completely (or use a different computer/browser for testing), and see if the problem persists. (Clearing your cache is important in case the browser is “remembering” a rogue redirect.)

    If it works with no plugins, you’ll need to enable them one by one and test again to work out what is causing the trouble. If you’re using any plugins that claim to do anything at all to the login process (e.g. restyle your login page or whatever), that would be a good place to start. It’s also possible that your theme is in some way incompatible with the WooCommerce login/register forms, so it would be worth trying a different theme too.

    As I mentioned, this plugin only adjusts the password-choice page, it doesn’t change the actual control flow of the password reset process. (Also, I’m assuming you know that the password reset process involves requesting a password reset email via the “Lost your password?” link, then clicking on the link in the email you receive? If you’re missing that step, and not getting an email, then maybe your server is not sending email properly.)

    If you’re still having trouble, it would be best to get more help in the WordPress or WooCommerce support forums as I don’t think this plugin is the cause (or solution!) of this particular issue.

    Plugin Author Fidgety Lizard

    (@fliz)

    Hi there! This plugin doesn’t change the control flow between pages in the password reset process; it just adjusts the layout of the password reset page and provides a “Suggest a password” button”. If you’re stuck in a password reset loop, something else is causing the problem.

    If you’re running any “membership” plugins or other user-management/user-profile plugins, and/or any kind of plugin to change the standard login address or provide a front-end login widget, I’d suggest you temporarily disable them and see if the problem persists. (I’ve seen problems like this before with plugins that attempt to customise the login address…)

    Plugin Author Fidgety Lizard

    (@fliz)

    Hi there,

    I’d love to take credit for the editor, but it’s just the bog-standard WordPress one; this plugin just switches it on fully for forum posts 🙂

    In terms of the automatic embedding, this is also a WordPress built-in feature for certain commonly-used services like YouTube that support a standard called oEmbed. You can find out more info here:
    https://codex.wordpress.org/Embeds

    If screencast-o-matic supports oEmbed, you can add a little bit of code to your theme to enable automatic embedding for its video links; details on this are towards the bottom of the page just mentioned.

    Hope this is helpful!

    Plugin Author Fidgety Lizard

    (@fliz)

    Noted 🙂

    Plugin Author Fidgety Lizard

    (@fliz)

    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…

    Plugin Author Fidgety Lizard

    (@fliz)

    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.wordpress.org/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!

    Plugin Author Fidgety Lizard

    (@fliz)

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

    Plugin Author Fidgety Lizard

    (@fliz)

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

    Plugin Author Fidgety Lizard

    (@fliz)

    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!

    Plugin Author Fidgety Lizard

    (@fliz)

    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!

    Plugin Author Fidgety Lizard

    (@fliz)

    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?)

    Plugin Author Fidgety Lizard

    (@fliz)

    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.

    Plugin Author Fidgety Lizard

    (@fliz)

    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!

    Plugin Author Fidgety Lizard

    (@fliz)

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

    Plugin Author Fidgety Lizard

    (@fliz)

Viewing 15 replies - 16 through 30 (of 71 total)