There is no such plugin or ability yet (or any expression of need for such an ability).
If you know how to code in PHP you might look at the experimental tag filter I made inside of the Hidden-Forums plugin to see how such a query would be done. You could then use the query to create a custom view for the topic results.
Hey _ck_,
Well I threw both files into diffmerge. The ‘do_action and apply_filter’ code is there. My file was missing ‘php echo $key’ – but I really don’t know if that matters or not.
I think I might give it a while and see how it goes without the plugin. If I find I can’t live without it I may be back!
BTW, I spent some time on your site last night. The top 100 list was very interesting and inspiring!
Thanks for the hard work!
Whew! Clearing cookies did it. Thanks
I just upgraded to WP 2.71 also, should have mentioned that.
It’s possible because I was testing it on 1.0 that 1.0 automatically escapes the mysql values passed and that 0.9 does not. I can’t remember.
Try adding this before the $bbdb->query
$pmtitle=mysql_real_escape_string($pmtitle);
$message=mysql_real_escape_string($message);
and see if it helps or if it just add slashes to your text instead and breaks it.
It may also be a quote problem but I thought the bbpress pre/post text filters should encode quote or any other problematic characters.
Try this one
<?php echo ( get_topic_author());?>
Something I just realized and I should have noticed / asked sooner.
You are using a custom template. A very common problem with plugins when you use custom templates is they have accidentally removed some critical actions / filters.
Open up your register.php template and open up the original bb-templates/kakumei/register.php template.
Compare the two, specifically looking for any do_action or apply_filter that you are missing.
In your case, specifically
<?php do_action('extra_profile_info', $user); ?>
but I suspect you have that, or you’d see nothing from the plugin.
So to be clear, it’s happening after you successfully submit it, not the message on the same page you type in the password right?
The password error only happens for two reasons, either the primary password doesn’t match the confirmation or the password is less than 6 characters.
The $_POST data must be making it through because you’d get a different error.
I assume you tried various passwords and aren’t using multibyte (unicode) password or with slashes in them.
I guess it would be a good alternative to akismet (or even in addition to).
Your code can be cleaned up and condensed considerably.
It also could benefit from some security checks on the $_POST data being injected into the url.
Here is an untested, condensed version with some mild security checks on the $_POST
http://pastebin.com/f7a50d82a
(there is also an alternative to curl in there for the 50% that don’t have it on their server)
I took out some of the extended manipulation of the returned data that you didn’t need.
Sorry, looks like I left some customized leftovers in there.
Simply remove line 5 entirely or comment it out like this
<?php // my_views_header(); ?>
I installed bbpress and went to activate it and got the following message on the plug-in page…
// Bail here if no key is set
if (!bb_get_option( 'akismet_key' ))
return;
I’m assuming this has something to do with my API key? No Idea.
-D
hello! o hola en español.
You can try with the version 1.0 alpha, it works fine!!
Hola/hello!
If someone else have the same problem try to use the version 1.0 alpha version!
it works!
Hola
I check the server it is using php 4.4.8 and mysql 5.0.45 and i dont have integrated anything…jaja
I tried to installed in a empty directory.
there is another version of bbpress?
It seems it should be pretty easy to modify the plugin. Just change the references to the table bb_online to the proper $bbdb->online and I think it should be fine. Or, for yourself, you could just hard-code the table prefix for your installation, but I would say that’s bad form and not portable.
To make my description easier:
view.php gives: view-page
view.php?view=port gives: view-page too.
I want view.php?view=port to give: port-page
Thx
I get the same error with that code, too. Is it supposed to be that short? I’m a tad confused, sorry.
If you thought I said the whole file was blank, I did not mean that. The line is, and it’s after that code.
What’s different between the two codes?
Thanks for trying to help! Hope we can fix this.
Probably by changing this: 'show_author' => 1, Make the 1 a 0?
A functions.php should be like this:
<?php
function bb_nonce_ays( $action ) {
$title = __( 'bbPress Failure Notice' );
$html .= "t<div id='message' class='updated fade'>nt<p>" . wp_specialchars( bb_explain_nonce( $action ) ) . "</p>nt<p>";
if ( wp_get_referer() )
$html .= "" . __( 'Please try again.' ) . "";
$html .= "</p>nt</div>n";
$html .= "</body>n</html>";
bb_die( $html, $title );
}
?>
Hi 
Well, it would be as simple as changing the existing CSS-rule. Just remove the #front-page parent declaration so that the rule applies to all pages containg the #hottags div
#hottags {
position: absolute;
top: 0;
left: 0;
width: 150px;
overflow: hidden;
}
a democratic voting by users would be cool, since it’s web 2.0
You would use either
forum_link($topic->forum_id); // self echos
or
$link=forum_get_link($topic->forum_id); // returns a string
what you probably want is:
<a href="<?php forum_link(); ?>"><?php forum_name(); ?></a>
If you have a complete new php file that acts like a new page, you can add it’s location with the below code, BUT I want to rename a existing php file. The problem is that its a filtered page: view.php?view=port. The problem is that this is still seen as view.php. How do I change this so that view.php?view=port is seen as a total new page so that the code below works and the location is added?
function bbport_location() {
if (bb_find_filename($_SERVER['PHP_SELF']) == "view.php?view=port"):
return "port-page";
endif;
}
add_filter( 'get_bb_location', 'bbport_location' );
function is_bbport() {
if ( 'port-page' == get_bb_location() )
return true;
else
return false;
}
We really should backport the fix that is in 1.0 to 0.9 for our international friends.
I can’t remember what the function was that had the problem but I believe it was
function htmlspecialchars_decode
there may be others.
Unfortunately those functions are not pluggable but you could try replacing them from 1.0 into 0.9 and use SVN to handle upgrades which might work around it.
Made a note on TRAC https://trac.bbpress.org/ticket/1059