Skip to:
Content

BuddyPress.org

Changes between Initial Version and Version 1 of Ticket #7847, comment 7


Ignore:
Timestamp:
05/22/2018 10:21:54 AM (7 years ago)
Author:
imath
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #7847, comment 7

    initial v1  
    1 I chose a 3rd approach. The idea is to change as fiew as possible for plugin authors. I think the new Messages UI is a perfect candidate for the [https://github.com/buddypress/BP-REST/blob/master/includes/bp-messages/classes/class-bp-rest-messages-endpoint.php BP Rest API], so untill we can count on it and why not deprecate some actions in favor of this API, i think we shoul use the existing actions and catch their content using the buffer. As this is done within a messages loop, data is accessible via PHP and it doesn't change anything for plugin authors. Here's a screenshot showing injected content using {{{bp_before_message_content}}} & {{{bp_after_message_content}}} :
     1I chose a 3rd approach. The idea is to change as fiew as possible for plugin authors. I think the new Messages UI is a perfect candidate for the [https://github.com/buddypress/BP-REST/blob/master/includes/bp-messages/classes/class-bp-rest-messages-endpoint.php BP Rest API], so untill we can count on it and why not deprecate some actions in favor of this API, i think we should use the existing actions and catch their content using the buffer. As this is done within a messages loop, data is accessible via PHP and it doesn't change anything for plugin authors. Here's a screenshot showing injected content using {{{bp_before_message_content}}} & {{{bp_after_message_content}}} :
    22
    33[[Image(https://cldup.com/wXf19swDlL.png)]]