bp_filter_request: What does it do and how does it work?
-
Can somebody help me pick this thing apart w/ a fork? I’ve been trying to parse it on my own with some success. I realize it has a global scope, can be called globally, and can be fed certain variables to get different ajax results.
So, for example, from the members directory page, when a user clicks on one of the pagination items, bp_filter_request handles a certain number of variable that are posted to “http://arxnew.tld/wp-load.php” (ajaxurl is the variable). But how are these variable processed (wp-load.php doesn’t seem to be doing the handling — where is this taking place?)
Some of the variables posted, for example, might look like this:
action: “members_filter”,
‘cookie’: “wp-settings-1%3Dm5%253Do%2526m9%253Dc%2526m0%253Do%2526m8%253Dc%2526m7%253Dc%2526m6%253Dc%2526m4%253Dc%2526m3%253Dc%2526m2%253Dc%2526m1%253Dc%3B%20wp-settings-time-1%3D1268530134%3B%20bp-members-filter%3Dnewest%3B%20bp-members-scope%3Dall%3B%20bp-activity-oldestpage%3D1”,
‘object’: “members”,
‘filter’: “newest”,
‘search_terms’: “Search anything…”,
‘scope’: “all”,
‘page’: 2,
‘extras’: nullBut what does it all mean, and how can I figure out what the different responses will be based on input? Very confused…
- The topic ‘bp_filter_request: What does it do and how does it work?’ is closed to new replies.