Title: Allow requests through custom process
Last modified: September 15, 2023

---

# Allow requests through custom process

 *  Resolved [squarestar](https://wordpress.org/support/users/squarestar/)
 * (@squarestar)
 * [2 years, 8 months ago](https://wordpress.org/support/topic/allow-requests-through-custom-process/)
 * I have 2 sites on which I have a custom function running on the `init `hook. 
   The code requires a user to be logged in under some circumstances. Currently 
   it seems to be blocking the WPRUS communication between the two sites.
 * Is there something I can check for that will allow me to identify WPRUS requests
   and allow them through this process? Like a POST element or other globally available
   variable?
 * Thanks

Viewing 1 replies (of 1 total)

 *  Thread Starter [squarestar](https://wordpress.org/support/users/squarestar/)
 * (@squarestar)
 * [2 years, 8 months ago](https://wordpress.org/support/topic/allow-requests-through-custom-process/#post-17053423)
 * Actually I answered my own question by logging the $_POST array and finding an
   element I can check for.
 * Thanks for the plugin 🙂

Viewing 1 replies (of 1 total)

The topic ‘Allow requests through custom process’ is closed to new replies.

 * ![](https://ps.w.org/wp-remote-users-sync/assets/icon-256x256.png?rev=2260728)
 * [WP Remote Users Sync](https://wordpress.org/plugins/wp-remote-users-sync/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wp-remote-users-sync/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wp-remote-users-sync/)
 * [Active Topics](https://wordpress.org/support/plugin/wp-remote-users-sync/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wp-remote-users-sync/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wp-remote-users-sync/reviews/)

 * 1 reply
 * 1 participant
 * Last reply from: [squarestar](https://wordpress.org/support/users/squarestar/)
 * Last activity: [2 years, 8 months ago](https://wordpress.org/support/topic/allow-requests-through-custom-process/#post-17053423)
 * Status: resolved