You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This plugin is "all in". There is no way to say all posts of post type X can use a WordPress theme, but everything else redirect to front-end, or to allow a certain page/ post to be allowed.
If a plugin adds a custom rewrite rule, it is probably blocked, which may be bad.
Solution
Add a filter that is the final decider of if request is blocked or not.
Add a UI that allows for a adding paths to allow. Should be able to use * paths:
Hey! We're now using this plugin on wpcampus.org. We definitely need a filter to help determine who gets access to the front end so will be adding a PR for the filter.
@bamadesigner do you still have this need? I vaguely remember a PR that was merged that might have fixed this, but I am not confident, nor have I poked around much.
Problem
This plugin is "all in". There is no way to say all posts of post type X can use a WordPress theme, but everything else redirect to front-end, or to allow a certain page/ post to be allowed.
If a plugin adds a custom rewrite rule, it is probably blocked, which may be bad.
Solution
Add a filter that is the final decider of if request is blocked or not.
Add a UI that allows for a adding paths to allow. Should be able to use
*
paths:/blog/hi-roy
-> Allowhttps://site.com/blog/hi-roy
/products/shirts/*
-> Matches anything starting withhttps://site.com/products/shirts/
Mockup - I made this by using the inspector to mock up using the page for the simple 301 redirects plugin on calderaforms.com
The text was updated successfully, but these errors were encountered: