Skip to:
Content
Pages
Categories
Search
Top
Bottom

Artisteer Buddypress theme compatibility

  • Avatar of Sizons
    Sizons
    Participant

    @sizons

    Hi,

    I’m using version 4 of Artisteers Theme creation software where I export a very nice customized theme for my clients’ website. My problem is that the headers (From Chrome’s inspect element function: item-list-tabs activity-type-tabs) are all overlapping to my two sidebars, my theme is a three column theme with a header and footer as well.

    I have run through the bp-Compatibility steps and on step three where I have to adjust the layout through FTP connectivity, I tried method 1 and 2 without pass. My major problem is that my page.php and index.php both have no div tags, just some php code though I was expecting a similar batch of code to the index.php file I find inside a folder like activity for example, where there is a lot of HTML along with the PHP code.

    Following is my page.php code:
    <?php get_header(); ?>
    <?php get_sidebar(‘top’); ?>
    <?php

    if (have_posts()) {
    /* Start the Loop */
    while (have_posts()) {
    the_post();
    get_template_part(‘content’, ‘page’);
    /* Display comments */
    if (theme_get_option(‘theme_allow_comments’)) {
    comments_template();
    }
    }
    } else {
    theme_404_content();
    }
    ?>
    <?php get_sidebar(‘bottom’); ?>
    <?php get_footer(); ?>

    I also tried to copy the header, footer and sidebar files and save them as sidebar-buddypress.php and so on but saw no difference, the site’s buddypress headers were still overlapping with my site’s two left and right sidebars.

    I have been struggling with this issue for so long, I even tried to create a css folder and copied the bp-default.css and called buddypress.css as I was instructed by one of your support documents on this site, when I changed any of the css I saw no change to the style on the page as I used this with the inspect element feature of the Chrome Browser.

    I really have no clue how to fix this now as it also affects some of the buttons on my site, causes them not to drop-down on my All-In-One-Event calendar plugin controls, though when I use the default buddypress plugin it works fine.

    Please help me, I wish there was a source of information about this that would just work, but the documentation I have found expects particular files which turn out to look different from what I have on the site’s files – Just a reminder, my theme was created using Artisteer 4.0 software.

    Appreciate any assistance.

    Regards [Addition: I am using the latest buddypress 1.8 (Upgraded this morning) and the latest wordpress 3.5.2]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Avatar of Hugo
    Hugo
    Moderator

    @hnla

    A source of documentation that just works? not sure what that means , there are a couple pf codex docs that go into fair detail regarding how to deal with theme compatibility and customising not sure we can make them any more explicit really, there is a certain amount of knowledge one just needs as regards generic PHP amd markup in order to be able to work effectively for ‘clients’

    My major problem is that my page.php and index.php both have no div tags
    Not really sure what you mean here, think you need to explain in detail what file structure and locations you are trying to work with before trying to see where you are getting confused.

    Avatar of Sizons
    Sizons
    Participant

    @sizons

    I’m sorry to have taken such nab with low emotional intelligence at the documentation, truly I am at a loss of understanding as to why such a powerful product is available under a GPL license, I guess I don’t fully understand the open source philosophy (PS: I’ve been reading your posts over the years Hugo and am a great fan, pity I started off on the wrong foot) –

    That aside, in my retraction of such careless words born out of frustration, I must say that the documentation seems very professional and concise, though I also feel it could be a little more detailed.

    I’m personally an average everything, I did a multimedia diploma that I dropped out of and never really excelled at anything. I did php during those days too but just barely passed with a 50% or something.

    Nevertheless, it is my view that the documentation should be able to lead someone with at least my little experience to getting the job done, it should be just a little bit more detailed, I would suggest print-screens of every step just to be safe.

    “Not really sure what you mean here, think you need to explain in detail what file structure and locations”

    Okay, under fixing alignment there is a sentence:

    Open up the page.php file (if this does not exist, use index.php). Make note of the HTML template structure of the file, specifically the <div> tags that surround the content and sidebar.

    When I open my page.php file from my FTP client at the root of my theme folder what I see from page.php is the following code:

    <?php get_header(); ?>
    <?php get_sidebar(‘top’); ?>
    <?php

    if (have_posts()) {
    /* Start the Loop */
    while (have_posts()) {
    the_post();
    get_template_part(‘content’, ‘page’);
    /* Display comments */
    if (theme_get_option(‘theme_allow_comments’)) {
    comments_template();
    }
    }
    } else {
    theme_404_content();
    }
    ?>
    <?php get_sidebar(‘bottom’); ?>
    <?php get_footer(); ?>

    In that code, (Forgive me if my understanding is lost here) there is not even one Div tag, infact, there is no HTML code in that file at all, even the index.php(the one in my themes root folder) file looks closely similar to the file above, here is its contents:

    <?php get_header(); ?>
    <?php get_sidebar(‘top’); ?>
    <?php
    if (have_posts()) {
    /* Display navigation to next/previous pages when applicable */
    if (theme_get_option(‘theme_’ . (theme_is_home() ? ‘home_’ : ”) . ‘top_posts_navigation’)) {
    theme_page_navigation();
    }
    /* Start the Loop */
    while (have_posts()) {
    the_post();
    get_template_part(‘content’, get_post_format());
    }
    /* Display navigation to next/previous pages when applicable */
    if (theme_get_option(‘theme_bottom_posts_navigation’)) {
    theme_page_navigation();
    }
    } else {
    theme_404_content();
    }
    ?>
    <?php get_sidebar(‘bottom’); ?>
    <?php get_footer(); ?>

    Perhaps I am using the wrong page.php file, but that would not make sense because I used the directory address provided by BP-Compatibility on the fixing alignment section.

    Avatar of Hugo
    Hugo
    Moderator

    @hnla

    The docs can always take improvement, and I think no one involved with them would claim they are anywhere close to covering all that’s required, but writing them can be very time consuming . The theme compat ones that exist, I thought pretty much covered the detail necessary, but as in all things can always stand reviewing and improving.
    In your opening post it struck there was a possible level of confusion between the older approach to custom themes using template pack plugin and theme compat as of 1.7. ?

    Essentially if allowing BP to run with the newish theme compatibility ( i.e you do not select bp-default theme, or you do not have any bp directories in the theme root e.g /my-theme/members/index.php ) then BP component screens should fit to match a themes content area. In this sense one doesn’t need now to worry about the markup structure as BP uses what exists in page.php (or any of the proscribed file names it looks for first) So here the important question is to ask whether it’s possible you are mixing BP templates i.e some in your theme root, some in theme compat directory – in your theme the only place you should have BP templates is located within a top level directory /my-theme/buddypress/ or /my-theme/community/

    In your page.php example the important section is the get_template part that includes the page content loop that’s where /what BP grabs to inject it’s data to.

    Now what isn’t known is how your chosen theme is managing styles for those sidebars, but if you want absolute control in being able to configure a primary template file for BP screens then you can copy page.php rename to ‘buddypress.php’ and locate that in /my-theme/buddypress/ now in that file you may call specific sidebars as in get_sidebar(‘buddypress’) along with a new sidebar sidebar-buddypress.php

    At the end of the day I think the initial issue to resolve is the (possible) confusion between the two ways of managing BP templates and that you probably want to ensure that full theme compatibility is being allowed to run ( again the bottom line to ensure that this is the case is that one has NO BP templates in the theme whatsoever, letting BP handle injecting it’s content via whatever files the theme provides )

    Avatar of @mercime
    @mercime
    Keymaster

    @mercime

    I have run through the bp-Compatibility steps and on step three where I have to adjust the layout through FTP connectivity, I tried method 1 and 2 without pass.

    @sizons Step 3, method 1 and method 2 … suspiciously sounds very very familiar and used in relation to the BP Template Pack – BP Compatibility process used up to BP 1.6.10.

    If this is the case, please deactivate BP Template Pack plugin and remove the 6 BP Template folders from your Artisteer theme folder in server. With BP 1.7 and above, BP is compatible with nearly all WP themes without lifting a finger. Now check how the BP pages are showing up in your theme.

    If you did not use the BP Template Pack plugin, then I will exit stage left and leave you with @hnla :-) Before I do, read up on hnla’s excellent article on BP Theme Compatibility http://codex.buddypress.org/developer/theme-development/a-quick-look-at-1-7-theme-compatibility/ and if you want to customize your theme further, check out r-a-y’s awesome article http://codex.buddypress.org/developer/theme-development/template-hierarchy/

    Avatar of Sizons
    Sizons
    Participant

    @sizons

    Thank you ever so much @mercime, I would have never known to deactivate bo compatibility. My buddypress pages seem to be fine now, and I am using r-a-y’s awesome article to just add a few touch ups to the buddypress stuff. I was so frustrated by this issue and everywhere I looked I could not find a solution, I was starting to think I am stupid. Thank you thank you thank you…

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

You must be logged in to reply to this topic.