Henry

I actually don’t get the error any more.

Hey guys thanks for the ideas. I ended up opting to programmatically set the front page to something different for logged in users. e.g.

if ( is_user_logged_in() ) {
    $page = get_page_by_title( 'contact us' );
    update_option( 'page_on_front', $page->ID );
    update_option( 'show_on_front', 'page' );
} else {
    // different front page...
}

jrf

regarding your validation check, are you thinking of doing if ( $post != null ) { ... }?

I’ve been doing some investigation and can see you’re using an is_singular() check around the code attempting to get the $post property. is_page() seems to return true for the BuddyPress change-avatar page (where there notices are displayed) but the $post variable seems to be null here. This could be the reason why toys are being thrown out of the push buggy.

Thanks again jrf – i’ve raised a BuddyPress Trac ticket:

https://buddypress.trac.www.ads-software.com/ticket/5241

The problem isn’t adding nofollow or stripping links. The problem is more to do with Google not recognising authorship when the two values are used together e.g rel="author nofollow"

you could copy the function to your theme’s functions.php file, rename it and then change the language. That’s what i did.

Guys, yes, it does return the date created. I can confirm that after checking on a fresh site.

thanks for you help.

flight1307 the header image of the panther loads instantly for me when I visit your site?

Thanks jrf – hoping your validating can resolve the problem.

Hi Russell

The target of the link is neither a paid link, nor an untrusted link, nor a login/protected link, which are the usual reasons for using nofollow

My site authors are not moderated so may well enter untrusted or paid links. This is the reason I need the nofollow on these links.

I don’t actually believe it can be done. You may know better though. Hope you can help.

Hey Lorenzo!

Thanks for the links, i’ll check them out. Much appreciated.

Yes I can and it isn’t a problem, it’s intentional. I just had an answer over at Stack Overflow if anyone is interested

https://stackoverflow.com/questions/19161310/why-does-wordpress-automatically-output-a-closing-li-or-div-tag-at-the-end-of-ea

I’m not entirely sure it’s a problem. I think it is intentional on the part of WordPress.

I can show you an example. Take a look at the custom callback function mytheme_comment on this page:

https://codex.www.ads-software.com/Function_Reference/wp_list_comments

You’ll see a tag is opened by line: <<?php echo $tag ?> <?php comment_class(empty( $args['has_children'] ) ? '' : 'parent') ?> id="comment-<?php comment_ID() ?>">. However the tag isn’t closed which indicates it is closed automatically by WordPress.

You’ll be able to replicate on a fresh install, default theme, no plugins activated.

Now do you see what I mean? My question is why does WordPress do it this way?

I’m 95% sure WordPress does! The callback is controlled by my theme yes, but there is no </li> in that yet one is being outputted!

Actually there were less warnings than I thought. 2 warnings were being thrown for each item in the list.

These are the two warnings I am getting.

Warning: call_user_func_array() expects parameter 1 to be a valid callback, function ‘my_css_attributes_filter’ not found or invalid function name in /wp-includes/plugin.php on line 173

Warning: implode(): Invalid arguments passed in /wp-includes/post-template.php on line 1057

Just tried on a different site which uses a different theme and no warnings appeared. Not really a big issue as I am now running a loop using WP_Query()