Skip to:
Content
Pages
Categories
Search
Top
Bottom

Forum Replies Created

Viewing 25 replies - 576 through 600 (of 3,962 total)
  • In reply to: Layout is to narrow

    @hnla

    Participant

    42 minutes?? Please do not bump posts until at least ~24 hours has passed 42 minutes is definitely far far too soon to be bumping your thread seeking help. please remember this forum is not a service nor is it a paid for service, threads are entirely answered by a volunteer community. The forums purpose is to attempt to lend some support for BP issues, however third party themes do not necessarily fall under that category, styling of themes is something users are expected to handle or the themes authors, also note that not all themes behave correctly with BP due to the way they have been constructed.

    If you have a little patience someone may be able to take a look and offer some advice to help your out.

    @hnla

    Participant

    grab one from trunk to be safe?

    @hnla

    Participant

    You’ll need to provide a little more detail than that. ‘tab’ ? what do you mean by tab, what theme are you using .

    have you actually tried a manual url? /wp-login.php ? or /wp-admin/

    @hnla

    Participant

    closed – Duplicate.

    @hnla

    Participant

    Well I could find it and appeared to be able to change it.

    @hnla

    Participant

    And have you enabled ‘Site Tracking’ in BP settings?

    @hnla

    Participant

    Examine your themes sidebars, functions.php and plain old widgets to try and fathom where the tagcloud is being set from if it’s custom i.e not just the WP widget and you can find it then you should be able to pass it args as in the link above but equally editing a core theme file will suffer same fate as any ‘core’ file that can be updated so always try and work in child themes.

    In reply to: Registration Process

    @hnla

    Participant

    You’ll need to look at the core function that filter ‘bp_core_signup_send_validation_email_message’ belongs to to see what has been missed in the return;.

    @hnla

    Participant

    Please never advise people edit core files. Core files must never be edited as you may cause unintended issues to develop and changes will be overwritten on update.

    The code Henry showed is how one displays a tag cloud in template files https://codex.wordpress.org/Function_Reference/wp_tag_cloud

    The question is how your theme is handling this, directly coded to sidebar/s? some function that is called in some manner? hard to tell how the theme manages it so you really need to address the question to the theme author, also it not really a BP question really as this is a WP function.

    @hnla

    Participant

    @cc-cailin It’s stated at the very top of the WP plugin forum page you link to!! the statement reads ‘please don’t use’

    This was the whole point of all the work that went into BP 1.7 for theme compat. Please read those links provided so you understand how things work now, it’s also worth following the BP blog and even bpdevel site to keep up to date with developments.

    In reply to: activity stream gone

    @hnla

    Participant

    never ever spaces never ever caps, *nix has never allowed spaces in file names it is only MS Windows/DOS that broke that rule; names in *nix are case sensitive so File.php is different from file.php

    @hnla

    Participant

    Guess they’ll point to the same resource, I’ve always checkout on the url I mentioned never really though much about it.

    @hnla

    Participant

    Closing thread. Duplicate of:
    https://buddypress.org/support/topic/warning-message-when-activated/

    Please don’t open more than one thread on a topic.

    @hnla

    Participant

    @henrywright-1
    I think on balance I would tend now to favour going the theme compat route, as the process best to follow in all theme/site building respects, we added extended capabilities with the template hierarchy which make it more useful and the templates and styles were updated and improved.

    But the other approach is perfectly valid and leaves full templates directly in your control.

    Personally I like the the ability, though, of being able to neatly segregate BP templates under one root dir /community/ or /buddypress/

    As for the js being the reasoning remember that both approaches essentially use copies of the same file/s so you still get those either way, one thing I’d like to see and may propose is the main js & ajax files being centralized as bp assets that both approaches could access rather than maintained separately in the theme folders – although that is the place they ought to live really.

    This whole question of approach taken is one I’ve raised as there are confusing aspects and I want a codex guide that outlines the approaches on offer and brings some clarity to making choices, which we’ll pencil in to the new guides once Codex is straightened out.

    @hnla

    Participant

    @sooskriszta
    You should be able to run a tortoise checkout with this url.
    https://svn.buddypress.org/trunk

    @hnla

    Participant

    ah ok, however I would still want to know what in a child theme prompts BP to assume (& it still stands: Assumptions are a bad thing altogether, period 🙂 ), didn’t spot that in the ticket referenced and as I’ve mentioned there is one issue we know of.

    @hnla

    Participant

    ‘Assumes’ ? assumptions dangerous things those, I would verify if that’s the case then.

    @hnla

    Participant

    As this thread says it’s likely a theme issue for the OP; as for your circumstances we don’t have detail, if you use the same theme then check with authors as suggested above.

    @hnla

    Participant

    @henrywright-1 Why are you choosing to work that way rather than running with theme compat template files? You do have a choice no way is right or wrong though if running the older style template approach you would need to have declared add_theme_support( 'buddypress' ); to ensure js/ajax unlinked, there is an issue with this though in that BP tries to get this value too early so fails to bail out of the theme compat class, so it needs to be positioned outside of a hook such as ‘after_setup_theme’ to be run early enough for bp.

    @hnla

    Participant

    Well for starters kill any plugins that might interfere with a registration process e.g facebook login ones – to test issues it’s always the instruction to disable all plugins working them back in until problem one is found.

    Other than that it’s hard to say there’s too little information. As far as BP 1.8.1 goes on a trunk install I appear to have no issues registering.

    @hnla

    Participant

    @sooskriszta Yes essentially. Ensure you have a checkout of trunk and that has update run to keep it current, then update a file and create a diff from that file created from the root of the plugin and as mercime says don’t forget to check your changes locally.

    @hnla

    Participant

    @sooskriszta You’re correct,;: bad grammar ought to be corrected and anyone can raise a ticket highlighting the need or go further and provide a patched file.

    @hnla

    Participant

    Empty functions file, don’t think I’ve ever seen a theme that has an empty functions file.

    bp-custom is a manually created file so that may well not exist, other than that it’s anyone’s guess what they’ve done.

    @hnla

    Participant

    I do hope they didn’t really say could only be fixed by buddypress support. Generally email issues are not BP problems, and currently BP has no issues I’m aware of in sending registration emails, which also is really a WP function.

    Easy check that should have been run first would have been and still ought to be tried is to disable BP and simply try registering an account under WP.

    Often email issues fall under the heading of ‘Domain Record’ issues i.e email servers rejecting an email as it can’t be verified as authorised on the sending domain or there’s no PTR record or SPF record, or simply that the server sendmail is at issue, these though are not really problems that lie with WP or BP which normally happily send out emails.

    Search this forum though as these issues have been discussed many times and you’ll find more info in the archives.

    @hnla

    Participant

    But it is visible for anyone by default!

    If it isn’t for your site you’ll need to look at what you have running that might be affecting that.

Viewing 25 replies - 576 through 600 (of 3,962 total)
Skip to toolbar