Forum Replies Created
-
In reply to: Friends and Groups for BuddyPress 1.3
Remember these are all just ideas and specific to the behind the scenes code. As far as the user interface is concerned there would be no overlap.
In reply to: Is wire broken in 1.2 bleeding edge?If you’re using the bleeding edge please report bugs in Trac, not here.
In reply to: Is BuddyPress confusing to users?Just add the profile fields in the backend.
In reply to: New BuddyPress 1.2 default themeYep, the original default is just renamed “classic” but has been updated. The wire has been completely removed from both the new and old theme and replaced with the new activity stream posting.
I will more than likely include the wire and status updates components in the “backwards compatibility” plugin for people to use with older themes.
I would consider it safe to begin working with the 1.2 theme. I expect there to be mostly bug fixes from now on. There is a chance thread favouring and/or reply notifications make it in before i freeze new stuff on Dec 30th, but it all depends on time. It should not change the theme though.
The final 1.2 should be out at the end of Jan.
In reply to: New BuddyPress 1.2 default theme@Mike Pratt – unfortunately previous to the change the links to threads were only being recorded with the group slug. Any posts from this point on will contain the link to the actual thread on the “View Thread” button.
In reply to: Activity DB Design DiscussionWe should really keep developer discussions such as this on trac, otherwise we will worry non-developers. None of the things we have talked about are certain, and there will always be some level of backwards compatibility.
In reply to: bp_core_add_message not showing anythingMake sure you the following somewhere in the template file you are redirecting to:
<?php do_action( 'template_notices' ) ?>Don’t change core files, you can pass a “per_page=XX” parameter into the template loop to change this.
In reply to: Activity DB Design DiscussionIn the end you have an activity stream class interface that basically says… you want to record activity? Ok, extend me and define these methods. You have to return data in exactly this format. Add yourself to my registry, and if you followed directions, I will do all of the heavy lifting for you. Otherwise, get lost.
I like this idea a lot, it introduces set structure which is important. It has to be easy to grasp though, I don’t want to increase the barrier for entry.
Once 1.2 is completed, let’s take a look at this is greater detail and come up with a solid activity stream API that we can move forward with.
In reply to: Activity DB Design DiscussionNot sure if you took my post on the other thread the wrong way, but it was meant to bring attention to the real problem, not to flame. Hopefully, I am not being labeled a troll here.
No no, I wasn’t taking anything the wrong way. I simply didn’t want to start a thread that encouraged flaming. The previous posts were constructive.
My reason for thinking the stream could become the hub was because it solves a lot of things that other components will want. Many components will want commenting, permalinks, edit/delete and the filtering the activity stream provides. It seems stupid to reproduce all these features for every component.
In reply to: Bug in the Group API with new theme (BP1.2)?These are really recent changes so I haven’t gone back and checked it. I’ll take a look at this later today and fix it up.
In reply to: New 1.2 SWA and Blog/Forum syncing: Feedback NeededI’m closing this thread since the conversation has moved on. Please continue over here:
https://buddypress.org/forums/topic/activity-db-design-discussion
In reply to: Buddypress SpamProbably because the spammers don’t recognize it as BuddyPress yet, don’t expect that to last long.
In reply to: New 1.2 SWA and Blog/Forum syncing: Feedback Neededone addl thought: if we went the route of disabling blog posts and forum replies, what is left to do on the SWA?
Don’t underestimate how much people will use the “What’s new John Doe?” box, since it is sitting there right in front of them. I can imagine that comments will mostly be on those updates.
In reply to: New BuddyPress 1.2 default themeD Cartwright: I’ve actually decided already to revert that, I don’t like it now I’ve had chance to use it for a while. I can fit the content in that menu inside of the header for the item.
In reply to: New 1.2 SWA and Blog/Forum syncing: Feedback NeededAlso with regards to removing excerpts – that seems as though it would remove a lot of the usefulness of the activity stream. I want to be able to scan the feed and get a taste for the content so I can click and read more of what grabs my interest. You really remove the ability to do that when it’s mostly posting one liners.
In reply to: New 1.2 SWA and Blog/Forum syncing: Feedback NeededTime is very limited before 1.2, there is not enough time to make this option so fine grained.
I think going ahead and introducing an admin option to disable/enable activity stream comments for blog and forum posts will suffice in 1.2? This option will mean commenting on forum and blog posts will be disabled by default, but you can turn it on.
In 1.3 this could possibly be changed to allow admins to pick and choose what is enabled. Although I’m still not convinced whether this should be something the admin has to think about at all.
In reply to: New 1.2 SWA and Blog/Forum syncing: Feedback NeededThe problem with all this syncing is that you’re making the need to visit the original content almost zero. I don’t think that’s a good thing.
In reply to: Activity Streams: Mergeyes: http://testbp.org/
In reply to: BuddyPress Editable Group Slugsjjj: just add an empty method in your group extension for widget_display()
In reply to: New 1.2 SWA and Blog/Forum syncing: Feedback NeededMy take is that a public group is public. The group activity shows on the site wide activity stream because of that. You must be a group member to post an original update in the group, but you do not have to be a member of the group to leave your comment on something that is openly public.
A private/hidden group is different, the activity will not show on the site wide stream, so you will need to be a member to comment or even see the activity when you visit the group.
I think for now it’s going to be too messy to try and start auto-joining people or thinking about permissions even further. Not to say that this won’t be thought about in greater depth after 1.2.
I’m not sure exactly how to handle the syncing of forum replies and blog post comments with the activity stream. I don’t want to make the original source redundant. It may be worth considering disabling comments on these items and instead providing a link to be able to comment at the location of the original content.
In reply to: New BuddyPress 1.2 default themeMy opinion right now is that I’m not going to spend any time on IE6. If someone wants to make the CSS changes needed in a separate file I will include the stylesheet with the theme.
In reply to: User / messaging exploit? Causing spamSpam is generally only a problem if you have blog registrations on, spammers only care about creating and spamming on blogs. I think some work will be done on this, but it’s not going to be on the BuddyPress side.
In reply to: New Default Theme Is AvailableStill report bugs, I still have lots to fix in the theme, it’s far from perfect right now.
In reply to: Spam from buddypress.orgI’ve spammed the user – please don’t re-post the messages in the forums since that sort of aids their cause.
