Forum Replies Created
hey r-a-y, thanks again.
just to be clear, i should be able to denqueue or whatever is necessary without mucking something up. that is, as long as is_buddypress() returns false then i don’t need all this BP “stuff”, yes?
@shanepb. Yeah, I’ve done that. But let me have another look.
You know how it is. Sometimes you get over-focused and things you thought you tried are actually things you meant to try but ran out of time in that moment 🙂
In any case, thanks again.
Well. Interesting. Cause that doesn’t seem to be what’s happening for me. I’m able to each the $arg being passed in and it’s spitting out a string, not array*().
I’ll have another look but I went round and round on this a couple days ago and kept thinking “where the heck is the array? why am I getting a string?
Thanks again @shanebp. As they say, “I’ll be back.”
I’ve mucked around with Roles and Caps here and there previously, but not in the context of BP.
I realize there’s a couple ways, I was just curious about best practices, and which membership plugin is a known for using with BP (as opposed to something that’s crap w/ BP).
Finally, is there a snippet I can put somewhere so that it’s easy to allow / prevent BP access – as opposed to doing something in multiple pages. I’m a BP n00b. This is my first true project with it so I’m still coming to terms with architecture, how it thinks, etc.
So type slowly so I don’t miss anything thing. Thanks. 😉
So shouldn’t my filter be receiving an array?”
If you can flesh that out really quick I’d appreciate it.
Agreed, this is far from ideal. I mean, even if you have users who are not admin but not subscribers either (e.g. editor), there’s at least some risk at the non-admin level. The obvious ideal would be to not use the user login credentials as user name. This is especially true if – for some reason – you want to use email address as user name.
Listen. I realize ANYTHING can be hacked if someone is up for the task. I’m simply suggesting trying to mitigate such risks.
Finally, let’s be honest, FB makes compromises because it’s not as interested in security as it is getting new users to sign up and then harvest as much personal details as possible. This is a flaw that WP / BP could be using to its marketing advantage if it wasn’t willing to follow the blind. Being alone is better than following and being wrong. At least that’s what mum always said 😉
1) That’s the only error dumping in the log
3) URLs – based on a sample – seem to be any / all. Again, as long as the user is logged in.
@henrywright – Yup. I hear ya. I just think in the spirit of weekly WP Security issues – which yes are quite often bad plugin code but none the less effect perception of WP – a bit more attention to detail would be nice. That is, the best practice would at least be to make it an option. Unless of course we’re talking about brain surgery then maybe I’ll just hope a couple aspirin and hope for the best 🙂
While I’m sure BP is flattered that you compare it to FB I’m not so sure that helps the rest of us who don’t have Mark Z “f*ck you” money to pay people to fix holes. That’s all 🙂
And thanks for Theme My Login, I’ll check that out. I hate testing new plugins only to find out they suck. Recommendations are always a bit plus. Cheers.
If it helps
1) I’m running ServerPress local. But I’m not pulling any random errors with anything else.
Other additional info:
2) Only happens when I’m logged in. No login === no error. That’s got to mean something.
3) I commented out bp_alpha_sort_by_key() in bp-core-functions.php. I then get an error from a call to that function at line 1847 – which is obviously kinda expected. But the original error disappears, which leads me to believe it’s something in that function. That question is, what?
This only week 2 of my working with BuddyPress. I wish I could be more helpful. Dev’ing with DEBUG off isn’t good. But with it on, I keep getting this error, which I can’t fix.
Any thoughts or recommendations? Please? Thx.
Metabox? I didn’t create no stinkin’ metabox 🙂
In fact, I looked at the BP core and didn’t see any hooks or filters for adding a metabox to the profile field page. This is why I had to use what’s already there (as-is) and make Editability and Visibility the same field (and store it in Visibility). I then parse that value as necessary.
But there is no metabox. Can’t be. It’s the same UI / UX both front and back but tricked out with some custom methods.
Does that help? Are you pulling errors?
WordPress might not, but that doesn’t make it right, does it? 🙂
Perhaps its just my comp sci education but a good DBA will tell you never have a field do “double duty” it can only lead to bad things.
A login name, and a communication / mention name are two very different properties. Two-step or not they really should be doing double duty.
Note: I’m not being a critic. That’s not my thing man 🙂 Just pointing out that a reasonable DBA would frown upon the current approach – especially in the content of the @mention of BP.
This is my first week w/ BP. I’m starting to realize the value of text search against the whole BP code base. That said, it’s a very sophisticated product so until I get a bit more comfortable with things I would rather ask than assume.
Might help. But isn’t there a way to figure out where that is set and change it? I’m mean it’s got to be in the DB as an option / meta or something, eh?
Basically, I’ve come up with a new list of visibility values and public is not one of them. I can code in an exception for name => public but that feels so hack-y, eh?
I’m back 🙂
Ok, I have it in a plugin and working 🙂 Thanks!
Now is it possible to use bp_register_template_stack(() with a class? When I tried
bp_register_template_stack(array($this, my-function/medthod-name) is funked up. So I had to move it outside my plugin’s class.
Was it me? Or BP?
Um. Oops. Either I’m reading too fast, or this isn’t exactly what I want.
Basically, instead of baking in the theme any of the templates I’m customizing, I want to move all the bp-legacy stuff into a plugin – so it’s not tired to the theme – and then tell BP to look for the templates there, not the theme.
I’m not really – yet? – changing what template to look for, only where to look.
Hey. Thanks again shanepb!
Can I suggest that the link you just gave me be added to the page I reference? I think it would help.
=> re: “Note that you need to add the correct id(s) for exclude_fields.”
Thanks shanebp. But is this the only way? I mean, I can’t do mucking with the code every time the client wants something new? Can I?
=> re: …/buddypress-xprofile-custom-fields-type/
“Add new visibility setting “Nobody”. Hide the field to all members.”
So this means, I presume that custom visibility is possible. Yes?
That said, I want to use standard fields, but I want to create the list via code, and not have to do it manually. Not possible? Mind you, it could be cause I’m new to BP but I’m trying to where / how the profile definitions are stored. I presume it’s an array, or close. So I want to do that but with code.