Forum Replies Created

Viewing 15 replies - 226 through 240 (of 409 total)
  • Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    Hey John,

    I saw yours as I was checking to see if anyone had done something similar prior to releasing mine. Yours definitely includes functionality I’d consider having in a post password manager plugin (the ability to sync all passworded posts to the same password; at least that’s how I understood what your plugin did from the description and now from what you said), but for this I really wanted to have it so the master post password worked in addition to the existing post password without changing anything.

    Different ways of accomplishing some similar ends!

    The feed and permalink stuff yours does could similarly be implemented in mine, which is worth a consideration.

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    Thanks for the suggestion! I’ll keep it in mind for a future release.

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    Please try the newly released v3.3 of the plugin. It should fix this bug. It also includes a tool you can use to test how it would treat usernames.

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    I just released v3.3 of the plugin. I fixed a bug relating the the partial username restrictions, but that doesn’t sound like what you’re experiencing.

    If you continue to have issues, please provide more details about what you’re attempting to do. How have you configured the plugin and how are you verifying that is isn’t working?

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    Are trying to allow or prevent spaces in usernames? Is the plugin’s related setting checked or unchecked?

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    Hi Rob,

    Getting a user custom field value is contingent on knowing the custom field “key” (the name with which a value is stored under — e.g. a custom field name/key of “favorite_color” may have the value of “blue”). You probably know that.

    I’m not familiar with Magic Members and since it is a commercial plugin I can’t investigate it for you. The first thing I would have checked would be to see if the extra custom user fields are indeed being stored as traditional WP user custom fields. It’s possible the plugin is storing those extra fields in a different way (as a plugin setting or in a separate data table).

    If it does use the WP user custom fields table, then it’s just a matter of knowing the exact custom field names/keys it uses. As a commercial plugin, you may be able to request that information from their support team.

    If you have access (and the comfort level) to view the database tables for your site, look at the table that ends with “_usermeta”. The “meta_key” column contains the names you need to know in order to use the plugin’s widget, shortcode, or template function to access the associated “meta_value”. So find the “meta_value” that contains information you supplied Magic Members via the User profile page. If it’s there, then the associated “meta_key” is what you’ll use with Get User Custom Field Values.

    Hope that helps!

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    Indeed. The plugin will be updated shortly. Stay tuned.

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    Ok, I understand what you’re trying to accomplish. How have you used the Get Custom Field Values plugin in this process? If you’ve inserted one of its template tags into a template, what template(s) and could you include the code snippet? If a shortcode, what was the shortcode?

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    Assuming that plugin provided a filter for the custom field data it display the answer would be yes. But on a quick scan I did not see such a filter. Can you describe briefly how you’re using Advanced Custom Fields? That may help me help you.

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    Can you provide an example of what you’ve done so far and demonstrate what you’d like to ultimately accomplish? I’m not clear what you’re looking to do or how you’re using the plugin.

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    Are you trying to display the <embed> as code in a post, or are you trying to actually put that in a post and want the browser to treat it as an embed?

    If the latter, then the question doesn’t relate to the plugin. You would have to enter the embed markup in the plain HTML editor rather than the Visual editor.

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    Hi Talitta,

    What are you trying to do with the plugin? Using a shortcode might be easier.

    Using the template tag (c2c_get_custom()) requires some familiarity with the theme you’re modifying. The loop can be defined in multiple files, so it is dependent on how the theme is structured and what context you want to display the custom field data.

    Provide a little context for what you’re trying to accomplish and I should be able to help steer you better.

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    It uses echo. _e() is only really useful if it is utilized in conjunction with a textdomain, which can’t be parameterized.

    It technically adds a slight bit more overhead. It essentially does the condition checks you’d do, but in order to accommodate passing along arbitrary arguments (making it flexible), it also uses func_get_args(). The extra overhead is quite minuscule and shouldn’t be noticeable. Even if being done 25+ times in a page.

    With the plugin, you save in time writing the code, you write/see less code, and have some flexibility afforded by some of the various methods provided by the plugin. But everyone’s perception of that value will vary.

    Plugin Author Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    That message is intentionally output by the plugin when, as it says, a searchform.php file is present in your theme. The description for the plugin explains this in more detail. But basically a limitation in WP prevents the plugin from stopping the contents of searchform.php from being displayed. The notice is just meant to make you aware of that.

    The plugin still works to prevent searches from returning anything and removes the search widget. But if your theme has a searchform.php file, the search form will still appear.

    Scott Reilly

    (@coffee2code)

    WordPress & Plugin Developer

    Yes, you’ll want to register a callback to handle sanitization of submitted form values. It’s the third argument to the register_setting() function.

    An example of the validation function:

    function sunburst_theme_options_validate( $input ) {
      $options = get_option( 'sunburst_theme_options' );
      if ( ! isset( $input['checkbox'] ) || $input['checkbox'] != '1' )
        $options['checkbox'] = 0;
      else
        $options['checkbox'] = 1;
      return $options;
    }

    If you have other options in your theme you’ll want to sanitize them in there as well.

Viewing 15 replies - 226 through 240 (of 409 total)