[Anointed]

My concept was to have template files defined just as directly as native wp does it, only using a folder system instead, thus keeping file_exists() to the same level.

As you can tell by the snippet, it is very basic. It works perfectly for standard post_types, as there are only a few template files to define.

A system like bbpress and buddypress is much more involved, thus requiring many new rules. Unfortunately I don’t know either system well enough yet to come up with a rock solid routing platform. I guess by the time I finish with bbpress that I will then have a strong enough understanding to pull this off.

Theoretically it should not break existing installs, as nothing really changes other than file locations, which would be defined anyhow. When plugins come into play it could become an entirely different situation though.

If you don’t beat me to it, I will try to come up with a complete system for bbpress when I finish my project site.

*I don’t think anything would actually have to change within bbpress itself. A custom function would simply reroute the wp template_include() to the new locations. But then again, I am sure you are aware of many other possible problems than I am.

Glad to hear you think it may be feasible.

[Anointed]

I am not running svn, but rev. 3326. I do a manual update each day just to catch up. For instance, you made tons of commits last night so I need another update. Dad is quite sick today so I have to take off for a bit, but will install new vs. when I return home tonight.

For the most part, I have not yet gotten into looking for bugs as I am 100% focused on building a custom template. For now I am not going crazy until things are more stable. It is a tedious job recreating the theme templates on each revision, which means I am leaving the internal logic alone for now.

Once I have a better grasp of what is truly going on, then I’ll post more reports. These reports are just the basic stuff that I am coming across while picturing what I want my bbpress to function like.

[Anointed]

I’ll send you a link to my demo forum when you wake up LOL.

I saw all the new commits in the middle of the night, amazing…

[Anointed]

Would be nice to have a switch to remove a users favorites from users views.

No, I have not setup any forums as private or hidden yet, have not yet made it that far into bbpress.

[Anointed]

@bryan_w

Yes, I believe it is indeed a code problem. I have used a number of different forum systems and ordering the forums always follows the same pattern as what I outlined above.

Meaning, I can use order #1 within each sub-forum, otherwise trying to maintain the ordering is a nightmare.

The problem may lie within ‘nested’ orders of sub-forums.

[Anointed]

That will probably be the long term solution I will use. However, at the moment with bbpress changing so fast I want to make as few changes as possible to ‘core’ bbpress files.

*I’ll ask you later, when I get to that point, what the best function would be in order to do that as efficiently as possible.

You are working at such a furious pace on bbpress that I have already had to ‘rebuild’ my custom bbpress custom templates over a dozen times.

For now I am simply taking the logic out of every bbpress template and wrapping it into my own templates on each revision. Having to remember to change core code as well would be to much to keep up with.

[Anointed]

That will probably be the long term solution I will use. However, at the moment with bbpress changing so fast I want to make as few changes as possible to ‘core’ bbpress files.

*I’ll ask you later, when I get to that point, what the best function would be in order to do that as efficiently as possible.

You are working at such a furious pace on bbpress that I have already had to ‘rebuild’ my custom bbpress custom templates over a dozen times.

For now I am simply taking the logic out of every bbpress template and wrapping it into my own templates on each revision. Having to remember to change core code as well would be to much to keep up with.

[Anointed]

Thanks for the info, kinda figured that was the case.

Because I fully plan on using separate template files for each topic, this is going to get out of hand very fast.

Maybe someday WordPress will look into this a bit more as I can see how this is going to get very messy with very complex themes utilizing a number of template files.

*I’m sorry that I have not yet participated in posting bugs etc.. I am still quite busy messing with template concepts so I have not yet gotten to the point of even trying out the functionality.

[Anointed]

Thanks for the info, kinda figured that was the case.

Because I fully plan on using separate template files for each topic, this is going to get out of hand very fast.

Maybe someday WordPress will look into this a bit more as I can see how this is going to get very messy with very complex themes utilizing a number of template files.

*I’m sorry that I have not yet participated in posting bugs etc.. I am still quite busy messing with template concepts so I have not yet gotten to the point of even trying out the functionality.

[Anointed]

Request:

I am using my own theme and did copy all the files to my themes directory. Everything is working as expected.

What I would like to do is instead of having to copy all the bbpress theme files into the root of my theme folder, is it possible to simply copy the bbpress folder itself into my theme folder?

I am finding that I have a ton of files in my theme root level now, and it is a bit ‘messy’. It would be so much cleaner if I could simply keep all my files in the bbpress folder within my themes root folder.

The problem would only get worse when I add in buddypress custom theme files.

I am also thinking long-term, as if I come back to a site months down the road, it would make it much easier to remember which template is for which plugin etc.. Having all the bbpress theme files in my theme root is making it hard to remember already what does what.

What I am hoping for is:

wp-content/my-theme/bbpress-forum-template-files/

Is this possible?

[Anointed]

Request:

I am using my own theme and did copy all the files to my themes directory. Everything is working as expected.

What I would like to do is instead of having to copy all the bbpress theme files into the root of my theme folder, is it possible to simply copy the bbpress folder itself into my theme folder?

I am finding that I have a ton of files in my theme root level now, and it is a bit ‘messy’. It would be so much cleaner if I could simply keep all my files in the bbpress folder within my themes root folder.

The problem would only get worse when I add in buddypress custom theme files.

I am also thinking long-term, as if I come back to a site months down the road, it would make it much easier to remember which template is for which plugin etc.. Having all the bbpress theme files in my theme root is making it hard to remember already what does what.

What I am hoping for is:

wp-content/my-theme/bbpress-forum-template-files/

Is this possible?

[Anointed]

@JJJ

LOL, I’m an idiot,,,,(should have remembered that from my bp theme days)

Working exactly as expected now.

[Anointed]

@JJJ

LOL, I’m an idiot,,,,(should have remembered that from my bp theme days)

Working exactly as expected now.

[Anointed]

++1 on more directions pertaining to categories.

suggestion:

I noticed that when I create a new category, I give it a title, and also type in a description into the wp post box. The description does not show up on the front end templates.

this does however work for sub-forums, where the description subtext shows up.

I do realize this is simply because the_content() is not called for categories on the template, but it would be a nice core addition.

*Some of us are going to be converting HUGE existing forums, where descriptions of even categories is kind of important.

also:

I am slowly starting to understand the template structure that the plugin uses. Needless to say it is quite different than I expected, and really takes template parts to a whole new level for me.

It would make bbpress life 10x easier, if there were a visual template guide reference available somewhere.

Nothing fancy, just a diagram showing each bbpress page, and the templates used to generate each area of the page.

I know a project like that is kind of a pain in the butt, however it would make life much easier for those of us making huge modifications.

finally:

Does this plugin currently tie into buddypress to replace the existing group forum structures?

-my ultimate goal is to use buddypress with the bbpress pluin. I’m waiting on bp 1.3 before I even attempt to add in bp to my site.

[Anointed]

@JJJ

Yeah the code looks much more user friendly than before. I was actually meaning to ask how this is going to work with bp as that is my ultimate goal. Hoping we don’t have to wait till 1.4 or something… I have not been paying attention to any bp/bbpress news lately, so way behind the times.

I just found bbp_custom_template so needless to say I am in heaven. So long as I have an easy way of using my own template files for each custom bbpress area, life is good.

p.s.

Are there plans on adding in post taxonomies metadata for things like turning forum posts into ‘questions, answers, suggestions, etc’ like getsatisfaction does?

(If not then I’ll do it myself, just don’t want to recreate a wheel already built)

[Anointed]

thank you kindly sir!

Have to say I am quite impressed with what I have seen so far. Not to deep into this yet, but so far so good. Already have bbpress into a fluid 1040 grid working properly including media queries.

Now it’s time to get a bit hardcore with the template changes…

[Anointed]

I’m one of those guys with a tricked out page.php file.

Is there a ‘global’ bbpress forum identifier that I can use?

I was thinking about doing something like this on my page.php

if page is a bbpress page then load file forum.php

else continue loading page.php

This would easily allow me to use a custom forum.php page for styling the forum pages, while still maintaining my ability to use a custom page.php file for everything else.

Anyone have a snippet that does this?

–or a better idea?

thanks