hakre

<p>Better HTTP Redirects makes your Blog’s redirects to play more nicely the HTTP standards. Dual Mode Plugin, can be used as a standard Plugin or as a Must-Use Plugin.</p>
<h4>Features</h4>
<ul>
<li>Provide Hypertext Fragments on redirects where applicable.</li>
<li>Compatible with <em>any</em> current usage of the wp_redirect() API function.</li>
<li>Prevent unnecessary redirect loops on UTF-8 based sites.</li>
<li>Improved user and robot (search engines etc.) experience for your website.</li>
<li>No need for you to wait until core code get’s fixed – if ever!</li>
<li>Helps you debugging redirect related issues with it’s unique <a href="http://hakre.wordpress.com/2011/03/20/how-to-debug-redirect-problems-in-wordpress" rel="nofollow ugc">Redirect Debug Mode</a>.</li>
<li>Free</li>
</ul>
<h3>TODO</h3>
<ul>
<li>Verify that the plugin is stricly preventing redirects that redirect to the same URI (see RFC 2616 section 3.2.3).</li>
</ul>
<h3>Integration</h3>
<p>“Better HTTP Redirects” works out of the box but for a better integration you can make use of the following:</p>
<ul>
<li>Hook <strong>redirect_hypertext</strong> <code>$hypertext = apply_filters('redirect_hypertext', $hypertext, $location, $status);</code></li>
</ul>
<h3>Document Scope</h3>
<p>This file readme.txt has been created in the intention to provide data to be displayed <a href="https://wordpress.org/extend/plugins/better-http-redirects/" rel="ugc">on the wordpress.org plugin repository website</a>. As always, for anything concrete and precise, refer to <a href="https://plugins.trac.wordpress.org/browser/better-http-redirects/trunk/better-http-redirects.php" rel="nofollow ugc">the plugin sourcecode itself</a>, it ships with <a href="http://en.wikipedia.org/wiki/PHPDoc" rel="nofollow ugc">phpdoc style comments</a>.</p>


Better HTTP Redirects

Better HTTP Redirects makes your Blog's redirects to play more nicely the HTTP standards.

SCAND

<p>This WordPress plugin supports the creation of new tickets in the osTicket system by using osTicket API. Only contact forms, which send emails, are supported as our plugin hooks the wp_mail function to get the forms’ data.</p>
<h4>Important</h4>
<p>The contact form must contain “Email”, “Full Name”, “Subject” and “Message” fields at least.</p>
<h4>osTicket API</h4>
<p>The osTicket API is used as simple XML or JSON over HTTP. Ticket creation is supported only.</p>
<h4>Authentication</h4>
<p>Authentication via the API is done via API keys configured inside the osTicket admin panel. API keys are created and tied to a source IP address, which will be checked against the source IP of requests to the HTTP API.</p>
<p>API keys can be created and managed via the admin panel. Navigate to Manage -> API keys. Use Add New API Key to create a new API key. Currently, no special configuration is required to allow the API key to be used for the HTTP API. All API keys are valid for the HTTP API.<br />
See more details <a href="https://github.com/osTicket/osTicket/blob/master/setup/doc/api.md" rel="nofollow ugc">here</a>.</p>
<h4>Deployment</h4>
<ol>
<li>Configure osTicket support system to enable the access via API for your WordPress (see “Authentication” section).</li>
<li>Set up the contact form and input the attribute value of the tag name exactly as given in the settings form of the plugin. This will let the data map to osTicket API data template correctly.</li>
<li>Add a hidden input with a name specified in ‘Form Identifier’ while using the contact form.</li>
</ol>


osTicket Connector

I discover this plugin work fine and is very easy to setup!

Easy and perfect

Create tickets in osTicket support system via the existing contact form.

Better HTTP Redirects vs osTicket Connector