Forum Replies Created
-
@anointed – In a word, no.
WordPress custom post types only know to look for their files in the root of the theme folder, and the same goes for page templates as well. For now if you want a totally customized theme, those files need to live in the root. I did my best to minimize the number of files in the root, and instead split them up into template parts in the /bbpress folder (because I want the same thing you do.)It might be possible to hook into the template loader, see what the request is, and force it to look into a different folder, but there’s no possible way to do it at all with page templates; it’s actually purposely disallowed to prevent the theme from having to scan every file inside every subfolder to find them.
@anointed – In a word, no.
WordPress custom post types only know to look for their files in the root of the theme folder, and the same goes for page templates as well. For now if you want a totally customized theme, those files need to live in the root. I did my best to minimize the number of files in the root, and instead split them up into template parts in the /bbpress folder (because I want the same thing you do.)It might be possible to hook into the template loader, see what the request is, and force it to look into a different folder, but there’s no possible way to do it at all with page templates; it’s actually purposely disallowed to prevent the theme from having to scan every file inside every subfolder to find them.
@jarledb – One of the unique challenges of creating a plugin with a large volume of users is catering to the 80% of users that want to turn it on, and not really mess with it. Different people will want different kinds of login and registration areas on their sites, and everyone with an opinion about where to put them why, is right. Some say sidebar, some say in the content area to draw attention to it, some say tuck it in a drop down menu, etc… All great ideas, but what’s the majority? The majority want it easy, and I think widgets are the easiest way to go right now without making everyone have a login/register page on the forum index of their sites.
Regarding ip-banning/anti-spam, you’re probably safe to hold off for a little bit. There’s no doubt these solutions are going to be needed eventually, and if someone takes the liberty of making an awesome plugin to help out, I’m all ears on how I can help bbPress core work better with it.
@jarledb – One of the unique challenges of creating a plugin with a large volume of users is catering to the 80% of users that want to turn it on, and not really mess with it. Different people will want different kinds of login and registration areas on their sites, and everyone with an opinion about where to put them why, is right. Some say sidebar, some say in the content area to draw attention to it, some say tuck it in a drop down menu, etc… All great ideas, but what’s the majority? The majority want it easy, and I think widgets are the easiest way to go right now without making everyone have a login/register page on the forum index of their sites.
Regarding ip-banning/anti-spam, you’re probably safe to hold off for a little bit. There’s no doubt these solutions are going to be needed eventually, and if someone takes the liberty of making an awesome plugin to help out, I’m all ears on how I can help bbPress core work better with it.
@SHope – You’re okay.
It sounds like you’re using the shortcodes correctly, but that something else isn’t working. I think I’m going to build in a shortcode helper, because I realize finding the ID isn’t the easiest thing to do.On the pages you’re using the shortcodes on, does anything appear where the shortcodes should be?
@SHope – You’re okay.
It sounds like you’re using the shortcodes correctly, but that something else isn’t working. I think I’m going to build in a shortcode helper, because I realize finding the ID isn’t the easiest thing to do.On the pages you’re using the shortcodes on, does anything appear where the shortcodes should be?
@jerledb – Login/register are supported via page templates, there is a login widget, and eventually shortcodes too. A register widget is a nice idea but leads way to lost-password and activation widgets, none of which will make it into 2.0.
Spam isn’t really handled yet, since there’s no one spamming forums that don’t use software that isn’t released yet.
There is a Trac ticket regarding Akismet integration, but either Akismet will need to be updated or a special version of Akismet to concentrate on post spam (which isn’t really a WordPress issue.)Regarding IP addresses, there are WordPress plugins to help with this, and WordPress multisite comes with this kind of functionality baked in. Traditionally WordPress doesn’t handle spam at a user level, since registered users are typically already trusted to some regard. We run into this issue a little bit even here at bbpress.org. bbPress does log the IP address of every topic/reply that is created, so a plugin can use that to check against a ban list or something.
@jerledb – Login/register are supported via page templates, there is a login widget, and eventually shortcodes too. A register widget is a nice idea but leads way to lost-password and activation widgets, none of which will make it into 2.0.
Spam isn’t really handled yet, since there’s no one spamming forums that don’t use software that isn’t released yet.
There is a Trac ticket regarding Akismet integration, but either Akismet will need to be updated or a special version of Akismet to concentrate on post spam (which isn’t really a WordPress issue.)Regarding IP addresses, there are WordPress plugins to help with this, and WordPress multisite comes with this kind of functionality baked in. Traditionally WordPress doesn’t handle spam at a user level, since registered users are typically already trusted to some regard. We run into this issue a little bit even here at bbpress.org. bbPress does log the IP address of every topic/reply that is created, so a plugin can use that to check against a ban list or something.
Just fixed a bug in the breadcrumb root that is the “root” cause of what you are experiencing. This will be fixed in Beta 2. Thanks for bringing it to my attention.
