Forum Replies Created

Viewing 15 replies - 166 through 180 (of 409 total)
  • Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @hseelam : The WP-SMTP plugin is a different plugin. You’ll have to ask for support from its developer in its own support forum: https://wordpress.org/support/plugin/wp-smtp/

    Cheers!

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @mvandemar : Hi Michael,

    The fields are optional. You can leave the “Sender email” and “Sender name” fields blank and the plugin won’t affect any “From:” field information for outgoing emails.

    It doesn’t selectively override those values though. It either always does (because you provided a value in the plugin’s settings) or it never does (because you didn’t provide a value).

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @casmiami : Hi,

    Sorry for the delayed response. Support for Text Hover in other places on a site (other than content, excerpts, and widget text) is possible but depends on knowing how that text is appearing on the site.

    Plugins often add filters on text they output, which is how this plugin changes text by default, but you’d need to know the name of such a filter (if there is one). Or if it’s something output by the theme, the Text Hover plugin could be called more directly (with a small change to the theme).

    So doing so isn’t that difficult, but it’s a matter of knowing what bit to change specific to your situation. What plugin is outputting the section on the upper right of the image you linked? If it’s publicly available I can take a look, but if it isn’t there’s not much I can do for you.

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @jonas-lundman : Hi Jonas,

    Thanks for pointing out the issue and sorry for briefly losing track of your support request. I released v1.3.4 of Add Admin CSS which should fix line-wrap handling for Firefox and Safari browsers.

    The issue was just with how the lines in the textarea were displayed and should not affect their actual newlines. (Basically, the settings saved in the database still have their newlines and should appear properly now.)

    Let me know if you’re still experiencing any issues with it.

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @kanjipad ; Hi,

    I can confirm that text immediately bookended by HTML tags do not get hover-texted. It’s a little trickier there to get it working and not have text inside of an HTML tag (such as in attributes) from getting hover-texted. I’m working on it though.

    I cannot confirm that text at the end of a sentence does not get hover-texted. At the link you provided, the kanji at the end of a sentence does have hovertext. My tests indicate that this should be working. Is this still a problem for you?

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @mulshine : Can you provide some specifics to help debug the issue?

    1. What settings (all of them) have you set for the plugin (and what are they)?

    2. What exactly were you trying to test if things worked (i.e. what usernames were allowed that should have been restricted)? Did the plugin’s “Test Username” tool say the username was valid or not?

    3. What is your site setup? (What version of WordPress? Or are you using BuddyPress or Multisite?) And presumably you are using the latest version of the plugin (currently v3.5.1)?

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    Hi Noahj,

    Glad you’re all set. If the plugin already had a settings UI, I’d consider adding a field for users to input the names of other filters to run the plugin against. I suppose I can add such a textarea in Settings -> Reading. I’ll mull it over.

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @cyberian90 : The two pages you linked and cited as not being linkified on your site are actually linked according to the plugin settings you noted above.

    Forum: Plugins
    In reply to: [Add Admin CSS] Not working
    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @cyberlp23 :The CSS you provided to override the #wpadminbar background color works for me regardless of the admin color theme chosen.

    I suspect you are talking about the adminbar’s background color on the front-end and not the back-end? If so, yes, the above CSS won’t work since the plugin doesn’t output any CSS on the front-end (hence the “Admin” in the name).

    Forum: Plugins
    In reply to: [Add Admin CSS] Not working
    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @cyberlp23 : Hi,

    Well, the first three worked fine for me. The last one didn’t work because the CSS selector was slightly incorrect (they are 2 classes on the same element). Here what I tried (I also added ending semi-colons; though for Chrome on OSX they weren’t necessary):

    tr.user-admin-color-wrap {display:none;}
    tr.user-rich-editing-wrap {display:none;}
    tr.user-comment-shortcuts-wrap {display:none;}
    tr.show-admin-bar.user-admin-bar-front-wrap {display:none;}

    Does that work any better for you?

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @cyberian90 : Hi,

    Could you provide some additional details:

    1. Which of the linkifications from your list aren’t working any more?
    2. What version of WordPress were you using previously? What version are you using now?
    3. Were you using v1.7 of Linkify Text before (when presumably all of the linkifications worked) and now? Or did you update the plugin between when you noticed everything worked and then some of them broke?
    4. If at all possible, could you provide the text of a sample post (the shorter the better; even if you create a new one just for this purpose) that demonstrates the issue of one or more of the linkifications that don’t work.

    I appreciate you proactively including your defined text and links.

    Your answers to the above questions will help me start to look into the potential problem. Thanks!

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @brand-dedication : Hi Noahj,

    The plugin has indirect support for hiding broken shortcodes as they may appear in other places, via the hide_broken_shortcodes_filters filter.

    In your case, this would be accomplished with a few lines of (untested) code added somewhere on the site (perhaps in an mu-plugin, or less ideally in the theme’s functions.php file):

    /**
     * Hides broken shortcodes that appear in WooCommerce product short descriptions.
     *
     * @param array $filters Filters that get their broken shortcodes hidden.
     * @return array
     */
    function hide_broken_shortcodes_in_woocommerce_short_description( $filters ) {
    	$filters[] = 'woocommerce_short_description';
    	return $filters;
    }
    add_filter( 'hide_broken_shortcodes_filters', 'hide_broken_shortcodes_in_woocommerce_short_description' );

    The point of the hide_broken_shortcodes_filters filter was to provide a way for the plugin’s functionality to be able to be extended to other places. There are probably hundreds of other situations where broken shortcodes could/should be hidden, but accounting for them all is not feasible.

    You could argue that WooCommerce is a large enough plugin that it should warrant exception. It’s something I could be swayed about at some point, but currently there haven’t been any other identical requests from others for this.

    Does the above code get you the results you wanted? I only skimmed the WooCommerce code to find what looks like the relevant bit, so I may not have chosen the appropriate filter.

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @embracing-motherhood : Hi, what you want to accomplish sounds exactly like what the plugin offers.

    This is how to go about using it:

    1. Install the plugin via your usual means.
    2. Activate the plugin on the site.
    3. Go to the plugin’s settings page. You’ll find it in the side menu under “Settings”, called “Text Hover”.
    4. In the big text box, put in the text you want to want to receive hover text, followed by the hover text itself. An example:

    To Kill a Mockingbird => A classic by Harper Lee
    Kindle Paperwhite => Amazon’s fantastic e-reader

    Be sure to only put one per line.

    With the above defined, in your posts wherever you had (or will) write “Kindle Paperwhite”, that text will be automatically modified so that if the visitor hovers their mouse over the text, a hover text popup will display “Amazon’s fantastic e-reader”.

    The actual styling of the text in a post is left up to the default browser handling (which is typically a dashed or dotted underline). Use of CSS could provide greater control on appearances, but that gets more into design; the plugin just makes doing that possible).

    Does that help? If not, where are you experiencing issues?

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @vickita : Hi, thanks for pointing it out! The plugin actually did have a changelog entry committed as part of the v3.4 release, but the plugin page here on WordPress.org failed to update to show it. I poked it and everything is showing correctly now.

    Thanks again!

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    @habannah: Hi Julie,

    You’re pretty much there and probably would have gotten it if I had documented a change made to the ‘c2c_admin_post_navigation_orderby’ filter whereby it can send a second argument that is the post type being navigated.

    I’ve updated the documentation to reflect the change, which will be included in the next release of the plugin.

    Cheers!

    Here’s the code:

    /**
     * Modify how Admin Post Navigation orders posts for navigation by ordering
     * pages by 'menu_order' and posts by 'post_date'.
     *
     * @param string $field     The field used to order posts for navigation.
     * @param string $post_type The post type being navigated.
     * @return string
     */
    function custom_order_apn( $field, $post_type ) {
    	if ( 'page' === $post_type ) {
    		return 'menu_order';
    	} else {
    		return 'post_date';
    	}
    }
    add_filter( 'c2c_admin_post_navigation_orderby', 'custom_order_apn', 10, 2 );
Viewing 15 replies - 166 through 180 (of 409 total)