Forum Replies Created
You don’t provide any detail as to the theme your using custom thirdparty, bp-legacy theme compatibility, bp-default.
The problems suggest a custom theme causing the issue, although you do state tha changing to bp-default does not correct problem, it may then lie with this role you have?
As for adding that code directly to a template you would need a conditional check to see if a user is logged in, have a look at the functions file in bp-legacy around line 380 to see how sitewide notices are handled.
Ok what is not clear in that particular guide is the necessity of creating a new forum but selecting ‘category’ rather than ‘forum’ when you save/create it, this category is the groups forums parent and the slug that you would see appear in that select option, the one referenced ‘Groups Forum’ is simply an example name.
Have a read of this other guide to installing bbPress from new written by our own @mercime as it explains the steps very clearly:
The upgrading guide will need a little editing to make things clearer.
I take it you are working in a localhost, dev environment from your reference to Dreamweaver?
If that is the case your topic title was a little misleading and implying something that wasn’t the case – fyi it is considered bad form on lists, forums to use ‘Urgent’ or ‘Emergency’ in thread titles.
Dreamweaver can’t run dynamic sites of any description, it’s frankly a rather bad application in general, the only real use for it is in it’s editor form, avoid any notion of using it’s wysiwyg options.
If this is a a localhost dev issue then you need to setup a proper server to run these sorts of sites from, look at installing something like Xampp or Mampp or search the WP plugin repo as iirc there are plugins to help with setting up dev environments.
>What is version 1.9.2 supposed to fix anyway? I could not find any documentation
There’s very clear documentation, right there on the main blog!
If you want help, you’ll need to provide as much detailed info as possible on your setup, in particular your theme in use and it’s approach to working with BP.
They don’t exist until you create them.
I’ll go and fish out all the codex guides that have been written on the subject of templating/themeing
Also remember you can use conditional logic to wrap the sidebar in your bp template so if you wanted the sidebar just for user account screens you could do:
if( bp_is_user() ) :
The two guides to read are:
That’s WP template code. Look at content-page.php. Please also read through the codex as we have provided guides to help with understanding what files will be in use when running BP theme compatibility.
Have you read through the guides in the BP codex?
Have you created a buddypress.php file to manage the page.php rendering? Theme compatibility uses the stock WP page.php file – or a series of other templates names in same manner WP performs template selection. You need to customize page.php essentially but not the themes copy but a copy of renamed for Buddypress use which you can then edit, again fairly detailed guides available in the BP codex to help explain the process.
Have you checked the sticky posts for guidance on info to post to help us help you and basic troubleshooting steps?
Are you using a custom thirdparty theme, if so can you activate a theme known to work i.e one of the WP default themes and see if things then start working, this way we identify the theme to be the issue- or not , and work from there.
No not a blank file, you copy over the existing file, the crucial aspect is that you retain the same folder paths to that file so members/single/index.php if found in your child theme is the one used, or in the case of that plugin you might need to us it’s templates in place of the BP ones.
If you are set on using bp-default then you probably ought to copy over all template files, and all assets css, js, etc to your theme along with the functions file parts necessary to locate BP ajax, scripts, styles and add the line add_theme_support( ‘buddypress’ ) in your themes functions.php file and run as a full theme.
Firstly this is a two year old thread!
Secondly a quick check of the plugin in the repo shows it hasn’t been updated in two years, that is very likely to mean it isn’t supported by the author any longer and also that given the changes to BP in that intervening time it’s very unlikely to work.
If you want to pursue further then the WP plugin support page is the best place to try.
It’s going to be a matter of understanding how themes & templates work in, in that respect the BP codex is your friend, I encourage you to read as many of the pages in there relating to BP themeing.
>does this mean i can build a theme on bp-default without creating a child theme… …without it being overwritten when i update after 1.9.1
No, and you never could, if you wanted anything other than the stock display produced by bp-default you had to create a child theme to carry your styles or template overrides.
I noticed your other thread, firstly you asked the same question on the plugins support forum, but haven’t really left sufficient time for the author to respond, asking the same question here will probably not get any quicker a response or solution as this is a third party plugin issue.
Having said that you mentioning you have copied /bp-default/ to your theme doesn’t sound right, to overload bp-default templates in a child theme you copy the folders and templates that exist under the bp-default folder; think of the folder name ‘bp-default’ as being translated to or being the equivalent of your theme folders name.
One last point, best advice is really to try and work your theme using theme compatibility, the general encouragement is to try and use theme compatibility rather than the older process, that eventually won’t get any significant updates or support and will only exist in a backwards compatible manner to ensure themes previously built on it continue to work.
@gfam105 Ok so most of these themes are built on bp-default, this theme is to be retired, a process begun with BP 1.9, this doesn’t mean it can’t be used and is still bundled in the core plugin for the moment, existing sites using it either directly or as a child of will still be able to work but new installs will not see the theme appear in the WP theme page as a selection, this is by way of encouraging people to use the new Theme Compatibility process which allows any theme to be used.
If you need bp-default as a parent try adding:
add_filter( ‘bp_do_register_theme_directory’, ‘__return_true’ );
to your functions.php or bp-custom.php files to force the theme to register in the WP theme page.
Several of what BP themes? BuddyPress works with any well written theme following the WP template principles, as you don’t mention what themes you have tried, try activating one of the WP standard themes bundled with WP then you’ll be able to see BP in action, also please do check the BP codex documentation as you’ll find helpful guides to getting started there.
P.S. Why are you looking for a bp-custom.php file what prompted you to do that? This doesn’t exist by default and is created as needed and the file is specifically to run code that affects BP core operation across any theme which may be installed; it isn’t required to simply run a theme or BP.
You will need to contact your hosts support desk about this issue, it’s server related rather than BP.
but it is a list already so not sure why you are getting this error. Unless you have modified the comments.php template you should have ul li construct for comments.
The filters seem problematic, add_filter works after a fashion but won’t take an empty string, remove filter doesn’t work from functions.php on any priority level.
hmm tbh I wouldn’t necessarily mess with the markup BP generates at this point; the div ‘activity-comment’ should contain the entry form and if comments a ul list which for a series of items like comments and where they may be nested is a about the only suitable choice really.
What have you got around the area where bp_activity_comments() is set?
@marcella1981 you’re missing the point of what I was trying to get across to you. In respect of bugs in reference to markup – rather than mid tier scripting – then likely you haven’t any, what you do have are markup errors, fixing those is not something you do at the end you must do it as you progress through a site build, this is strict and for the reason that you can’t apply styles to a broken DOM, and you can’t expect browsers to handle a broken DOM in the same manner browser to browser, fixing markup errors can clear up a heck of a lot of issues you may be seeing at the moment (html tidy performs the same markup checking as the W3C Validator it’s not just a markup tidier but a sgml parser that will report errors by line)
Also Please get rid of that x ua-compatible meta tag it’s IE proprietary and used to induce google frame is just wrong and always was and isn’t doing anything useful, IE 9+ are reasonable browsers that will handle Standards pretty well lose that meta tag and you have one less validation error
Couple of important things:
When building sites/layouts WP or other wise build to Standards, this means building in ‘Modern’ browsers that observe W3C Standards, if you’re building in a browser and then find that you are not getting the same display in another known standards compliant browser then it is something you are doing incorrectly. Browser checking is something that takes place from word go you must trap problems early rather than later.
Get in the habit of using debug tools i.e html tidy to tell if there are markup errors as the commonest reason you’ll see a display render differently from browser to browser is because of human errors thus forcing the browsers tag soup rendering engine to step in and try and silently correct those errors- the W3c does not specify an rules for vendors to adhere to in interpreting errors or performing error correction so browsers will do what they think is right and that varies from bowser to browser. Clear up markup errors and you’ll find many things will fall into place.
I note a few mis-matched elements, elements without correctly placed closing tags.
In the body tag I see no class tokens or class attr this is a function of WP and BP pushes out many classes for it’s own screens through this function, if you’re using the BP styles then many won’t be applying if they’re based on body classes.
You probably want to be using bp_core_new_nav_item() hooked to bp_setup_nav the new nav item takes an array ‘name’, ‘slug’, ‘default_subnav_slug’, ‘screen_function’, ‘position’
‘screen function’calls a function that in turn hooks a template function to ‘bp_template_content’ and bp_core_load_template() which for ease use plugin.php
Then in your function that is hooked to ‘bp_template_content’ you’ll run what ever ‘stuff’ you want to display on the screen.
What’s the question?
You can do that, essentially all you need is the group permalink to hang a graphic off and dump all the rest of the groups index loop detail.
These are probably questions better asked on bbPress forum – remember although bbPress integrates with buddyPress it is a standalone plugin.
I doubt however you need to overload all the files as above.
I would strongly urge you to first have a good read through what articles we currently have in the codex to familiarise yourself with basic setup & operation:
Then if you have further questions post back with a full outline of your setup – check the forum stickies which tell you what information to provide in order to gain help here.
This is more a WP question, you can remove the comments by passing an empty array back to comment form in the template file, have a read of this post on WP support:
P.S. when you state you have tried something please actually say what it was you tried as it may have a bearing on the matter.
As an author technically you/we shouldn’t use it at all not that it’s prohibeted from use in author styles but just that in the environment of WP plugins & themes it’s a poor practise; in general author styles it should be severely limited if used at all though!