Search Results for 'theme'
-
AuthorSearch Results
-
May 23, 2009 at 10:34 am #45923
In reply to: Change /blog title
Burt Adsit
ParticipantYou want to change the title of the page in the browser? I think that’s what you are asking. Each page has a different title based on what it is and what it contains.
If all you want to do is change the title to the same thing on your site then that is located in the /bpmember/header.php file on line 7 – <title><?php bp_page_title() ?></title>
If you want to change the title to something else based on what page is being viewed then you’ll have to either alter the core code, which isn’t a good idea, or install a filter.
The title for each page is determined by the function bp_page_title() in bp-core-templatetags.php
At the bottom of that function bp calls a filter so that you can change the title without altering either header.php or bp_page_title(). You can install a filter by creating one in your bp-custom.php file like this:
function my_page_title($with_site_name, $without_site_name){
return ‘my page title’;
}
add_filter(‘bp_page_title’, ‘my_page_title’, 10, 2);
The parameters that get passed to your new filter are the page titles with and without the site name that the bp_page_title() function is going to use as the page title. Whatever you return from that function will be the page title for *all* pages that use the bp home theme.
May 23, 2009 at 9:22 am #45918In reply to: Erroneous message -> Buddypress themes not installed
ParticipantWell, the error message is correct. You don’t have any bp themes installed if that gif actually is whey way the files are layed out. The bp-themes folder belongs in /wp-content not in /themes it is *not* a normal wp theme. Please see the readme.txt in /bp-themes.
May 23, 2009 at 2:46 am #45912In reply to: optionsbar & userbar’s Not Hidden on Directory Pages
ParticipantHi everyone.
Priority 5 :
1. bp_core_directory_members()
2. bp_core_search_site()
3. bp_blogs_directory_blogs_setup()
4. groups_directory_groups_setup()
That’s a partial dump of the hooks that run for the action ‘wp’.
All those fns get triggered on each page load. The purpose of all of them is to detect if a directory is being viewed or the search fn is being run.
Let’s just look at the members directory and it’s fn bp_core_directory_members() in bp-core.php
In that fn is the line:
if ( !is_home() && is_null( $bp->displayed_user->id ) &&
$bp->current_component == $bp->default_component ) {That’s what bp uses to determine if the member’s directory is running. Underneath that line is $bp->is_directory = true which shuts down the option and user bars. Either that line is failing, your theme isn’t triggering this fn or something is setting $bp->is_directory to false again.
This works just fine in the default themes with 1.0 and wpmu 2.7.1.
May 23, 2009 at 2:20 am #45911Rich Spott
ParticipantYou’ve just got to tear out *everything*. All this domain mapping and other things. Get down to a bare install of bp 1.0 using the default themes and wpmu 2.7.1.
I did that, took out all plugins except for buddypress 1.0, and changed the themes to the default buddypress theme, and default buddypress member theme, and used a vanilla .htaccess for wpmu 2.7.1.
Still got an internal redirect when Googlebot-Images came through and looks for something that is not there. I even recreated the error and was able to see the 500 error.
Did you remove your previous bp install from /mu-plugins? Why is it trying to get to an avatar image from there? I suspect it’s all your *other* addons in some combination with the upgrade to 2.7.1 from 1.x and the addition of bp into the mix that is causing your problems
Yes, I removed buddypress RC-1 from mu-plugins before proceeding with installing BP 1.0. I dont know why it is grabbing files that dont exist. But that’s not really why i’m worried about it, it’s more that if any sites links to tries to get a file that is not currently on the site, it creates a 500 error.
I didn’t upgrade from WPMU 1.x to 2.7.1, I went from 2.7 to 2.7.1, and 2.6.5 before that and basically following each and every update that there has been since 1.3.3 last april. Maybe it was confusing in the way I wrote it.
Take things back to a known, working state. Start with bare 1.x. Then upgrade to wpmu 2.7.1 incrementally. From everything I hear on the wpmu forums this is the recommended procedure. Jumping from 1.x to the latest version in one step isn’t recommended.
I went from WPMU 2.7 to 2.7.1, and it was working fine in 2.7 with BP RC-1
But I did have everything stripped out for a matter of 10 hours and i still got the same errors. I do know that some plugins leave tables in the database, should i drop those tables associated with a plugin and see if that works? Because even if I have a clean install of WPMU 2.7.1, then BP 1.0, i still have a database with all of the remnants of the old stuff.
May 23, 2009 at 1:06 am #45909ParticipantYou’ve just got to tear out *everything*. All this domain mapping and other things. Get down to a bare install of bp 1.0 using the default themes and wpmu 2.7.1.
Did you remove your previous bp install from /mu-plugins? Why is it trying to get to an avatar image from there? I suspect it’s all your *other* addons in some combination with the upgrade to 2.7.1 from 1.x and the addition of bp into the mix that is causing your problems.
Take things back to a known, working state. Start with bare 1.x. Then upgrade to wpmu 2.7.1 incrementally. From everything I hear on the wpmu forums this is the recommended procedure. Jumping from 1.x to the latest version in one step isn’t recommended.
When wpmu 2.7.1 is operating correctly without any fancy domain mapping installed. Then install bp 1.0 and get that working. Gradually add in your other plugins and test before moving to the next one. That procedure, by itself, may solve your problems.
The upgrade and installation of new features procedure, that you have been practicing currently, has driven your site insane. You are trying to track down individual symptoms of a completely unknown state of affairs. You’ll just wind up chasing symptoms instead of curing what’s wrong.
May 22, 2009 at 2:31 pm #45879In reply to: Admin bar problem with premium theme
Jeff Sayre
ParticipantAytac-
Is the premium theme BuddyPress enabled? Is it designed specifically for use with BuddyPress? If so, contact the theme designer and tell them of your issue. They are the ones who should be providing support.
If the premium theme is not designed to be used with BuddyPress, then choose a theme that is.
if I use default theme Buddypress admin bar is working well
Since this is not a BuddyPress support issue but an issue with a custom theme, I’m setting this to resolved. As you state, your site works fine with the defualt BP themes.
May 22, 2009 at 7:09 am #45860In reply to: Erroneous message -> Buddypress themes not installed
jugularbean
ParticipantThanks for the response Burt.
I am using WPMU 2.7.1
However the subfolder within bp-themes is bpmember, so no problems there. And when I go to the wpmu BuddyPress backend I cannot select any themes.
See screenshots at
http://70.32.90.231/buddypress-gen-settings.gif
http://70.32.90.231/wpmu-site-themes.gif
http://70.32.90.231/ftp-file-structure.gif
I even tried removing the non BP themes from the BP folder. But it doesn’t make a difference.
May 22, 2009 at 6:34 am #45859In reply to: Group and forum problems…
2954679
InactiveHEEEEEEYYYY!
ANSWER ANYONE!!!!
HOW COULD IT DONE THAT STABLE HAVE PROBLEMS WHICH NO PRESENT IN RC-1?
I’M REALLY CANNOT LEAVE A GROUP!
I’M REALLY CANNOT USE SKELETON THEME!
ETC
DO ANYTHING!
May 22, 2009 at 6:23 am #45858In reply to: Blogs Using BP Theme
John James Jacoby
KeymasterIronically enough, that’s pretty much exactly what I ended up doing. Spent a little time getting close and comfortable with a few hooks and filters and checked out some of the existing WPMU default settings blogs.
May 22, 2009 at 6:16 am #45857In reply to: multiple instances of BP widgets
Callum Macdonald
ParticipantHola Magi182,
Did you have any luck with this? I’d like to duplicate the Pages widget because on the BP theme I want it on the front page and on my blog sidebar. They’re never shown at the same time, but I only have one copy of each widget.
If I find a solution I’ll try to remember to post back here. I don’t think I can email subscribe to this thread though, so I may lose track of it in the winds of time. Feel free to send me a PM chaser…
Be well – Callum.
May 22, 2009 at 6:14 am #45855In reply to: Blogs Using BP Theme
Participant@John James Jacoby: You could use the new blog defaults idea to set the widgets for all new blogs. Disabling the menus is pretty easy via a plugin. If you wanted to be secure you’d probably also need a quick check in the wp-admin interface to ensure that users don’t stumble upon the theme / widgets pages. You could easily redirect them if they did.
That would provide a pretty consistent experience without having to re-code the sidebar.
Ooh, or even simpler, oh yes, this is genius. Hook into the pre get option call and replace the sidebar-widgets option with the sidebar widgets from another blog. So you could either use the sidebar widgets from your primary blog (ie blog id 1) or another blog that you could maintain for just that purpose. Then you have one central place to manage the widgets, and they’re automatically modified across all your blogs. Nice.
Let me know (PM, I probably won’t see replies on this thread) if you need any pointers with the code. I could probably whip something up or at least give you the core function calls to investigate.
May 22, 2009 at 6:00 am #45848In reply to: Fresh New Install Error 404 Not Found
InactiveYeah I adjusted the permalinks for the blog other wise it nothing worked. It was on custom structure (/blog/%year%/%monthnum%/%day%/%postname%/) when I changed them to the default.
Yes the functions.php file is located at wp-content/themes/bphome/.
htaccess file:
# Use PHP5 as default
AddHandler application/x-httpd-php5 .php
May 22, 2009 at 5:48 am #45846In reply to: Fresh New Install Error 404 Not Found
KeymasterNot all of them..
http://www.sportssonet.com/?p=1
http://www.sportssonet.com/wp-login.php?redirect_to=http%3A%2F%2Fwww.sportssonet.com
It’s just the BuddyPress ones. Does your theme have the functions.php that came included with the bphome theme still there?
Can you copy/paste the contents of your .htaccess file here within code tags? Also, what are your permalink settings set to, or are they still just the default?
May 22, 2009 at 5:44 am #45845In reply to: Fresh New Install Error 404 Not Found
InactiveYes I’m using the bp home theme (see link in first post) and all the links are 404ing.
May 22, 2009 at 5:40 am #45843In reply to: Fresh New Install Error 404 Not Found
KeymasterAre you using the included bphome theme? Which links specifically are or are not 404’ing?
May 22, 2009 at 1:03 am #45833ParticipantOkay, thank you for helping me, I’ll try to go through your questions one-by-one.
First I’ll let you know what I have:
Slicehost
1GB slice
Ubuntu Hardy LTS 8.04
Running Apache, PHP 5, MySQL 5.0 (followed Pickeled Onion’s walk-throughs on how to set it up, I am by no means an expert, and my very first barebones VPS was this one.)
I help run http://sportsblognet.com where we have WPMU 2.7.1 and BP 1.0, along with bbPress 1.0-alpha6
Have you tried deactivating all non-buddypress plugins, wp-super-cache in particular?
I deactivated all but buddypress, feedwordpress (because our theme will break), wp-super-cache, and doncha’s domain mapping plugin. But maybe I will remove them all for an hour to see if any errors get through
I am removing wp-super-cache right now, but it was tough to get rid of the wp-content/cache folder because it was owned by the root user. But i got it deleted and removed the wp-super-cache stuff in the .htaccess and I’ll guess i’ll have to wait to see how that goes.
Have you tried using the default .htaccess file that ships with WPMU?
I just tried to, but it won’t let me.
My current working .htaccess (minus wp-super-cache stuff)
<FilesMatch ".(ico|pdf|flv|jpg|jpeg|png|gif|js|css|swf)$">
Header set Expires "Thu, 15 Apr 2015 20:00:00 GMT"
</FilesMatch>
RewriteEngine On
RewriteBase /
#uploaded files
RewriteRule ^(.*/)?files/$ index.php [L]
RewriteCond %{REQUEST_URI} !.*wp-content/plugins.*
RewriteRule ^(.*/)?files/(.*) wp-content/blogs.php?file=$2 [L]
# add a trailing slash to /wp-admin
RewriteCond %{REQUEST_URI} ^.*/wp-admin$
RewriteRule ^(.+)$ $1/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule . - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-.*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*.php)$ $2 [L]
RewriteRule . index.php [L]
<IfModule mod_security.c>
<Files async-upload.php>
SecFilterEngine Off
SecFilterScanPOST Off
</Files>
</IfModule>and the WPMU standard one
RewriteEngine On
RewriteBase BASE/
#uploaded files
RewriteRule ^(.*/)?files/$ index.php [L]
RewriteCond %{REQUEST_URI} !.*wp-content/plugins.*
RewriteRule ^(.*/)?files/(.*) wp-content/blogs.php?file=$2 [L]
# add a trailing slash to /wp-admin
RewriteCond %{REQUEST_URI} ^.*/wp-admin$
RewriteRule ^(.+)$ $1/ [R=301,L]
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule . - [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(wp-.*) $2 [L]
RewriteRule ^([_0-9a-zA-Z-]+/)?(.*.php)$ $2 [L]
RewriteRule . index.php [L]
<IfModule mod_security.c>
<Files async-upload.php>
SecFilterEngine Off
SecFilterScanPOST Off
</Files>
</IfModule>it wont let me use the standard one, and the only difference that I can see is the expires header setting that i added.
Are there any PHP errors in your log files?
this is my current concern right now
Request exceeded the limit of 10 internal redirects due to probable configuration error.ALERT - canary mismatch on efree() - heap overflow detectedfor the ALERT error, I contacted slicehost and they upgraded my kernel, they said that has fixed other people’s problems (fingers crossed – but no errors since they did that this morning) if that doesnt work i have to go through and install php without the suhosin patch.
most of the other errors are of spam scripts trying to signup and not finding wp-signup (i changed the signup name)
what are the other listed errors in your apache log?
That’s pretty much it.
EDIT: it’s about 30 minutes later and an Internal Redirect Error just showed up in my logs with wp-super-cache out, and all but buddypress plugins out. So it doesn’t look like its a plugin.
May 21, 2009 at 10:44 pm #45830Participant301 Redirects:
http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=93633
http://www.seomoz.org/blog/url-rewrites-and-301-redirects-how-does-it-all-work
Using your robots.txt file to block googlebot-image from discovering your image files:
http://www.google.com/support/webmasters/bin/answer.py?answer=35308
Make sure you block only the image directories that you do not want indexed.
Also, if you do not use Google’s Webmaster Tools, you may want to investigate. This service offers many tools, including a list of which files are throwing 404s. http://www.google.com/webmasters/tour/tour1.html
Do you mean while I get this situation worked out? Or do you mean that people are working on this because numerous people have been getting this issue?
I’m not sure that the word numerous applies as I’ve only seen a half dozen or fewer threads with this particular issue. Remember, one person’s 404 is not necessarily the same as the next persons.
This type of issue often comes down to one or more factors: bad install, using too old a version of WPMU or BP, plugin conflict, custom theme issue, apache issue, ISP limitations.
We can try helping you with most of these but do not have any control outside the core of the BuddyPress code. We investigate as best we can with the information provided and if it is caused by BuddyPress, offer a fix in trunk.
I see in another thread that you are on Slicehost. I’m with them as well. Since you have to set up your own slice, there may be an apache issue. So, to better understand you particular issue, please provide some more details:
- Have you tried deactivating all non-buddypress plugins, wp-super-cache in particular?
- Have you tried using the default .htaccess file that ships with WPMU?
- Are there any PHP errors in your log files?
- what are the other listed errors in your apache log?
May 21, 2009 at 7:45 pm #45821Mark Leonard
ParticipantHi Jeff,
Thanks for that but it is same with all themes.
I have created another problem by inadvertently installing a “member ship” script in the members sub directory. The result of that is now I can’t access groups and member profiles. I think I have some emails to send to my users and inform them that I need to do a clean reinstall and advise them that their profiles have been wiped.
I feel like a right muppet.
May 21, 2009 at 6:35 pm #45816In reply to: Reinstall – Should I delete old tables from db?
omgitsrfb
ParticipantDJPaul,
I deleted all of the wp_bp tables. I’m not sure what you meant by check the wp_sitemeta table for similarly-named buddypress settings? Could you give me an example of what you are talking about? Here are the meta_keys for the sitemeta table? Anything I need to do or am I good to go with the reinstall?
admin_email
admin_user_id
registration
upload_filetypes
blog_upload_space
fileupload_maxk
site_admins
allowedthemes
illegal_names
welcome_email
first_POST
update_core
blog_count
blog_count_ts
user_count
user_count_ts
comment_indexer_version
comment_indexer_installed
communities_version
communities_installed
forums_version
forums_installed
friends_version
friends_installed
messaging_version
messaging_installed
post_indexer_version
post_indexer_installed
signup_language_version
May 21, 2009 at 3:26 pm #45806In reply to: bpContents 0.1X Core Code – Dev Sneak Peek
ParticipantYes I know it’s been several days since an update to bp contents. The core is working and I’m struggling with getting this up and running in the member theme properly.
May 21, 2009 at 3:19 pm #45805In reply to: bpContents 0.1X Core Code – Dev Sneak Peek
ParticipantYes I know it’s been several days since an update to bp contents. The core is working and I’m struggling with getting this up and running in the member theme properly.
May 21, 2009 at 2:17 pm #45800In reply to: Erroneous message -> Buddypress themes not installed
ParticipantOnly bp themes go into /wp-content/bp-themes. Normal wp themes do not go there. They live in /wp-content/themes as always. If you have just upgraded to 1.0 then the bp member theme directory name has changed from bp-member to bpmember due to changes in wpmu 2.7.1.
Go to the back end of wpmu BuddyPress > General Settings, make sure the default member theme is selected and press Save Settings. Should go away.
May 21, 2009 at 2:05 pm #45798In reply to: Adding True BP Functionality to Standard WP Theme?
Participantblacklegtr, “And I have the same problem. Anybody can help me?”
What exactly is the problem? This is a 4mo old thread that wasn’t understood in the first place and we don’t seem to be getting any clearer today.
May 21, 2009 at 1:52 pm #45792In reply to: Adding True BP Functionality to Standard WP Theme?
David Lewis
ParticipantIf you want to add a login to the sidebar and no widget exists… just hard code it in the templates. The code already exists in the admin bar… so it’s probably just a copy/paste.
May 21, 2009 at 12:52 pm #45788ParticipantTry switching to the standard, default Buddypress theme. If the issue goes away–meaning that you have three columns once again–then it is time to contact the facebuddy designers.
-
AuthorSearch Results
