MarcusPope

<p>A WordPress plugin that converts all URL formats to root-relative URLs to enable seamless transitioning between staging/production host environments and debugging/testing from mobile devices, without the use of hackish tactics like textual find-replace strategies or risky hosts/NAT spoofing strategies.</p>
<p>With Root Relative URLs you can browse your development site from http://localhost/ or http://127.0.0.1/ or from a named network resource like http://mycomputername/ without worrying about links redirecting you back to your site’s URL.</p>
<p>This plugin also modifies the tinyMCE hooks so links and media embedded with built-in tools will only insert URLs from the first forward slash after the domain (i.e. the root of your site.)  This means when you push content changes to a staging or production environment they are guaranteed to reference the correct target instead of accidentally referencing a production resource in development or, worse-yet, a development-exclusive resource in production.</p>
<p>It supports path-based MU Installations, but does not support domain-based MU sites due to architectural deficiencies in the WordPress core.</p>
<p>Version 1.5 fixes an infinite redirect problem that is a result of a core bug in WordPress.  If you have problems with the <!–more–> tag or permalinks for custom post types, please read the FAQ or new Install Steps for support.</p>
<p>Version 2.2 allows for adding certain URL’s or partial URL’s to a blacklist, meaning I won’t use root relative urls, but dynamic absolute URLs instead for displaying content.  This will fix problems with 3rd party plugins, and can be configured on the General Settings page.</p>
<h3>Arbitrary section</h3>


Root Relative URLs

Converts all URLs to root-relative URLs for hosting the same site on multiple IPs, easier production migration and better mobile device testing.

Jeremy B. Shapiro

<p>The URL Params WordPress Plugin allows you to access URL parameters in the Query String of the URL.</p>
<p>The plugin even allows you to specify a default value in the shortcode if the parameter isn’t set, so if you want to say “Hello, FirstName” and FirstName isn’t set, it could say something like “Hello, Friend!”</p>
<p>To specify a backup url parameter, enter multiple parameters seperated by commas. The plugin will check for each parameter, in order, until a matching one is found and return that. Failing finding any of the parameters you listed, the default will be returned. For example, you can specify <code>[urlparam param="FirstName, First, name" default="Friend" /]</code> to check for FirstName, and if not found, then First, if not found, then name, and if not, then just return “Friend”.</p>
<p>If the parameter is a date, you can also specify the <code>dateformat</code> option using a <a href="http://php.net/manual/en/function.date.php" rel="nofollow ugc">PHP friendly date format</a>, for example <code>[urlparam param="somedate" dateformat="F Js" /]</code>. Note that PHP only returns dates formatted in English regardless of locale settings.</p>
<p>This is great if you have personalized links, like from Infusionsoft or Keap, as it lets you personalize a landing page with a persons name.</p>
<p>You can also use this to pre-fill out form fields for folks based on the querystring. For example, if their first name is passed in the URL, your landing page can greet the viewer by name and pre-fill their name on a form.</p>
<h3>Usage</h3>
<p>Use the shortcode urlparam with the optional parameter of “default”. For example <code>[urlparam param="FirstName" /]</code> or <code>[urlparam param="FirstName" default="Friend"/]</code>.</p>
<p>For conditional content use <code>[ifurlparam][/ifurlparam]</code>. For example, <code>[ifurlparam param="FirstName"]Hey, I know you, [urlparam param="FirstName"]![/ifurlparam]</code> would greet known visitors, but display nothing to users without a FirstName in the query string.</p>
<p>If you want to show content when a value does NOT exist, you can set <code>empty</code> in <code>[ifurlparam]</code>. For example <code>[ifurlparam param="FirstName" empty="1"]Welcome to the site, visitor![/ifurlparam]</code> would greet visitors without a FirstName in the query string, but display nothing for visitors with FirstName in the query string.</p>
<p>If you want to show content only to visitors with a specific value in their query string, you can set <code>is</code> in <code>[ifurlparam]</code>. For example, <code>[ifurlparam param="FirstName" is="Bob"]Hi, Bob![/ifurlparam]</code>, would only greet visitors with the FirstName param set to Bob.</p>
<p>If you want to have urlparam return an HTML attribute, for example to use in pre-setting the value of input or hidden input fields, pass in the optional <code>attr</code> parameter. You might set a value attribute for an input field like so: <code><input type="text" name="firstname" [urlparam attr="value" param='FirstName']></code> or you might set a src attribute for an image tag like so: <code><img [urlparam attr="src" param='imgurl']></code></p>
<p>If you want urlparam to return an entire HTML tag, for example in creating an input field, pass in the optional <code>htmltag</code> parameter. For example, <code>[urlparam htmltag="input" type="text" name="firstname" id="first" attr="value" param="FirstName" default="Bob" /]</code> will produce something like <code><input type="text" name="firstname" id="first" value="Bob" /></code></p>
<h3>Security</h3>
<p>To help protect your site against <a href="http://en.wikipedia.org/wiki/Cross-site_scripting" rel="nofollow ugc">Reflected Cross Site Scripting</a>, we sanitize output with <a href="https://codex.wordpress.org/Function_Reference/esc_html" rel="nofollow ugc">esc_html()</a> which prevents any HTML tags from being passed in and displayed. This would prevent someone from passing in javascript, for example, and having it execute on your site.</p>
<p>Starting in the <a href="https://make.wordpress.org/core/2015/07/23/changes-to-the-shortcode-api/" rel="nofollow ugc">WordPress 4.2.3 security auto-update</a>, you can no longer include shortcodes in HTML attributes. Previous to this WordPress update, you could set a field value like this: <code><input type="text" name="firstname" value="[urlparam param='FirstName']"></code>. Now you have to set it like this: <code><input type="text" name="firstname" [urlparam attr="value" param='FirstName']></code> or  <code>[urlparam htmltag="input" type="text" name="firstname" attr="value" param="FirstName" /]</code>. If you are still using this shortcode the old way, unfortunately, WordPress simply won’t process the shortcode and will return the full shortcode text unprocessed.</p>
<p>To prevent unprivileged users (like Contributors) from using this shortcode to have privileged users (like Admins) accidentally execute arbitrary javascript via HTML attributes (like <code>onclick</code>, <code>onmouseover</code>, etc), html tags and attributes are sanitized.</p>
<p>If you do need have a need to set certain sanitized tags or attributes, at your own risk, you can manually allow these from the URL Params options page under Settings.</p>


URL Params


Thanks for making this a great free option!


Love the advanced features

Short Code to grab any URL parameter from the Query String and display it or display conditional content.

Root Relative URLs vs URL Params