[buddypress-trac] [BuddyPress] #3508: Associate two BuddyPress components with the same WordPress page

buddypress-trac at lists.automattic.com buddypress-trac at lists.automattic.com
Tue Aug 23 21:45:19 UTC 2011

#3508: Associate two BuddyPress components with the same WordPress page
 Reporter:  masonjames      |       Owner:
     Type:  defect          |      Status:  new
 Priority:  minor           |   Milestone:  1.5
Component:  Administration  |     Version:  1.5
 Severity:  minor           |  Resolution:
 Keywords:                  |
Changes (by boonebgorges):

 * priority:  normal => minor
 * component:  Settings => Administration
 * severity:  normal => minor
 * milestone:  Awaiting Review => 1.5


 This ticket was worthwhile if only so that I could learn the word

 Good catch with this problem. I would say that the behavior itself (one
 component works while the other one fails) is expected - there's not much
 we can do about it. As for your two suggestions, disallowing already-
 selected pages is a nice idea, but there are lots of implementation
 problems. Ideally, we'd have some sort of javascript slickness on the
 Dashboard page that removed used pages from the dropdowns, in addition to
 some server side checks, but that is pretty complicated, especially at
 this point in the dev cycle.

 I think we can fairly easily create a warning message. It should probably
 go in bp_core_activation_notice(), with other such notices. If anyone
 wants to work up a patch, it should be pretty straightforward. Otherwise I
 will try to get to it this week. (Putting in the 1.5 milestone, though I
 think it's fairly minor and could be bumped if absolutely necessary).

Ticket URL: <https://buddypress.trac.wordpress.org/ticket/3508#comment:1>
BuddyPress <http://buddypress.org/>

More information about the buddypress-trac mailing list