-
-
Notifications
You must be signed in to change notification settings - Fork 19
Allow developers to create complex domain access rules #2
Comments
I end up using an action instead a filter. It made more sense. The default logic uses the base URL from the plugin settings, this way:
A developer may create a custom logic adding a new function to Here is an example on how to use the action:
|
Following the support case in here, I think the plugin needs a way to prevent redirects based on custom logic. Keeping the current action hook, a filter also could be added. In case the filter returns an empty value ( |
Besides creating a custom redirect logic, one can also disable the built-in redirect using a new filter called
When the filter returns |
Added filter to programmatically disable redirects. Fixes #2
Despite the possibility of setting a base URL for each domain, it may be interesting to allow developers to create complex domain access rules. The behavior should be kept the same as we have today: if the user is accessing a disallowed URL he/she will be redirected to an allowed URL.
A filter is probably the best solution do achieve this:
The text was updated successfully, but these errors were encountered: