antonioandra.de

WP htaccess Control should now really be called WP htaccess and Rewrite Control. It provides an interface to customize the htaccess file generated by WordPress but also its permalinks (author, category, archives, pagination and custom taxonomies). Have a look at the screenshot for a clearer idea of the available options.
Features:
<ul>
<li>Customizing the htaccess file generated by WordPress;</li>
<li>Removing any custom taxonomy’s slug base from permalinks;</li>
<li>Removing the category base from permalinks;</li>
<li>Removing the author base from permalinks;</li>
<li>Customizing the Author Permalink Base;</li>
<li>Customizing Paginated Permalinks (translate the “page” word on permalinks to your own language);</li>
<li>Customization (and canonization) of the Search Permalink Base;</li>
<li>Creation of Category, Author, Tag and Custom Taxonomy based archives (ex: “http://your-site.com/category/stories/2010/12”, “http://your-site.com/author/admin/2010/12/page/2” and “http://your-site.com/tag/wordpress/2010/12”), this will also work if you’ve removed the base slug;</li>
<li>Maintenance mode.</li>
</ul>
Easy to use “Suggested htaccess” rules:
<ul>
<li>Jim Morgan’s htaccess;</li>
<li>Disable directory browsing;</li>
<li>Disable and redirect image hotlinking;</li>
<li>Disable and redirect file hotlinking;</li>
<li>Force canonical url (WWW or non-WWW);</li>
<li>Limit maximum file upload size;</li>
<li>Protect wp-config.php file from access;</li>
<li>Protect .htaccess file from access;</li>
<li>Protect comments.php from spam bots coming from nowhere;</li>
<li>Set 500 error page;</li>
<li>Set 403 error page;</li>
<li>Use mod_gzip if available;</li>
<li>Use mod_deflate if available;</li>
<li>Set admin email on server generated error pages;</li>
<li>Disable ServerSignature on server generated error pages.</li>
</ul>
POT file is included, translations are welcome.
<h3>Known Issues</h3>
I still haven’t tested this under WordPress multisite, issues have however been reported.
<h3>Additional Credit</h3>
Removal of the category base is based on iDope’s WP No Category Base but extended so that it works with category archives (ie.: “http://example.com/my-category/2010/12”).
Search redirection is based on Mark Jaquith’s Nice Search but extended so that it works with custom search base (ie.: “http://example.com/search-base/search-term”).
<h3>Stable Versions</h3>
For WordPress versions above 3.9 use the plugin version 3.4.
For WordPress versions above 3.4 use the plugin version 3.3.
For WordPress versions prior to 3.4 use the plugin version 2.7.2.1.

WP htaccess Control

Interface to customize the permalinks (author, category, archives and pagination) and htaccess file generated by WordPress.

cartpauj

Shortcode Redirect sends visitors from any post or page to another URL. No settings screens, no database tables — just drop it in where you need it.
There are two ways to use it, and both produce the exact same front-end output.
1. The Redirect block (new in 1.1.0)
In the block editor, add the Redirect block from the Widgets category. The block sidebar exposes three simple fields:
<ul>
<li>Destination URL — where the visitor should end up</li>
<li>Seconds to wait — how long to pause before redirecting (<code>0</code> = immediate)</li>
<li>Show “redirecting” message — toggle the visible “Please wait…” line on or off</li>
</ul>
The editor shows a live summary of what the block will do, e.g. “Redirects to https://example.com — after 3 seconds · message shown”. No shortcode syntax to memorize.
2. The classic shortcode
Paste into any post or page:
<pre><code>[redirect url='https://example.com' sec='3']
</code></pre>
Shortcode attributes:
<ul>
<li><code>url</code> — destination URL (required)</li>
<li><code>sec</code> — seconds to wait before redirecting (optional, default <code>0</code>)</li>
<li><code>show_message</code> — set to <code>false</code>, <code>0</code>, <code>no</code>, or <code>off</code> to hide the “redirecting” message (optional, default <code>true</code>, new in 1.1.0)</li>
</ul>
Example with all three:
<pre><code>[redirect url='https://example.com' sec='5' show_message='false']
</code></pre>
Same output either way
Block or shortcode, the front-end renders the same single <code><meta http-equiv="refresh"></code> tag (plus the optional one-line message). No JavaScript. No server-side redirect. No third-party tracking. Existing <code>[redirect]</code> shortcodes from earlier versions continue to work unchanged.
<h4>Features</h4>
<ul>
<li>Block editor support — native “Redirect” block (new in 1.1.0)</li>
<li>Classic shortcode — <code>[redirect]</code> works exactly like it always has</li>
<li>Optional delay — choose how many seconds to wait before redirecting</li>
<li>Silent mode — hide the “redirecting…” message for a clean, blank-page redirect (new in 1.1.0)</li>
<li>Lightweight — a single PHP file plus a small block; no settings, no tables, no dependencies</li>
<li>Backwards compatible — upgrading from 1.0.x is drop-in</li>
</ul>

Shortcode Redirect

Redirect any post or page — with a native block or a classic shortcode. Optional delay. Optional "redirecting" message. Zero configuration.

WP htaccess Control vs Shortcode Redirect