Change function names, filters to resolve conflict with wordpress and be consistent

bb_get_title is for the title of the page, get_user_title is for a user's title ( "Moderator" or some custom value, for example); very few of the other user template functions are prefaced with bb_.

Anyway, yeah, let's reexamine our function naming for .80 or (more likely) 1.0.

Can someone take a stab at some guidelines for the function names and hooks..

any takers?? :)

anyone?

Just some things off the cuff. Not all of these are specifically about function names.

1. Any new functions should by prefixed with bb_

1. bb_get_X always returns

1. Template functions should use query style args bb_template_functions( 'key=value&so1o=awesome' ); See helper function bb_parse_args() and bb_user_search() for example. Other functions should use this format when appropriate (more than a couple args).

What else?

• bb_x displays x
• there is another group of functions that we need to tackle/standardize. these are the links.. we have to differentiate between link and url..

bb_get_topic_url

 returns 'http://www.somehost.com/topic.php?id=1'

bb_topic_url

 prints 'http://www.somehost.com/topic.php?id=1'

bb_get_topic_link($link_title)

 returns '<a href="http://www.somehost.com/topic.php?id=1">$link_title</a>'

bb_topic_link($link_title)

 prints '<a href="http://www.somehost.com/topic.php?id=1">$link_title</a>'

• all template functions have to have a filter before return or display

also one question - do we need to deprecate old functions for next x minor releases or till the next major versions or just drop them coz we are under 1.0?

do we want take this up?

also advise on back ward compatibility

Any functions we rename, we need to put into deprecated.php. We may be able to drop them for 1.0.

so

a_fuction() {
     return bb_a_function();
}

Paying careful attention to globals and arguments.

I like your link/url differentiation. What will it break?

there are a couple of urls and links like the topic_link, author_link... we'll take it as they come and discuss.. i'll start working on these..

is there a thought about filter hooks' backward compatibility

We can probably break filter backward compatibility if we have to.

Can you throw up a piece to look at?

Moving this to 1.0.

ticket patch

just added a patch for the ticket.. this includes partial changes..

question.. what about the filters in the functions which we'll change the names for.. how do we maintain backward compatibility?

some of the function we have to change are high profile like get_forums

(In [792]) bb_ goodness from so1o. re #528

We can change filter names. There's few enough plugin developers still that we can get the word out pretty well. We can also include deprecated filters in deprecated.php:

function something() {
    return apply_filters( 'something', bb_something() );
}

where appropriate.

I applied your patch, so1o, but took out some things from deprecated.php that are really only used internally. Also, those functions defined in compat.php (there's only one at the moment) are function available in PHP5 but not in 4. So they don't need renaming.

need to resolve the conflict of pre_post_status filter in wordpress and bbpress.