Forum Replies Created
@posh-john shanebp’s link above will explain the basic approach, however we do provide documentation that covers this sort of area and many others too; please make sure you have given those a good read as they will answer many points you may have, issues beyond what is covered in the documentation are then suitable for asking on the help forum.
Usually i try to avoid modifying template files except where absolutely necessary It is never absolutely necessary unless you are taking over support for that code. One of the most important aspects of the WordPress Theme api is it’s template hierarchy, it’s this that allows ‘Child themes’ to be created, all correctly written themes will be able to work with child themes if the parent theme doesn’t allow child themeing it’s a good indication that you should drop it like a hot cake and find another.
No sorry no patch as it isn’t an issue with BP thus not one possible to fix, you need to take that error message back to theme or plugin author for advise.
Why are you using a very outdated BP version, you need to update to the latest stable BP release and clean out any template pack stuff that that theme has added, and run BP under it’s automagic theme compatibility. Please check the codex for various guides that will help you understand this process.
@sarathvs-1 Please read the codex for guides on how to work with BP templates, Docs should always be first port of call!
BP works in the same manner as WP pages do in terms of hierarchy and thus also fits seamlessly into child themes or parent ones, you never directly edit template files.
@macpresss Thanks for the Codex contribution, I have however moved it for the moment to the user submitted guides under getting started as the components section is really descriptions of the standard default BP settings.
In reality we do have a page in progress here http://codex.buddypress.org/developer/filters-reference/ which is designed to list filters and defines in one place due to the large number of these.
Your theme isn’t aware of BP components so can’t add any particular styling to them other than whatever default properties it styles such as links and it’s major structural elements, by the same token BP cannot be aware of the variances of theme it may be slotted into so has to keep it’s styles to an absolute minimum to enable a basic layout for components, thus the onus is on the user to then take and extend the BP styles to better fit to their requirements; for this you will need a basic level of CSS knowledge.
And what results if you switch to a known working theme?
This sounds like a theme issue due to reference to ‘CustomHeadersAndFooters::loop_start()’
You could do this by adding a conditional check around the tr markup in the while loop that generates the field name and data
while ( bp_profile_fields() ) : bp_the_profile_field();
With that check in place you would then remove the
bp_the_profile_field_value()function and replace it with something like
echo do_shortcode( '[myshortcode user_id=' . bp_displayed_user_id() '] );
@mehdi-w The ruleset example does work as originally given you and placed where suggested, so if it isn’t then you either have a modified theme which you haven’t informed us of or you have added the ruleset incorrectly, sadly as you provide no information as to what you attempt each time we are just stabbing at solutions for you.
@henrywright-1 Thanks for fielding.
I have removed those links, as Henry says the codex is currently undergoing general review and update.
Checking the revision history on that page showed me those links were added two years ago, and there is no corresponding page I can find, I suspect what was actually intended was that those links be inline anchors links href=”#some-token”.
@nowton With tags such as conditional ‘_is_’ ones they are generally boolean so returning either true or false and their name acting as the reference so in this respect further reference or explanation unlikely with all tags will be referenced in this one page.
Not sure of the problem, but it sounds plugin related if only happens when posting to social networks, so may not necessarily be a BP issue, but with possible issues with BP betas please post to http://buddypress.trac.wordpress.org/ using your user account login with full steps to reproduce; posting in the support forum will just get lost.
That page looks fine. You’ll need to define what you mean by “templates look messed up” and whether that’s in a specific browser.
In BP 1.9 there are now built in BP account screen links that can be added to WP menus.
@henrywright-1 no the article is new at least for this current codex project and as with all pages we welcome comments and suggestions, it’s a basic set of guidelines designed to keep some uniformity to pages and submissions
I looked for that function but it doesn’t exist and the activity loop filters it’s loop if it sees bp_displayed_user_id() so that tag would have little use – I suspect it was removed long before things were added to deprecated files?
@henrywright-1 thanks for spotting that, the whole aspect of auditing the codex pages for outdated references is a very slow & laborious one.
In the codex guide page I added I left two snippets of code at the bottom to be used to add flags to the top of pages if issues are spotted, but equally yes if you’re confident that somethings wrong or needs updating please go ahead and do so, and drop myself or @mercime a note that you have – if possible, not essential – just so we’re aware, as it may signify a page needs checking in more detail.
When you do anything like upgrading an app and you’re not 100% familiar with the process you MUST read the documentation, looking for any guides or instructions to follow.
You are attempting to update a really outdated version of BP, and you cannot do a straight jump to the latest stable:
Read this page and link to upgrade process for 1.2 versions to 1.5
And strong word of advice, keep current with latest releases of BP in the intervening version releases there have been a few critical security fixes that left un-patched leave your site and others vulnerable
You need to follow up with your hosts, BP does not contain any nasties and this sounds like a false / positive from some form of scanning software your hosting provider uses, but you never did answer the question where you obtained BP from in the original failed attempts.
The first place to start is with the BuddyPress documentation ( Codex ) Read the following two pages to familiarise yourself with BP theme compatibility and how to use custom files, if that isn’t sufficient to correct your issues you may have a theme that does not play properly with the WP template process and has a custom process for dealing with the loop in ‘pages’ which will need modifying in a custom bp file, however the theme author is best placed to be able to tell you what adjustments you need to make.
Don’t be confused by the term ‘Legacy’ those files in that directory section are the format for template files working under BP’s new theme compatibility layer, use those for any custom mmods you need to make copying them to a theme/child theme in a directory named either ‘community’ or ‘buddypress’ and observing the folder structure within that directory to maintain paths.
It’s not good form to post a question in another thread it causes confusion. In your other threads I did mention basic trouble shooting so can you confirm you have tried deactivating your custom theme and trying with one known to work and that all components are activated and have pages existing for BP to use.
http://buddypress.org/support/topic/getting-help-for-this-forum/ a quick response to that thread would have been appropriate just to let us know that you understood those basic steps.
bp-custom.php does run as Paul advised earlier, nothing has changed I ran some test code in one yesterday so know there’s no issues.
There must be something else occurring as both those defines work.
That has been advised two posts up, please re-read and read the links. Creating a custom file named buddypress.php which is a copy of your themes page.php file will allow you to modify the markup directly so you can specify named get_sidebar() calls to include a new sidebar template file for BP screens only, however bear in mind how your theme deals with sidebar files and dynamic sidebars(widget calls) is something we have no knowledge of.
BP is just a plugin running under WP, WP handles users/registration. You need to create Users not members first so you’ll need to run up a little script to import the .csv file using fgetcsv() into an array then use that to loop over and set values to add for a user with the function wp_insert_user().
BP recognises members when a user logs, in until that point you will have no populated members list, BP looks to usermeta key ‘last_activity’ to see if there is a value so you can, as your looping and setting a new user, then also set ‘last_activity with the php date function and a pause between each itteration so you get a unique time stamp for each (not that that’s vital)
// edit: beaten to it!
You must determine if it’s the theme or not; this is done by reverting to a theme we know works with BP and those are any of the WP default series, ‘Twentytwelve’, ‘twentythirteen’. I’m afraid that nine times out of ten things will be a theme issue but also might be pluging related so ensure you disable all non essential plugins.
One last thing to consider is whether the various BP components are activated, so visit the BP settings screens and check what is activated.
Firstly did you not read the sticky post ‘getting help’ ? in that is a bullet point list of information it’s useful to provide (not all necessarily essential) I have also just updated that post with basic troubleshooting steps that everyone overlooks and which we end up repeating again & again. many issues are third party theme related so the most important step is enabling a known good theme e.g ‘twentythirteen’ then check plugins.
Looking over your posts I don’t see any current ones more then 20 hours old. We ask that people wait 24 hours before bumping posts to gain attention, and also we are just coming out of a weekend so things will be slower and all help here is on a voluntary basis.
Post titles on tech forums: Please ensure title threads are descriptive of the issue not a generic cry for help, yes we’re aware there’s an issue, so titles like ‘please help, not working’ won’t gain much attention as ones stating what sort of issue is occurring.