Chip Bennett

Theme developer has been contacted regarding the XSS vulnerability, and the Theme has been suspended in the directory pending the issue being fixed.

Regarding the Theme’s handling of custom headers: the Theme doesn’t claim to support the Custom Header Image feature; rather, it has a custom logo option. This is acceptable, because custom header images and logo images are two different things.

For future reference when searching for Themes: if you want a Theme that supports Custom Header Images, look for Themes with the “custom-header” keyword. Any Theme with that keyword uses the Custom Header image feature, and does so via implementing the core method for that feature.

Hi soulint,

What Theme did you test on? Were any other Plugins active? I’m trying to recreate your issue on my end.

Also: do you have a live link that demonstrates the problem?

For testing purposes:

1. Have Twenty Twelve active
2. Disable all other Plugins
3. Remove define( 'WP_DEBUG', true )
4. Don’t make any Theme file changes (such as adding Plugin functions directly)
5. Ensure you have both cbnet Really Simple Captcha Comments Plugin active AND the Really Simple Captcha Plugin active
6. Ensure you’re viewing the comment form from a browser that is NOT LOGGED IN to your WordPress install.

Do you still not see the CAPTCHA in the comment form? (By default, it will appear before the comment textarea, right after the other form fields (name/email/website).

I’m not sure what WP theme 1041 is. Can you (temporarily) switch to a core-bundled Theme (Twenty Twelve, Thirteen, or Fourteen), and let me know if the issue persists?

Hi soulint,

What Theme are you using?

When I add <?php cbnet_comment_captcha(); ?> in Appearance > Editor > comments.php (right after the comment entry TEXTAREA form field or anywhere else around it) everything below this php tag (including footer) disappears from the pages.

Where you’re getting a blank page, you almost certainly have a fatal error, but the error message is hidden. Can you enable debugging (add define( 'WP_DEBUG', true ); to wp-config.php), and tell me what fatal error message appears when you do this?

Hi Breezy,

Let’s try to track down the front page issue first.

1) Assuming you’re using a static page as front page, for the page assigned as the front page, what Page Template do you have assigned?

2) Assuming the Page Template is “default”, what is the Static Page Layout you have assigned to that page?

There is no out-of-the-box option for a content-on-left, sidebar-on-right layout for static pages. That’s perhaps something I could add.

Now, for the footer copyright: the default copyright text uses the oldest published post to derive the copyright date.

The copyright date specifically is not filterable (something else I should add), but the copyright text itself is, via the oenology_hook_site_footer filter. For example, you could add the following to a Child Theme:

function breezy_site_footer( $site_footer ) {
    // Site name/link
    $site_footer['copyright'] = '<span><a href="' . home_url() . '">' . get_bloginfo('name') . '</a></span> ';
    // Current year
    $site_footer['copyright'] .= '&copy; ' . date('Y');

    // Return
    return $site_footer;
}
add_filter( 'oenology_hook_site_filter', 'breezy_site_footer' );

This will replace the oldest post date with the current year.

Hi @befound, did you post a support topic to try to resolve the issue?

What does the browser source show? Are <div class="nav-previous"> and <div class="nav-next"> appearing?

Note that previous_posts_link() displays newer posts, and next_posts_link() displays older posts – but both only output if there are multiple pages of posts to display.

That Theme was last updated five and a half years ago. Your best bet is to find a Theme that has been kept current with WordPress.

Are all of you using the NL language version?

What Theme are you using? What Plugins do you have active? Is it a single-site or multi-site network install?

Do you have the WP Beta Tester plugin installed/active, and set to “bleeding edge nightlies”?

No problem. Happy to help!

Okay, in wp-admin\includes\class-wp-upgrader.php, there is a function, send_core_update_notification_email(). This is the function that sends the email notifying the administrator that a new core update is available. In that function is a filter:

if ( ! apply_filters( 'send_core_update_notification_email', $notify, $item ) )
    return false;

$this->send_email( 'manual', $item );
return true;

That basically says, “if $notify is false, then don’t send the email; otherwise, send the email”. So, you just need to tell WordPress that $notify is false. To do that, just add a filter (which you can put in a site functionality Plugin, or a Child Theme:

function designsandcode_prevent_core_update_email( $notify ) {
    __return_false();
}
add_filter( 'send_core_update_notification_email', 'designsandcode_prevent_core_update_email' );