#6914 closed enhancement (fixed)
bp_locate_template() in WordPress Administration
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 2.6 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Core | Keywords: | dev-feedback |
Cc: |
Change History (10)
#2
@
9 years ago
imath tested removing the checks and running unit tests, apparently everything worked correctly. So, for 2.5, we have two options:
1) Leave as-is and tell people to use new filter in r10594
2) Or remove the WP_USE_THEMES + DOING_AJAX checks.
This ticket was mentioned in Slack in #buddypress by djpaul. View the logs.
9 years ago
#6
@
9 years ago
As tempting and maybe convenient that might be for developers using bp_send_email
in custom situations, I think my last suggestion was over-eager.
#7
@
9 years ago
- Owner set to DJPaul
- Status changed from new to assigned
I'm going to remove the checks. YOLO (aka BuddyPress 2.6.1-paul-messed-up).
Note: See
TracTickets for help on using
tickets.
I think we might need to bring this forward despite r10594.
@modemlooper had some code that sends an email for new comments https://gist.github.com/modemlooper/8aeb3b03e2a58f1a129e and this fails in exactly the same place. Dealing with new comments is so trivial I am embarrassed if our solution is "filter something on and off".
I looked back through this line's history: r7842 and r7837. I guess we need to next remove these checks and run unit tests and debug what's happening.