Skip to:

BuddyPress stopped working with Thesis on upgrade from 1.8 to 1.9

  • Jeremy


    Hi I am using WP 3.8 with the Thesis theme and Buddypress 1.91.

    Buddypress was working fine with the Thesis Theme on version 1.7-1.8 with the addition of the awesome theme compatability, but when I upgraded to 1.91 it no longer works.

    I get some output basically this:

    Jeremy Francis – Online Design Specialist”>Jeremy Francis – Online Design Specialist

    active 2 seconds ago ActivityProfileSites 2Notifications 0Messages 0Friends 0Groups 0Settings PersonalMentionsFavoritesFriendsGroups Show: Everything Updates Posts Comments Friendships New Groups Group Memberships What’s new, Jeremy? Sorry, there was no activity found. Please try a different filter.

    But it is pure text inside a <p> tag and there are no links at all.

    Here is a link to my site:

    it is in development so there are no links on the site to the buddypress compnents but I use standard naming for the other pages, the other pages ie etc.

    I can confirm that it worked in version 1.8 I rolled back the plugin and everything worked just fine.

Viewing 12 replies - 1 through 12 (of 12 total)

  • modemlooper


    I’m not sure why but when you are in the page admin for a BuddyPress page can you select a different page template? Looking at your source code in browser there is reference to a class “teaser” which is making me assume its showing a page excerpt



    Yeah it uses just the default page temaplate, It worked fine in 1.7 and 1.8 but now not so much in 1.9…



    I have the same problem and also no freaking clue how to solve this. Previous versions worked perfectly and this update screwed it up basically.



    I’ve got exactly the same problem. It would be awesome if someone could help!



    This is probably related:

    Thesis probably has an unusual method for displaying page content. Atahualpa, another theme, suffers from the same issue.

    Since Thesis is a paid theme, I do not have access to see how their templates are set up.

    John James Jacoby


    It does, as do many other robust theme frameworks that bypass WordPress’s template loader with their own. I’m conflicted on how much we can realistically support themes that deviate so far from the norm.

    Previous to 1.9 we were purposely doing it wrong for the sake of maximum compatibility. In 1.9, we fixed up a few things, that now uncover pretty fatal flaws in several themes. I’m torn, but I think it’s up to theme authors to decide their level of plugin compatibility, rather than the other way around where theme authors would expect every plugin to adapt to their proprietary output system.




    I’m using Attitude theme (which is free) with the same problem. Do you have any recommendation on how to fix this issue? Or a suggestion on how to communicate the issue to the theme developers?



    As with herrieher1, I am experiencing the same issue with Theme Horse’s Attitude theme. I’ve had roll back to 1.7.2 as I can find an original zip file with anything new pre-1.9 to install. Things are working fine again as they did prior to the last release for now.

    Any thoughts or help on this would really be appreciated…

    > I’m conflicted on how much we can realistically support themes that deviate so far from the norm.

    I see no real conflict to be resolved, it’s impossible for BP to take into account unknown divergences from the core template api WP provides, if theme authors want to create something non-standard then sadly that’s their problem and unfair to expect BP to have to try and deal with this. The best BP can do and is doing pretty well is to tie in as much as possible to the set WP template approach and if all themes did the same – and frankly they probably could regardless of proprietary approach to frameworking – then this would be a non issue.

    >that now uncover pretty fatal flaws in several themes

    Flaws that existed and have existed in many themes that do their own thing.

    Where that leaves things is sadly fairly and squarely in the theme authors court to try and help provide a solution for template issues.

    On a sidenote on another thread I noted a response relayed from a theme author to the user on enquiry of how to resolve their theme issue that the theme author couldn’t possibly support every third party plugin issue that happened along! It’s worth perhaps pointing out to any theme authors that might happen past this thread that there are plugins and there are plugins that really are best described as modules that extend WP they transcend the notion of a simple plugin and leverage the WP API to it’s fullest, these plugins, and I’m thinking of BuddyPress and bbPress here are in wide spread use, and really the smart theme author might be advised to actually test their themes with both these ‘plugins’ to gauge the level of support the theme offers and where possible improve it!

    Obviously the above isn’t a great deal of help to those of you having these issues, but this forum is going to struggle to help on these sorts of issues being it’s primary purpose has to be directly related to BP issues and third party themes especially premium ones are something we can’t deal with due to lack of knowledge on how they are constructed.



    Thanks to Qball7686 for posting a freely-available theme that runs into this problem.

    I have a tentative fix for this. See:

    If people who are having problems with their themes can test this fix and let us know if that works for them, that would be great.



    I wrote my own theme and am always trying to do things the right way but initially things were not working correctly with bbPress or BuddyPress. I now realise was my theme using the_excerpt rather than the_content on the special pages.

    I’d read the topics in the buddypress codex on theme support but these mainly addressed the issue of altering pages using the template selection rather then explaining what a theme author needs to do to make their theme work properly with bbPress or BuddyPress. Just explaining how it injects its content into pages (by hooking the_content) is not immediately obvious to the newcomer.

    In my theme I had been using is_singular() to know when to show content rather then expert and use parameterised preferences for each post type for when is_singluar() was false.

    Simply changing this test to (is_singular() || is_page()) suddenly turned my theme from incompatible to reasonably compatible. The “/forums” slug still did not work properly but after searching around I discovered the is_bbPress() function and expanded the test to:

    (is_singular() || is_page() || (function_exists(‘is_bbPress’) && is_bbPress()))

    There may be other tricks and gotchas I haven’t found yet, but as I say it would be really nice to have a topic directed specifically at theme authors to make sure they know what needs to be in place to make things work.



    Hi, I’m experiencing the same problem using the Stargazer theme from themehybrid, and the problem persists even after applying the fix above. It’s also a free theme that can be found at:


Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘BuddyPress stopped working with Thesis on upgrade from 1.8 to 1.9’ is closed to new replies.
Skip to toolbar