Page Guard Redirect uses a single URL parameter or POST variable as a means of providing a token to guard access to any page on which this plugin's shortcode is placed - redirection can be made to occur when the token fails to match what is expected (the alternative, i.e. redirect when token DOES match - is also included for completeness.)<\/p>\n\n
The shortcode to use is 'pgredirect' - its attributes are:<\/p>\n\n
tokenparam (required): a string value containing the name of the token URL param - e.g. 'mytoken'\ntokenvalue (required): a string value containing the expected value of the tokenparam - e.g. 'x34ggj45b'\nredirectURL (required): a string value containing the URL to redirect to (you can use an existing page as the target for the redirection - alternatively, for many configurations, setting this to a non existent page will make WordPress redirect to the default 404 \"not found\" page.)\nredirectWhen (optional): -> when = \"1\", redirects when match is found, otherwise defaults to redirect on non-match\n<\/code><\/pre>\n\nSyntax examples:<\/p>\n\n
redirect on non match (default) -\n [pgredirect tokenparam=\"mytoken\" tokenvalue=\"1234abcd\" redirecturl=\"http:\/\/my.redirurl.com\/notfound\" \/]\n\n redirect on match (add redirectwhen=\"1\" as an attribute) -\n [pgredirect tokenparam=\"mytoken\" tokenvalue=\"1234abcd\" redirectwhen=\"1\" redirecturl=\"http:\/\/my.redirurl.com\/notfound\" \/]\n<\/code><\/pre>\n\nUsage<\/h3>\n\n
A typical use scenario might be to prevent access to a downloads page. Suppose you have a PayPal \"Buy Now\" button on your site which allows visitors to make a payment for say, an eBook or audio recording. When setting up the button in your PayPal account you specify a URL on your site to which the visitor is returned after they've made payment. On this return page you've added a link the visitor can use to download their purchase - however, you don't want any non paying visitors to find the return page by chance!<\/p>\n\n
Add a parameter to the end of the return URL (using any name and value you want) when you set up your button in PayPal e.g.<\/p>\n\n
\"http:\/\/your.wordpress.site\/download\/?dltoken=Xc345Fd77\"\n<\/code><\/pre>\n\nNext, add a pgredirect short code to your return page in WordPress -<\/p>\n\n
[pgredirect tokenparam=\"dltoken\" tokenvalue=\"Xc345Fd77\" redirecturl=\"http:\/\/your.wordpress.site\/notfound\" \/]\n<\/code><\/pre>\n\nThis will cause a redirect if Page Guard Redirect detects either the lack of the expected token in the URL parameter, or a value which doesn't match the one in the short code's tokenvalue attribute.<\/p>\n\n\n
\n- To install the plugin, download the zip file and upload via the plugin interface of your WordPress site or install the plugin through the WordPress plugins screen directly.<\/li>\n
- Activate the plugin through the 'Plugins' screen in WordPress<\/li>\n<\/ol>\n\n\n
\nCan I use any name for my URL token parameter<\/h3><\/dt>\nYes you can! You might like to use somewhat obfuscated token names as well as values in order to further minimise the possibility of a visitor finding your protected page purely by chance e.g.<\/p>\n\n
\"http:\/\/your.wordpress.site\/download\/?cck4634kep=spefe4639\"\n<\/code><\/pre><\/dd>\n\n<\/dl>\n\n\n1.1<\/h4>\n\n
Added a filter to enforce use of classic editor when editing any page containing a pgredirect short code. The new block (Gutenberg) editor was found to run pgredirect's code rather than ignoring it, resulting in a redirect away from the page needing editing.<\/p>\n\n
1.0<\/h4>\n\n
First implementation<\/p>","raw_excerpt":"Adds a short code which allows page redirection based on the value of a token passed as a URL parameter or POST variable","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/eo.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/55210","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/eo.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/eo.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/eo.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=55210"}],"author":[{"embeddable":true,"href":"https:\/\/eo.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/fculross"}],"wp:attachment":[{"href":"https:\/\/eo.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=55210"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/eo.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=55210"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/eo.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=55210"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/eo.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=55210"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/eo.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=55210"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/eo.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=55210"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}