Forum Replies Created

Viewing 15 replies - 241 through 255 (of 3,660 total)
  • Theme Author Chip Bennett

    (@chipbennett)

    It worked but what confuses me is the first step, when I cut the function from widgets.php, because what happens when an update replaces this file?

    No worries. That’s the same change I made in the development version – meaning that, when the next version is released, that change will have been implemented.

    Say for example I ever have to upgrade wordpress will that mess up the whispy theme from all the CSS and other changes that have been made?

    Updating WordPress itself (something you always want to do, as soon as an update is available) will have no impact whatsoever on installed Themes or Plugins. When WordPress core updates, the update doesn’t touch the wp-content directory where Themes, Plugins, and uploaded user content are stored.

    If so what should I do so I can replace everything after upgrading. I just don’t want to loose anything and if I run into a problem in the future I want to be able to replace anything that was lost, overwritten or whatever may happen.

    That’s only a potential concern if you are updating the Theme itself.

    The way to avoid that problem is to ensure that you don’t modify the Theme itself, but instead use a Child Theme (or, if the changes are CSS-only, you can use a custom CSS Plugin, such as the custom CSS module of the JetPack Plugin).

    I have a friend that had a custom theme made and when he upgraded to the new version of wordpress it ruined everything so I don’t want to be stuck in that same position if you know what I mean!

    Very likely, the issue there was that the Theme itself wasn’t well-coded. (All of us who have ever developed a custom Theme have been there before.) But you’re using a Theme from the Theme directory; all Themes in the Theme directory should be safe to use with updated versions of WordPress.

    I strongly encourage you to update your Themes and Plugins whenever updates are available. The developers release updates to add new features, to support changes to WordPress core, and to fix bugs and potential security vulnerabilities – though any Theme added to the Theme directory in the past couple of years should be relatively free of security vulnerabilities, thanks to the review each Theme must undergo before being approved.

    Why don’t you use add_image_size() to add a custom image size for that particular template use?

    For example (in functions.php, inside a Theme setup function, hooked into after_setup_theme):

    add_image_size( 'front-page-featured', 9999, 150, false );

    Then, in your template:

    <div class="featured-thumbnail">
    <?php
    if (has_post_thumbnail()) {
        the_post_thumbnail( 'front-page-featured' );
    }
    ?>
    </div>

    The add_image_size() args:

    'front-page-featured': name of the custom image size
    9999: width (in pixels)
    150: height (in pixels)
    false: hard-crop? (false = box-resize; true = hard-crop)

    So, that means that the custom image size will be scaled to fit a maximum height of 150px, with any width (less than 9999px).

    Same question.

    I’ve tried activating on a single multisite network site, and network activating. In neither case do I get an update notice.

    Theme Author Chip Bennett

    (@chipbennett)

    @thebachman,

    I don’t understand. Oenology ships with .mo and .po files, in the \languages subfolder.

    I would, of course, welcome translations!

    Theme Author Chip Bennett

    (@chipbennett)

    Sorry for delayed responses for a bit; I’m incredibly swamped at the moment.

    I’m honestly unsure why it won’t work for you, but if you want to try what I did:

    1. Move the function oenology_showhide_widget_content_open(){} and function oenology_showhide_widget_content_close(), and function oenology_get_widget_args() function definitions from functions\widgets.php into functions\custom.php

    2. Add the apply_filter() calls to oenology_showhide_widget_content_open(){} and oenology_showhide_widget_content_close()

    3. In your Child Theme functions.php, add the filter callbacks:

    add_filter( 'oenology_showhide_widget_content_open', '__return_false' );
    add_filter( 'oenology_showhide_widget_content_close', '__return_false' );

    (No need to put inside another callback.)

    This worked for me, as tested in a test Child Theme.

    Note: I’m getting close to having things ready for the next release, where your add_filter() calls should work out-of-the-box.

    Plugin Author Chip Bennett

    (@chipbennett)

    Hi yoramzara,

    Please try removing the Plugin entirely, and then re-installing. This appears to be an issue that has already been addressed in recent bigfixes.

    Please let me know if, after doing so, you still get the same issue.

    Thanks!

    Plugin Author Chip Bennett

    (@chipbennett)

    Hi stug2013,

    The Plugin doesn’t work explicitly on a post-by-post basis.

    However, I believe that the post authors should already get email notifications for comments for their own posts. So, you can use the Plugin to add yourself, or an admin, or whomever, to also get notification emails.

    Theme Author Chip Bennett

    (@chipbennett)

    Er, copy-paste error:

    The hooks are:

    – oenology_hook_site_header_before
    – oenology_hook_site_header_before

    function jknetdesign_site_navigation_hook() {
        get_template_part( 'site-navigation' );
    }
    add_action( 'oenology_hook_site_header_before', 'jknetdesign_site_navigation_hook' );
    Theme Author Chip Bennett

    (@chipbennett)

    Thank you for your kind review!

    Note: table styling can easily be overridden, either via Child Theme, or a Custom CSS Plugin such as the one available in JetPack.

    Theme Author Chip Bennett

    (@chipbennett)

    One idea:

    1. Via Dashboard -> Appearance -> Oenology Options -> General Tab, set “Header Nav Menu Position” to Do Not Display.

    Then, hook the site navigation template-part file into either of the following hooks:

    – enology_hook_site_header_before
    – enology_hook_site_header_before

    For instance, if you want the menu to appear above the header image:

    function jknetdesign_site_navigation_hook() {
        get_template_part( 'site-navigation' );
    }
    add_action( 'enology_hook_site_header_before', 'jknetdesign_site_navigation_hook' );

    Note that you may need to adjust CSS rules to accommodate whatever change you make.

    Theme Author Chip Bennett

    (@chipbennett)

    Try site-navigation.php.

    header.php loads site-header.php, and site-header.php loads site-navigation.php, either before or after the site name/description (based on Theme option setting).

    Plugin Author Chip Bennett

    (@chipbennett)

    @stug2013: please start a separate topic, since your issue is unrelated to the OP. Thanks!

    Plugin Author Chip Bennett

    (@chipbennett)

    This is probably related to Twitter’s recent API changes and updates. I need to investigate if anything analogous is available to use to update the Plugin, but it may be that I simply can’t.

    The Plugin relies on a script served by Twitter, and it appears that Twitter is deprecating that script. They appear to be trying to move users into different scripts, that aren’t quite so easy to package as WordPress Plugins. I will investigate and get back with you.

    Plugin Author Chip Bennett

    (@chipbennett)

    Younglion: please start a new topic, as you have a separate issue.

    Also, based on your error message, the issue is with the Really Simple Captcha Plugin, not the cbnet Really Simple Captcha Comments Plugin.

Viewing 15 replies - 241 through 255 (of 3,660 total)