[buddypress-trac] [BuddyPress Trac] #8683: BP .htaccess rule causes server CPU spikes

[buddypress-trac]

#8683: BP .htaccess rule causes server CPU spikes
--------------------------+------------------------------
 Reporter:  kuznacic      |       Owner:  dcavins
     Type:  defect (bug)  |      Status:  assigned
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Core          |     Version:  10.2.0
 Severity:  major         |  Resolution:
 Keywords:                |
--------------------------+------------------------------

Comment (by kuznacic):

 @dcavins Thanks for the reply. I am still investigating this issue but so
 far have not found anything definitive.

 Furthermore, the "fix" that was implemented by Cloudways (renaming the
 .htaccess file in /wp-content/uploads/bp-attachments so that it does not
 rewrite the media URLs) has essentially disabled BP Docs as now users
 cannot even see them in their BP profiles and groups.

 Because the ability to upload and share documents via BP is a major part
 of my client's BP site, I have undone the "fix" so that media URLs are
 being rewritten (e.g. ?bp-attachment=13109/NorthCrawford-300×225.jpg) but
 this means we are back at square one and the server CPU is spiking
 whenever a logged-in user accesses the WP media library (/wp-
 admin/upload.php).

 Coincidentally, our paths have crossed previously because of this issue --
 you chimed in on a thread in the BP Docs support forum on wordpress.org
 back in February 2021 when I was receiving the notice, "Your BuddyPress
 Docs attachments directory is publicly accessible. Doc attachments will
 not be properly protected from direct viewing, even if the parent Docs are
 non-public."

 Link to thread:[https://wordpress.org/support/topic/allowoverride-
 problems/]

 I am curious if you believe that the solution that Cloudways implemented
 might be a cause of the issue this site is experiencing with CPU spikes
 when accessing the WP media library? To my knowledge all was working
 properly from the time this was implemented in Feb. 2021 until my client
 reported an issue to me in March 2022. But, perhaps a recent WP or BP
 update might have altered something?

 I will continue to investigate and troubleshoot on my end, but wanted to
 get your thoughts on this. Any advice or guidance you can provide is very
 much appreciated.

-- 
Ticket URL: <https://buddypress.trac.wordpress.org/ticket/8683#comment:4>
BuddyPress Trac <http://buddypress.org/>
BuddyPress Trac