Forum Replies Created
-
In reply to: BuddyPress 1.2.5 tickets are cleared out
@DJPaul –
Because, as you state in the Trac ticket thread, IE 7/8 does not support the :nth-child selector in CSS. But it will work when it’s used in JQuery. It is a simple, single line fix — at least for the alternate table row highlighting.
In reply to: BuddyPress 1.2.5 tickets are cleared outOkay, see my most recent post in that Trac ticket. I’ve discovered that :nth-child selector is not recognized by IE 7/8 when used in CSS but it does work in those IE versions when used via JQuery. So, my proposed fix should work like a charm.
In reply to: BuddyPress 1.2.5 tickets are cleared outSee the two new screenshots uploaded to https://trac.buddypress.org/ticket/2465#comment:15
@hnla — I agree. Unfortunately, IE 7 and 8 do not support the simple JQuery fix. However, IE 9 is finally with the program on this issue. But, there are other ways to strip a skunk.
In reply to: BuddyPress 1.2.5 tickets are cleared outI’m removing the alternating highlighting from the Privacy Component for the time being. The “fix” still has issues. It still selects for the entire form and not per table. If you add another row to the outputted settings tables in the Activity, Messages, or Friends form coding, you will see the issue when navigating to “Settings > Notifications” in your user profile menu.
It is an issue of odd versus even rows in a given table. Right now, since all the outputted tables (a total of four tables are outputted to make up the aforementioned screen) each have an even number of rows, it appears that all works fine. But by doing what I suggest–adding a test odd row–you will see the problem.
In reply to: Need Testers: Activation Issue with BP v 1.2.5@hnla: I should have been more clear. With WP3.0, the “Activate” link for BuddyPress is replaced with “Network Only”. To activate BuddyPress, you have to click the “Network Activate” link.
I have tracked down this issue. It is specific to WP 2.9.2 only. I thought I was seeing it in both WP 2.9.2 and WP 3.0. But, after reinstalling everything, I can only reproduce it in WP 2.9.2.
Would someone please confirm this on a WP 2.9.2 install. I suppose it could be a quirk in my dev setup, but this issue did not exist with the four or five 1.2.5 branch versions that I tested yesterday.
If others can replicate this issue, then the “Requires at least” tag in BP’s readme.txt file should be changed to WP 3.0. Otherwise, we will have people activating BP for a single blog, and not site wide–that is if they just click the “Activate” link in WP 2.9.2.
Do we need to updated the information for plugin devs? Should they include the “Network: true” tag in the header of whatever file they consider their loader file?
In reply to: Need Testers: Activation Issue with BP v 1.2.5Very strange. I’m going to delete my dev sites, reinstall WP and BP, reboot and see what happens. I’ve already cleared out caches, cookies, and rebooted several times. Perhaps I shouldn’t be using my Commodore PET to run my dev sites. I’m also going to try on my other two MacBook Pros.
In reply to: Is WP Supercache okay to use with BP?There’s also this Codex page that has some useful advice for improving performance.
In reply to: upgrading 1.0.3 site to 1.2.4As always, first backup everything.
Then, read the instructions in this codex article for Upgrading from 1.0.x to 1.2.x. I would also search the forums to see what issues people may have had with this process. As I upgrade with each new version, I have zero practical experience with such a big upgrade.
In reply to: Something funky going on please helpWe do not have enough information to help you. Please answer these questions: https://buddypress.org/community/groups/how-to-and-troubleshooting/forum/topic/when-asking-for-support/
In reply to: what’s expected for 1.2?In reply to: Is bp dying a slow death?I’ve been watching this thread since @anointed ‘s first post and have been hesitant to jump in as most community members view moderators as part of the core team. So first let me state, as has been periodically stated in the past by other members and moderators, that I am not part of the core BuddyPress team.
The core BuddyPress team currently consists of three people: @apeatling, @johnjamesjacoby, and @MrMaz. Within that core team, only @apeatling is employed by Automattic. The other two volunteer their time and energy to the project.
My association with the BuddyPress project is as a volunteer–as a moderator on the BP.org site and as a independent BP plugin author. As a non-core volunteer and moderator, I do not have any special knowledge or an inside track to the discussions of the core team. Everyone has the same access as I do via the biweekly dev chats on IRC.
So what I post is just my personal assessment. This is not a proclamation about the project. These are solely my thoughts and observations based on informal discussions with others.
Any nascent project experiences bursts of intense activity, followed by lulls as excitement wanes for awhile and people catch their breath, preparing for the anticipated next big burst of activity. This is common at least for successful projects. BuddyPress is no exception. I have observed three or four of these bursts over the past 16 months or so. That is as long as I have been involved with the project and therefore my entire BuddyPress timeline. I would imagine that the project experienced one or two noticeable bursts farther back than 15 months.
Is the recent lull a sign of a slowly dying project? Does Andy’s apparent lack of activity in the project’s bleeding-edge version (aka Trunk) point to deeper issues concerning the future health of the project?
I can of course only speculate, using my previous experience with other Open Source projects as data points. But I will not venture a guess as some might surmise my thoughts to be the truth. Instead I will address this thread’s hypothesis with a few thoughts.
First, I will address my recent lack of activity on the BP.org site. It can be attributed to five factors:
1. I took some time off to attend a family reunion
2. When the new BP.org redesign was launched, it dramatically changed the way support topics where organized and managed. From a moderator’s standpoint, I believe it became more difficult to effectively moderator the conversations.
3. I have other projects that need my time. As I do not get paid to moderator and I have earned only $325 dollars from my BuddyPress activity (in the form of plugin donations), other projects have priority.
4. I needed a break from the community. Before the site’s redesign and relaunch, I was the moderator with the most activity and highest post count. That past history was lost (at least is not reported anymore) with the new design as the old external bbPress forum install gave way to the new internal, group-based bbPress forum install.
5. I’ve been working on the BuddyPress Privacy Component.
Now, on to more pertinent thoughts:
* I believe that the official project site of any Open Source project needs to have a strong showing (presence) by the core team members. It demonstrates the team’s commitment to the project and community. As it currently stands, there is little active involvement on BP.org by the core team members as evidenced by their forum post count.
* The community currently has a single person as project gatekeeper. Andy has ultimate control over the BP.org site, Trac, and the overall project codebase. It is difficult for an Open Source project to thrive in the long term when that is the case. Of course, this is Andy’s creation and he was hired by Automattic to continue the build out of BuddyPress. I’m not sure whether Automattic now owns the copyright to BuddyPress or in fact who owns the copyright. But, keep in mind, that BuddyPress is another Automattic project and Automattic is a for-profit corporation that has graciously provided Andy’s services to keep the project going. BuddyPress is not an Open Source project that is created by, run by, and owned by the community. It is not an Open Source project managed by a not-for-profit entity. What does this mean? Ultimately, it is up to Automattic, and not the community, to decide what happens to BuddyPress and the BuddyPress brand.
* BuddyPress needs to have more active, core developers with commit access.
* Andy needs to communicate with the community on a regular basis, responding to inquires in a more timely manner. Of course Andy deserves rest and time off from the project, especially since over the past two years (or more) he has put in yeoman’s duty. But proactive communication from him would go a long way as to keeping the community informed. It may help bring back the excitement that once seemed to permeate the overall community.
* Finally, we all owe Andy a great deal of gratitude for creating a wonderful alternative to the current social networking platform morass. He is responsible for the vast majority of the codebase and has been very open to feedback and new ideas. If he chooses to move on to another project or company (and I am not saying that is the case as I have absolutely zero inside knowledge), we should simply wish him good luck and thank him for his hard work on BuddyPress.
I will end with a link to an article I wrote on my website six months ago pertaining to project management and leadership. Whereas it is not an article about Open Source projects, there are a few key points that apply to projects of any type.
In reply to: Privacy component–where is it?rich! @ etiviti ( @nuprn1 ) –
Have you seen my WordPress Hook Sniffer Plugin? I created it out of necessity to figure out all the BuddyPress hook issues I was having.
In reply to: Privacy component–where is it?@gezan –
This one in particular. It is also needed for all plugin developers as well!
https://trac.buddypress.org/ticket/2325
jjj has issued his own patch. I’m not sure why mine was not accepted and why his has not been implemented. It is a complex issue but with simple fixes that I detailed and provided in the patch. With my fixes, everything works well.
In reply to: Privacy component–where is it?The BuddyPress Privacy Component is practically finished. However, I’m still waiting on a few patches to be added to BuddyPress. Hopefully the 1.2.5 release will incorporate those. If not, I’ll need to refactor a few functions to work around various BP hook issues. I’m also waiting on the release of WP 3.0.
As you may know, plugin developers can only estimate when bug fixes, patches, and new core releases will happen. My guesstimates have been way off as of late. But, once these issues are addressed in core and WP 3.0 is released, the Privacy Component will be released.
In reply to: Is BuddyPress Install Currently Broken?Make sure that your WordPress installation is working before adding BuddyPress. Your hosting package must meet these requirements at a minimum. Also, as rich! @ etiviti ( @nuprn1 ) states, you can learn a lot about potential install issues by checking your server’s log files.
In reply to: Buy themesI’m closing down this thread as you have the contact information of the OP if you are interested in their theme work.
@ferhat –
You are going to have a difficult time selling your themes if you do not have an active website that demos your works for sale. Asking people to contact you via email so that you can then send them a theme once they’ve sent you money is always going to be treated with suspicion. You need to earn the trust of your potential clients first. Showing that you are serious about your work and supporting your potential clients after purchasing your themes is just one step toward earning their trust and their money.
Finally, as others have said within this thread, the BuddyPress.org community does not look favorably on those who only ask and do not give. When you have created a website that demonstrates your work, you should feel free to post a new thread with a link to your website. But please do not simply come here to paste overt, commercial messages.
I’m glad that you find the WP Hook Sniffer useful. Thanks for the donation!
I had @mikepratt download it today to help him out with an add_action function that was not firing.
@mercime –
Yeah, that was my suggest above as well.
In reply to: Alternative to Facebook@arxpoetica et al –
I just created the private BP group Semantic Web and Open Stack Integration to focus our discussions. As it is a private group, you must request membership. I felt it was better to create a private group so that we could ensure the conversations are maintained at the proper level.
That is a good point. However, since BP.org is currently pulling in all plugins that include the “buddypress” tag, there is not much we can do. If we had a BP.org plugin and theme moderator, that would be different!
In reply to: Buddypress 1.2.3 to 1.2.4 ugrade FAIL!You must always deactivate any BuddyPress-specific plugins before upgrading or reinstalling BuddyPress. That is why your first attempt failed. Moving your plugins outside of the /plugins directory basically accomplished that for you.
https://codex.buddypress.org/getting-started/upgrading-from-10x/
From that Codex article:
“…it’s a good idea to disable other BuddyPress plugins first of all”
Since BP 1.2, all BP-dependent plugins should have code that will prevent them from firing if BP is not activated. However, some plugin devs have not added that coding to their plugin so you can have issues.
In reply to: Alternative to FacebookIt depends on your definition of “near future”. Since all authentication is handled by WordPress, not BuddyPress, this project is truly a WordPress-specific feature. We are forming a group to work on this issue and also discuss the possibilities of implementing Semantic Web and / or Open Stack protocols in BuddyPress.
But, this will not be a core WP feature–at least not in the near term. I imagine that we will let the WP 3.0 series work out any new issues once that series is released. So, sometime around the WP 3.1 or 3.2 public release might be a reasonable target for releasing a WebID plugin for WP.
Do you have any specific interest and / or experience with WebIDs?
The real issue is that any plugin in the WP Plugin Repo that is tagged “buddypress” is automatically listed in BP.org’s Extend Section. So, any plugin dev that uses that tag will have their work listed.
We could request that plugin devs use the tag “buddypress-compatible”, instead of “buddypress”, when tagging plugins that are not dependent on BP but can run under BP. This way, only those plugins that are truly BuddyPress specific (dependent) will be listed in the BP.org Extend Section. Of course, it would be up to each plugin dev to honor that request.
In reply to: Alternative to FacebookI couldn’t access the link. Chris’ site just keep trying to load and then threw a 503. I’ll try again later.
In general, as you know, I have issues with using OpenID in a distributed environment because it requires a lot more server calls and a 3rd-party provider / verifier. This basically locks individuals back into the same mantra of depending on another provider. Decentralized services are best, IMO, managed and controlled by each individual. This is where FOAF+SSL-backed WebID shines. It does not require a 3rd-party authenticator and the process takes significantly fewer steps.
Of course, that does not preclude offering both options–the Open Stack and their SemWeb counterparts.
In reply to: Privacy component–where is it?@raoul2 –
Yes, users will be able to turn off friend requests. The Component is pretty solid right now. I’m still waiting for BP 1.2.4 to come out. But, either way, look for the new beta release at the time of WordCamp Chicago or soon after.
