Forum Replies Created
-
I am having the exact same problem. I submitted it as a ticket:
https://buddypress.trac.wordpress.org/ticket/4706
What is happening is its trying to redirect to the home tab, then the change default filter moves it to the other tab, which causes the loop.
Until its fixed simply add ‘/home’ to the line mentioned in the ticket.
@LPH2005 Good point, I dont know if it gets overwritten, I’ll have to look into that..
Sounds like a memory issue. I had it when working with WP-commerce. My suggestion is to adjust your memory in wp-settings to something like: ini_set(‘memory_limit’, ‘128M’);
What’s happening is theres a glitch somewhere and its crashing the whole script. If the glitch happens early it displays a big blank nothing.Turn off ALL plugins, then turn on BP. See if it crashes again.
Also, view the source of the blank page, you can see if anything is loading at all.link?
I think the reality will be a simple search filter like on WP. It either will work with 1.3 or it wont, and I think as long as your plugin falls out of working with 1.3 and the dev hasnt updated I would consider it abandoned. The issue I have is when they wont admit it or have taken money in offer of support but disappear.
I’m going to be doing work on group docs here soon, the older developer has been super busy and he graciously let me work on the code with him to get it to 1.3 So Id say contact the Dev and see what their status is. I’m actually writing up stuff for Group Docs right now.Some plugins are going to break with 1.3 Most should be rewritten for it. I think 1.3 will be the stable ground for plugins beyond this point as the biggest difference is a solid framework from 1.2
There isnt a plugin I know about, but there are a few for group docs and things like that..
Just like when you install WP, users will see xyz.com not xyz.com/wp-admin
r-a-y posted the best response to this. I think a plugin would over complicate the site. You can use the loop or just call your groups specifically.
I’m burried with side projects right now but I’ll add this to the list of “quick-tuts” I plan on doing..I think one thing to note is twitter uses the hashtag identifier and also is limited to 140 chars. You would have to search all the content in a blog post, filter the results, and compare.
Twitter just takes all the #whatever tags and compares them. I dont think a plugin would be too hard but I dont think there is one that would do this.@svenl77
I would go to the trac: https://buddypress.trac.wordpress.org/
and create a ticket for your ideas. This would give other dev’s the chance to look at it, and you can work it much easier than starting threads on the forum. It also keeps all the files you put up so its a good revision tracker.
And what most of us do is create a patch against the newest version of the trunk and the core dev’s check it out and either ad as/is or work to modify it to fit..And I was wondering, if moving the sidebar can be done with just CSS why are we adjusting the markup for it then? I understand to avoid repetitious code but for backpat sake if css can do it, why create more hassle? PS, this is the stuff that can go on the trac.
@johnjamesjacoby : Wouldn’t moving the sidebar cause a nightmare for backwards compatibility?
I am currently writing my own theme that looks nothing like BP-default, but I’ve been on trac almost daily with the UI tickets. I don’t know if we need a dedicated “UI/UX” team, but as long as folks are submitting on those tickets it will ease some of the other dev’s needing to mess with it. I DO think it is an important component with BP and we need to keep talking about 1.3’s problems.
I’m glad to see all the discussion going on, especially in light of all the “BP IS DEAD” nonsense. I think the biggest issue is how the forums make it hard to actually talk, but the testBP forums are great and I’m excited to see them go live here. I’m also anxious to see the new BP.org which seems to be slated to June.
My biggest issue with the BP sites I run is spam. Even my non indexed test servers get spammed. My AIGA site was deleting 250 spam users/blogs a day before shutting off new user registration. The first part of that comes from spam users being registered. There are two types of spam services, bots, and (slave) labor. These folks get through the Captcha’s and set up real fake accounts. But in my experience with my comment forms adding a Captcha killed a vast majority of spamers. Then with comments, contact forms, etc this would kill most spam. From there heuristic spam fighting from splogs, comments, etc. Also a system that users can mark a item as spam would help a ton.
Second, its that to learn how to do ANYTHING in BP I have to take something that works with the current version and hack it a part to figure out basic commands and actions. Once the new site is up I think there should be a real push on getting the Codex up to snuff(look at jQuery and WP) that have examples, resources, etc. Then have tutorials on things, hell syndicate them from other bloggers.
So as my thing(s) I want to keep being a part of fixing UI issues, and will as long as I can.
I want to write for the Codex, and am here and willing to write Blog articles for BP. Tutorials, Updates, whatever. I’m game. I will be writing tutorials for AIGA members anyway, so why not sync the content here.
I am working on the Group Documents plugin with its original developer because my sites need it.And lastly I will be writing a BP-Spam component. I will do it as a plugin first and will want/need tons of feedback. But to get the University to sign off on my project I will need to stop all the Viagra and other inappropriate content from making it through. I will do this regardless of it being a part of BP but want to give back however I can.
I’m so psyched to see all the energy is still in this project!
There is a groupDocs plugin, and Boon is working on a great doc’s plugin. I think it might be set for users too..
nav_row is after the content tag so look in index.php Should be there. Functions.php relates to custom functions for your theme, not to your nav.
Somewhere in your code there is the info that creates that navigation that’s under your logo. Put the code pcwriter mentioned there, it will generate the BP related menu items. My guess is its either in the Header.php(should be) or is called in the index.php file. If you are using a tool like dreamweaver or notepad++ you can just select your template folder and run the find comand, search “nav_row” and there it is!
Not using a child theme will create the chance for theme mistakes to break the site. That is why they are there. So if you create a new theme thats great, but BP-default has pretty much every case loaded into it, so if your child theme messes up its there to cover you. Thats the only issue I see. Also, there are situations where BP adds classes and style to elements in the DOM such as “accepted” to buttons, this is something to consider when creating a theme.
I lost everything on the community tab..
Not 100% but I’m guessing which components are currently turned on under the component settings
It’s exciting to see! Last time I was messing with the code it wasn’t so well documented throughout and I’m excited to see the component class. Out of curiosity, why isn’t that stuff in the codex? Time? I’d be willing to put some of it in there..
The only thing I see as an issue right now is filtering out the subclasses from the parents. IE events from groups. I’ll have to setup exclusionary functions… Not a big deal but something I’ll have to deal with.
So I have been reading through the code from the trunk and it seems I hadn’t read the code like I should have. The code is already built around the component class, but ALL components are. From what I have been reading I am simply wanting to extend the BP_Groups_Component to fulfill my individual needs. Somethings I wish were different but I dont want to reinvent the wheel.
Thank you Paul! I’m going through it now, on the trunk its bp-core-component.php
I agree that the default theme needs a designers touch, but it has all the nuts and bolts to make everything work. If for some reason your new theme breaks, the default will at least be there to back you up. Plus its always helpful to be able to simply turn off your theme to see if its a BP issue or a issue in something you did.. If it works in default then it will work in your theme.
What your talking about with the stream I agree changes should be made, but thats a personal preference so you have to write that function into whatever you are doing and go from there..
I think LPH2005 is like most folks and doesnt think of writing the css path off of the body tag. I think it makes sense from a ground up prospective but with there already being so much styled it is probably best to use the path method for BP specific items.
I removed the bar completely and replaced it with my own segment of code. you can copy bp-core-adminbar.php to get whatever it is you want but say you want a totally custom bar you’ll have to kill the original. heres how I did it:
function ovc_adminbar() {
require('ovcbar.php');
remove_action( 'wp_footer', 'bp_core_admin_bar', 8 );
}
add_action('wp_footer','ovc_adminbar',1);ovcbar.php is where my markup is, the function name is ovc_admin bar..
this is all in functions.php
I really like how far beyond the default theme you’ve gone..I really wonder what it will look like with 1.2
Heres the real truth to all of this,
I want a facebook style gallery. Thats what I want. So when the bp-just-like-facebook-gallery plugin comes out I will rejoice and work it on my site.
Until then I think both applications are severely lacking in comfort and usability. I have only seen a site with bp-Galleries on it and it has some serious issues that I think will eventually be resolved but its alot closer then the other.
I have yet to try bp-albums so I cant give an honest review but since I already know it doesnt have more than one album I know its out.
I’ve started with bp-Galleries because I need to start themeing but the big fear is the the core team will eventually adopt a codebase that is different then that I am using. Then when I have 1000 photos on a defunct plugin what the hell will I do?
So with that I think it hugely important the the core decide on a path to go with this. If Brajesh wants to Open his code to the community so we can all contribute I think he should. Because I’ll be honest I’m already hacking the hell out of it. But I’m not going to go too far because he will release again and break my work..
I want to hack it, I want to break it, then I want to make it sing. So because Brajesh SAYS he will open it, I will stick with BP-Galleries, but since its also GPL if it starts to delay or stagnate I hope we as a community take it out of the box and get more hands on the code. Once Brajesh drops the paywall and lets some other developers offer patches, Ideas, or help I think the plugin will jump leaps and bounds. It is GPL so anyone who has it could redistribute it for free, or for $40,000 its whatever you want to pay for it.. Yay Open Source!
Or it will be replaced. I had plans to work on a plugin for a project of mine, but its so back burnner right now I cant see tackling that until the summer at earliest. But I think Brajesh is in the right path so for now I’m sticking with him.
