Forum Replies Created

Viewing 15 replies - 121 through 135 (of 409 total)
  • Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @mkormendy : Hi again,

    I just released v2.0 of the plugin. While I didn’t specifically implement a fix for this issue, it’s possible that it may have been inadvertently fixed. If you could, please try again.

    Unfortunately I have still not been able to reproduce the bug. I even tried to reproduce everything about your situation that I could glean (using the CPT UI plugin to create a restaurant post type, having a restaurant post titled “Eduardo’s”, and a next post titled “El Campesino”). Is there any chance you can try with all plugins except for Admin Post Navigation and CPT UI disabled?

    Thanks again for reporting the issue and working with me. I just want to let you know I’m still looking into it whenever my attention makes its way back around to the plugin.

    Cheers!

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @joff19: Hi,

    Thanks for the bug report. Please try the just-released v2.0 of the plugin to see if your issue has been resolved.

    Cheers!

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @madivad: Hi,

    Thanks for rating the plugin and also for the suggestions!

    I’ve made note of the save-when-you-navigate idea. It would certainly be handy, though it’ll require some rework and testing to implement, so I didn’t put it into the just-released v2.0.

    The ability for the user to easily specify sort order has been on the TODO list for awhile. Definitely something I’d like to get to.

    The “Save/Update and Back to All” is a good idea, but not one I’d incorporate into this plugin since it’s a bit out of scope. However, it’s something I would consider implementing as a standalone plugin.

    Finally, thanks for performing the test for the apostrophe bug brought up by another user. The independent confirmation helps. However, I am as yet unable to reproduce the bug. I’ve recreated everything I could from the original report, as well as other variations, and it always works for me. I’ll continue the investigation. If you are so inclined, please try the apostrophe-in-the-title test again with v2.0.

    Thanks again! Cheers!

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @quadbox: Hi,

    Apologies for the delayed response.

    Thanks for the suggestions! Please check out v2.0 of the plugin for its newly added RTL support. Let me know if you encounter any issues with it.

    Cheers!

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @importantlyernest: Hi,

    Here’s some code for allowing the widget titles to receive the Text Hover treatment. You’ll have to put the code somewhere (ideally in a site-specific plugin, or possibly more conveniently in your active theme’s functions.php file).

    If you don’t know how to modify files on your site, you’ll have to look around for more information to do so (look for creating a “wordpress site specific plugin”). I always encourage people to have a fresh backup of the site before they make any sort of modification and have enough know-how to be able to restore the file(s) they changed in case something goes wrong. This code works for me; it’s possible (though unlikely) it may not work for you given your specific theme and/or plugins.

    // Prevent WP escaping HTML in widget titles (so they can be text-hoverable).
    remove_filter( 'widget_title', 'esc_html' );
    // Perform text hovering for widget titles.
    add_filter( 'c2c_text_hover_filters', 'my_text_hover_widget_title', 100 );
    function my_text_hover_widget_title( $filters ) {
            $filters[] = 'widget_title';
            return $filters;
    }
    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @ben_dajao: The plugin expressly does not do permanent replacement, so it must remain activated.

    Changing data globally in the database can result in some unintended text replacements, so it’s safest for the plugin not to do it. Also, depending on the size of the site’s data and the nature of the site’s hosting environment, it may not complete in a timely enough fashion, leaving the data in an unknown state (and the replacement process may not be able to safely be run again, depending on the replacements that were defined).

    In short, there’s a lot of risk to do in a general-use way in a plugin and isn’t something I set out to do with it. The plugin could certain be used by another script or plugin to iterate through all posts on the site, call the plugin’s function to handle text replacements, and then save the posts back to the database. But that’s an exercise left to someone else.

    If you have access to a web interface for your database (such as through phpMyAdmin in your hosting account’s cPanel (or similar)), you could directly run an SQL statement to permanently replace text (Google would help you find the specifics).

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @maredbor : Hi,

    Thanks for reporting the issue! It has been fixed in the just-released version of the plugin, v1.6.

    Cheers!

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @overhall: Hi,

    Yes, the plugin is safe to use! I’ve updated it to explicitly note its compatibility with WP 4.3.

    Cheers!

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @apunahasa : Hi,

    How exactly didn’t things work for you? Did the login form page whitescreen? Did the login process give you any errors? Did the login form submit and stall out? Were you just redirected back to the login form without being logged in and without errors?

    The plugin does very little so I just want to make sure I have a good idea of what you’re experiencing.

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @dietpop : Hi,

    Can you provide more details about how you’re using the shortcode? What is the actual shortcode you’re inserting? And where are you putting it (presumably a bbPress post)?

    Are you using the latest version of bbPress?

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @mwsat : Hi,

    Thanks for reporting the issue. I have just released v2.9.1 of the plugin to fix it.

    Cheers!

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @rjpedrosa : Hi,

    Thanks for reporting the issue. It has been fixed in v1.9.2 of the plugin.

    Cheers!

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @opentoesock : Hi,

    Thanks for the follow-up and checking into caching being the culprit. As you would’ve suspected and hoped from the plugin, once it is deactivated it has no lingering effects on the site.

    Cheers!

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @aamir2007 : Hi,

    As I explained earlier in this thread:

    There’s a lot involved in allowing duplicate usernames, little of which overlaps with what the plugin currently does. It would warrant being its own plugin, but not one I’m looking to build at this point.

    I go into some of the details in that response as well.

    I’m curious: if you’re using another plugin to handle logging in via email rather than username, then why do you need to permit duplicate usernames?

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    Yes, the reported issues for the plugin were fixed in v2.5 back in February.

Viewing 15 replies - 121 through 135 (of 409 total)