Forum Replies Created
-
In reply to: BuddyPress Links 0.2-RC1 now available
You ought to be able to use the ‘bp_located_template’ filter to be able to find templates within the plugin’s folder. Let me know if you get stuck.
In reply to: Member Widget timezone issueRight, I’m ninja’ing your thread Mike. I’m getting this exact problem, and if you Google for “Use GMT Timezone”, there are hundreds of results.
I’m also getting this problem when using the bp_core_time_since() function in my blog theme’s header. What’s going on?
In reply to: User / messaging exploit? Causing spamI’ve given up trying to add gmail-style folder tagging to the messages system in BP at the moment via a plugin; there’s not enough hooks to filter some queries. Might hack the core and do a patch
When you say you want a seperate forum install, what *exactly* do you mean/want as a result?
Do you want a different theme or user interface to access the forums? Do you want it to be like a traditional forum site rather than BuddyPress’ group interface?
In reply to: Slug Change = how to change name of group urlEdited the title and marked as resolved to help people find this via search in future.
In reply to: Where/how to download the latest bleeding edge beta?Peter’s been around these forums for a while, so he might be wanting to move to a svn checkout to make life easier
In reply to: Where/how to download the latest bleeding edge beta?Lots of theme development and fixes still going on. What you need first of all is an SVN client. I don’t know which OS you run, so I can’t suggest a specific client.
In reply to: Sub-Blog Doesn’t Show Blog PostsYou only get /blog/ if you’re using the default BuddyPress theme. In fact, that’s what the code above should be doing – it handles this sort of URL – http://utahdogs.com/blog/2009/12/15/suggest-links/
I think there’s a bit of confusion here.
You’re using a WPMU install (subdirectory type). So ‘parks’ is a hosted blog, which you can therefore access at http://utahdogs.com/parks/. You’re also using the default theme for hosted blogs; the default theme it isn’t built to support that and you are going to get weird things happening with the URLs in the menu, for example.
Ignoring those, your root blog is accessible at /blog/. This is because the root blog has to provide all the member pages, groups, and so on, so there has to be a special URL provided to be able to get to the actual *blog*.
Um. I think we’re missing why you need to run two bbPress installs?
In reply to: Slug Change = how to change name of group urlJames, have a look at https://codex.buddypress.org/how-to-guides/customizing-labels-messages-and-urls/
In reply to: Only selected plugins on member blogs?can you guarantee that ANY plugin that works on WPMU also works on Buddypress? And works for all features of BuddypressNo, we can’t. I’m also closing this thread as it’s two months old and now off-topic.
In reply to: Activity DB Design DiscussionMy visualisation of this discussion is to forget the concept of what A. Streams were, and instead envisage the new SWA as a kind of super-Wire; with threaded commenting, permalinks and supporting more media types than just text, whilst retaining the ability to be able to use it anywhere (you were able to use the Wire in custom components easily).
Is that where the discussion is up to, and moving on to discuss how to map forum posts and blog comments into this?
I’ve not seen any. My Achievements plugin sort of does this in some ways, but it isn’t intended to be a user stats plugin.
In reply to: New 1.2 SWA and Blog/Forum syncing: Feedback NeededDigging up obscure PHP error messages means you just have to fix them John
In reply to: BuddyPress Editable Group SlugsThat’s a cool message. Google suggest it means “missing double dots” aka ::.
Are you trying to call a static class function from a dynamic variable thingy? e.g.
$myvar = ‘something’;
$myvar::explode_world();
In reply to: New 1.2 SWA and Blog/Forum syncing: Feedback NeededI’m not convinced that comments should be fed back to blog posts, as per Andy’s first post on the thread.
In reply to: New 1.2 SWA and Blog/Forum syncing: Feedback NeededWith regards to blog or forum posts – I may not/do not want to autojoin the group.
Another thought: Maybe an admin option to turn off excerpts in activity would
prevent forking. When I post a new blog or forum post, an update might appear
on the activity feed that says "Boone posted a new blog entry: Boone's
Blog Post", but without an excerpt. People could still comment in ways that
make sense ("Boy Boone, you blog a lot") but they wouldn't really be able to
leave substantive comments on the content of the blog entry/forum post, since
it wouldn't appear on the activity stream.
(Boone Gorges)+1
In reply to: external bbpress + buddypressYes.
In reply to: User / messaging exploit? Causing spamWhat we need, is a spam bin. I has an ideas. Let me mock it up.
In reply to: User / messaging exploit? Causing spamPlease, please, please – we don’t really need to see these spam message contents are they are pretty much identical, and we certainly don’t need email address or URLs posted as they help the spammers’ cause.
In reply to: User / messaging exploit? Causing spam– Anyway, I think a very good start is that you can only message your friends. Thought that this would be already ths case, that is why I wondered how we could get spammed?
In my case, I need to be able to receive messages from anyone. Such a thing needs to be a per-person decision/setting.
In reply to: User / messaging exploit? Causing spamRather than complaining that the sky is falling, how would you propose we resolve this issue? A captcha on the Messages screen (or at least making sure hooks are in to allow a plugin dev to add this)? Messages sent only to friends?
In reply to: Can’t delete forum topicsPlease look at https://buddypress.org/forums/topic/when-asking-for-support
In reply to: compose message, send to usernameThis is the way it works at the moment. If you want it changed, create an enhancement ticket suggestion on https://trac.buddypress.org/ using the username/password which you use for this site.
At the minimum, yes, that error message ought to be improved.
I’m marking this thread as ‘not a support issue’ as this is working the way things should be working at the moment.
I think this URL is hardcoded in wp-login.php which, as it is hardcoded, we can’t change?