Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 25 replies - 801 through 825 (of 3,962 total)
  • @hnla

    Participant

    @jianzhi
    I needed this a while back for a bunch of existing users, so ran up a simple quick script to do this, wouldn’t run it on a production site but worked in my test environment for my purpose, you can copy and run if it helps:
    https://github.com/hnla/force-show-bp-users/blob/master/force-show-bp-users.php

    @hnla

    Participant

    @shameermohamed50 the Codex is your friend, do have a read of some of the guides there as they will answer a certain amount of your questions in setting up BP and bbP

    @hnla

    Participant

    Marking as ‘resolved’ then, re-post if further issues arise.

    @hnla

    Participant

    $post is available as soon as you hit a post/page so doesn’t have to be in the loop

    Think my earlier example holds good for passing the id to bp_has_profile but I’d probably do $user_id = $post->post_author;

    @hnla

    Participant

    lol but do have a read of the two detailed ones written to help people work with theme compat.

    @hnla

    Participant

    can’t elaborate as already written a fairly detailed page on the first round of theme compatibility so would be repeating myself for no good reason 🙂

    Look under developers > theme (something) on the right menu list in the codex.

    @hnla

    Participant

    This would work (& does work):
    bp_has_profile(‘user_id=’ . get_the_author_meta( ‘ID’ ) )

    or you could grab the user id from $post->post_author

    I’m assuming you’re running this in a single post loop.

    @hnla

    Participant

    You should drop template pack really.

    Theme compatibility already provides for a custom bp version of page.php ‘buddypress.php’ in that you can specify named sidebars. BP 1.8 will increase the flexibility of theme compat templates further by allowing you to specify index pages with full markup, or templates called on certain actions/component views.

    It’s all written up in the codex.

    In reply to: Get user ID of Profile

    @hnla

    Participant

    bp_displayed_user_id()

    @hnla

    Participant

    Not really sure how this is relevant to this support forum, doesn’t sound BuddyPress related?.

    @hnla

    Participant

    @themefusion wrote: Avada does work with BBpress
    That’s good, however the thread was referring to BuddyPress not bbPress 🙂

    @hnla

    Participant

    Could always overload the styles and make it responsive? In it’s ‘native state’ it may never be as these things can tend to be reliant on the parent themes actions.

    @hnla

    Participant

    No help is ever urgent on voluntary free help forums! 🙂

    This sounds like an issue with woocommerece if as you say it providing some form of registration, so have you also contacted their support & asked whether they have a notion of why this happens?

    Not sure what you mean by go into the editor of the register php it tells me that buddypress registration is disabled Can you elaborate on the ‘editor of the register php’ and what is telling you buddypress registration is disabled, WP handles enabling / disabling registration, BP just provides a page/form that can be navigated to if a blank registration page is setup.

    @hnla

    Participant

    Forums output is the responsibility of the bbPress plugin and as of BP 1.7 all handling of templates belongs with bbPress with BP no longer bundling the pared down version for groups that it used to. Look at the bbPress plugin directory templates for the files you want – more info on overloading files for modifying should be available on the bbPress site.

    In reply to: BuddyPress Group Page

    @hnla

    Participant

    @disqusnow BuddyPress is a plugin, plugins live in the WP directory /wp-content/plugins/ not in the directory /wp-content/themes/

    BP historically ran it’s default theme from it’s plugin struture and still does along with the new theme compatibility files /buddypress/bp-templates/bp-legacy/

    If you have a custom theme and you want to edit the bp theme compat templates then you must copy them over to your theme and edit them from there ( to confirm as mentioned earlier the actual WP pages are placeholders you do not enter content in them.)

    Please see the codex for more in depth guides to theme compatibility and overloading the templates to your theme.

    @hnla

    Participant

    Check the Codex and BuddyPress release notes! As of 1.7 there is a theme compatibility layer built in to BP that allows it to work with most themes – activate your theme, activate BP, that is about all you have to do bar a few style mods if required to bed BP screens in.

    @hnla

    Participant

    it is in the Codex!

    Originally BP used a stripped down version of bbpress built in, now that is removed and bbPress plugin provides support for BP groups forums, there is a guide on transitioning over.

    https://codex.buddypress.org/user/buddypress-site-administration/migrating-from-old-forums-to-bbpress-2/

    @hnla

    Participant

    No not going to say go with bp-default theme but am going to ask why on earth the template pack has been used – it’s now virtually obsolete, 1.7 introduced theme compatibility, it’s been the highlight of that release stream and much talked about and for all new custom themes is all you need running really, if you need to overload templates then that is entirely possible (read codex guides) and 1.8 will refine & expand that ability to manage templates. Talk to your developers get them to switch, they ought to have read up on latest release and best approach to themeing really.

    @hnla

    Participant

    <font> is a deprecated & obsolete element and has been since the very early days of Standards and separation of presentation from data, if you have to add style try and do so from stylesheets, but if having to work directly on markup add the styles as ‘inline’ using the style attribute.

    In reply to: Creating New Plugins

    @hnla

    Participant

    In other words the function that essentially attempted to call into itself other core files from WP core & BP core for no real good reason, I’ve seen that function before as well and puzzled as to why someone thought that was necessary or good.

    The fundamental approach of loader.php as the top level file still holds good as common and best practise, with your header,main checks, language local, and any functions to run on activation or deactivation etc.

    @hnla

    Participant

    @number_6 this is where – like the previous thread – we really need posters to detail their setup first before asking questions.

    You are slightly confusing BP with your theme, your theme provides many options and conditions as in this particular instance.

    This widget is part of the Custom Community theme and found in their core includes, modifying would require you to copy it out to another safe area, rename it, make mods in order that your changes weren’t overwritten if/when you upgrade the main theme files, so a child theme is called for and your widget copy placed in a new functions.php file in your child theme.

    @hnla

    Participant

    You don’t edit the dashboard BP pages, they are simply placeholders for BP, you mention the BP codex did you not see this page? :
    https://codex.buddypress.org/developer/theme-development/a-quick-look-at-1-7-theme-compatibility/

    That should help.

    In reply to: Creating New Plugins

    @hnla

    Participant

    Well think the point here is going to be someone sorting out that codex entry then with a more complete and in depth examination of the check and load process, especially given people are receiving messages from WP repo pointing to the original post stating to use bp_loaded.

    In reply to: Creating New Plugins

    @hnla

    Participant

    But you haven’t really run a check to see if bp is loaded, at least not in the loader file which is why I think you have that response ( although the response does direct you to our codex entry showing the approach you have followed, so that doesn’t really make sense it smacks of an automated response or worse someone just zapping off the message without thinking? ), you simply require your main file without any checks then do a add_action on bp_include, in your main file you do use that function I’ve seen before to try and require the bp-loader and if not post a message which is fine it works but I wonder whether it’s better to move all your checks to your main loader file?

    I have to admit I’ve always puzzled the best approach, rather annoyingly you can check half a dozen of the better BP developers and they all do something different, I would favour a consensus as to the best approach and have that written up as a best practice to follow in the codex – personally I’ve tried a variety of approaches all work, on my one wp repo plugin I used same loader.php approach you have requiring and add_actioning on bp_include hook.

    Also originally the check was not so much to prevent ones plugin from loading but to prevent white screens if BP was deactivated with your plugin still running.

    @hnla

    Participant

    You’ve chosen to go down the DIY route, I’m afraid that with that comes a degree of learning that must be undertaken. Generally the codex talks to a novice level so things are never that complicated but other than as Henry suggested in hiring someone to do the move you will need to bite the bullet and gain that experience, install a second test WP site use that to practice changing the DB, use a hosts file to manage domain extensions so you can work with domains at a localhost level.

Viewing 25 replies - 801 through 825 (of 3,962 total)
Skip to toolbar