Sami Ahmed Siddiqui

Aliya Yasir

Permalinks Customizer helps you to set the different permalink structure for different PostTypes and Taxonomies which are publicly available.
You can use the tags which are defined by the WordPress as mentioned <a href="https://github.com/yasglobal/permalinks-customizer#default-tags-for-posttypes" rel="nofollow ugc">here</a>. Also, you can use the tags which are customily defined by this plugin for <a href="https://github.com/yasglobal/permalinks-customizer#custom-tags-for-posttypes" rel="nofollow ugc">PostTypes</a> and <a href="https://github.com/yasglobal/permalinks-customizer#custom-tags-for-taxonomies" rel="nofollow ugc">Taxonomies</a>. You can also find these tags in Permalinks Customizer menu on WordPress Dashboard (if the plugin is installed).
<h3>How to set the Permalinks for different PostTypes</h3>
Let’s assume that you have 6 PostTypes and you like to apply differnet permalink structure for them. Like:
<ol>
<li>Blog : For this post type you want to create a permalink which looks like this: http://www.example.com/blog/year-month-date-postname/</li>
<li>Customers : For this post type you want to create a permalink which looks like this: http://www.example.com/customers/postname/</li>
<li>Events : For this post type you want to create a permalink which looks like this: http://www.example.com/events/year-month-date-postname/</li>
<li>Press : For this post type you want to create a permalink which looks like this: http://www.example.com/press/category/year/postname/</li>
<li>News : For this post type you want to create a permalink which looks like this: http://www.example.com/news/year/postname/</li>
<li>Sponsors : For this post type you want to create a permalink which looks like this: http://www.example.com/company/sponsor/post_title/</li>
</ol>
This plugin allows you to do this very easily. You just need to go on Permalinks Customizer Settings Page. Where text fields are shown with PostType name. You can define your permalinks you want to create for each post type.
If you leave any PostType field empty, Permalinks Customizer will create a permalink for that PostType by using the default permalink settings.
<h3>How to Configure Permalinks Customizer</h3>
You can configure the plugin by navigating to the <code>Permalinks Customizer</code> menu from the WordPress Dashboard
<h3>Structure Tags</h3>
You can find all the tags which are currently supported by the <code>Permalinks Customizer</code>.
<h3>Default Tags for PostTypes</h3>
Below mentioned tags are provided by the <code>WordPress</code>. These tags can be used on Default <code>WordPress Permalink</code> Settings Page as well as <code>Permalinks Customizer</code> Settings page.
<ol>
<li><code>%year%</code>: The year of the post, four digits, for example 2019</li>
<li><code>%monthnum%</code>: Month of the year, for example 01</li>
<li><code>%day%</code>: Day of the month, for example 02</li>
<li><code>%hour%</code>: Hour of the day, for example 15</li>
<li><code>%minute%</code>: Minute of the hour, for example 43</li>
<li><code>%second%</code>: Second of the minute, for example 33</li>
<li><code>%post_id%</code>: The unique ID of the post, for example 123</li>
<li><code>%postname%</code>: A sanitized version of the title of the post (post slug field on Edit Post/Page panel). So “This Is A Great Post!” becomes this-is-a-great-post in the URI.</li>
<li><code>%category%</code>: A sanitized version of the category name (category slug field on New/Edit Category panel). Nested sub-categories appear as nested directories in the URI.</li>
<li><code>%author%</code>: A sanitized version of the author name.</li>
</ol>
<h3>Custom Tags for PostTypes</h3>
Below mentioned tags are provided by the <code>Permalinks Customizer</code> for PostTypes. These tags can not be used on the Default <code>WordPress Permalink</code> Settings Page.
<ol>
<li><code>%title%</code>: Title of the post. let’s say the title is “This Is A Great Post!” so, it becomes this-is-a-great-post in the URI.</li>
<li><code>%parent_title%</code>: This tag is similar as <code>%title%</code>. Only the difference is that it appends the immediate Parent Page Title in the URI if any parent page is selected.</li>
<li><code>%all_parents_title%</code>: This tag is similar as <code>%title%</code>. Only the difference is that it appends all the Parents Page Title in the URI if any parent page is selected.</li>
<li><code>%parent_postname%</code>: This tag is similar as <code>%postname%</code>. Only difference is that it appends the immediate Parent Page Slug if any parent page is selected.</li>
<li><code>%all_parents_postname%</code>: This tag is similar as <code>%postname%</code>. Only the difference is that it appends all the Parents Page Slug in the URI if any parent page is selected.</li>
<li><code>%child-category%</code>: A sanitized version of the category name (category slug field on New/Edit Category panel).</li>
<li><code>%product_cat%</code>: A sanitized version of the product category name (category slug field on New/Edit Category panel). Nested sub-categories appear as nested directories in the URI.
 This <code>tag</code> is specially used in WooCommerce Products.</li>
<li><code><%ctax_custom_taxonomy%></code>: A sanitized version of the custom taxonomy where the taxonomy name is <code>custom_taxonomy</code>. Replace the <code>custom_taxonomy</code> with your appropriate created taxonomy name.
 If you want to provide the default slug which is used when the category/taxonomy doesn’t be selected so, make sure to provide default name/slug which looks like this: <code><%ctax_custom_taxonomy??sales%></code>. Value which is written between the <code>??</code> and <code>%></code> is used as default slug.</li>
<li><code><%ctaxparents_custom_taxonomy%></code>: This tag is similar as <code><%ctax_custom_taxonomy%></code>. Only the difference is that it appends all the Parents Slug in the URI if any parent Term/Category is selected.</li>
<li><code>%author_firstname%</code>: A sanitized version of the author first name. If author first name is not available then it uses the author’s username.</li>
<li><code>%author_lastname%</code>: A sanitized version of the author last name. If author last name is not available then it uses the author’s username.</li>
</ol>
Note: <code>%title%</code> is similar as <code>%postname%</code> tag but the difference is that <code>%postname%</code> can only be set once by WordPress whereas <code>%title%</code> can be changed by user at multiple times. let’s say the title is “This Is A Great Post!” so, it becomes “this-is-a-great-post” in the URI(At the first time, <code>%postname%</code> and <code>%title%</code> works same) but if you edit and change title let’s say “This Is A WordPress Post!” so, <code>%postname%</code> in the URI remains same “this-is-a-great-post” whereas <code>%title%</code> in the URI becomes “this-is-a-wordpress-post”
<h3>Custom Tags for Taxonomies</h3>
Below mentioned tags are provided by the <code>Permalinks Customizer</code> for Taxonomies. These can not be used on the Default <code>WordPress Permalink</code> Settings Page.
<ol>
<li><code>%name%</code>: Name of the Term/Category. let’s say the name is “External API” so, it becomes external-api in the URI.</li>
<li><code>%term_id%</code>: The unique ID # of the Term/Category, for example 423</li>
<li><code>%slug%</code>: A sanitized version of the name of the Term/Category. So “External API” becomes external-api in the URI.</li>
<li><code>%parent_slug%</code>: This tag is similar as <code>%slug%</code>.
 Only the difference is that it appends the immediate Parent Term/Category Slug in the URI if any parent Term/Category is selected.</li>
<li><code>%all_parents_slug%</code>: This tag is similar as <code>%slug%</code>.
 Only the difference is that it appends all the Parent Terms/Category Slugs in the URI if any parent Term/Category is selected.</li>
</ol>
<h3>Filters</h3>
You can find all the filters below which are provided by <code>Permalinks Customizer</code> plugin. These filters can be used as per your Website requirement.
<h3>Exclude Permalinks</h3>
If you want to exclude some Permalink to processed with the plugin so, just add the filter looks like this:
<pre><code>function yasglobal_exclude_url( $permalink ) {
 if ( false !== strpos( $permalink, '/contact-us/' ) ) {
 return '__true';
 }
 return;
}
add_filter( 'permalinks_customizer_exclude_request', 'yasglobal_exclude_url' );
</code></pre>
<h3>Show Relative Permalink/URL</h3>
To show relative permalink/url in Edit Post, add this filter in your themes <code>functions.php</code>.s
<pre><code>add_filter( 'permalinks_customizer_remove_home_url', '__return_true' );
</code></pre>
<h3>Exclude PostType from the Plugin</h3>
To exclude the plugin to be worked on any PostType. Add this filter in your themes <code>functions.php</code>.
<pre><code>function yasglobal_exclude_post_types( $post_type ) {
 if ( $post_type == 'page' ) {
 return '__true';
 }
 return '__false';
}
add_filter( 'permalinks_customizer_exclude_post_type', 'yasglobal_exclude_post_types');
</code></pre>
Note: Plugin stops working on the backend. No more permalinks would be generated by the plugin but the permalink which are already created will remains in work.
<h3>Disable automatically create redirects</h3>
To disable automatically create redirects feature on creating and updating the post/pages/categories, add this filter in your themes functions.php.
<pre><code>add_filter( 'permalinks_customizer_auto_created_redirects', '__return_false');
</code></pre>
This filter stops to be creating new redirects but existed redirects keeps working. To stop existed redirects, add <code>permalinks_customizer_disable_redirects</code> filter.
<h3>Disable Redirects</h3>
To disable redirects to be applied , add this filter in your themes functions.php.
<pre><code>add_filter( 'permalinks_customizer_disable_redirects', '__return_false');
</code></pre>
This filter only stop redirects to be work but the automatically create redirects still works. To stop automatically create redirects feature add <code>permalinks_customizer_auto_created_redirects</code> filter.
<h3>Bug reports</h3>
Bug reports for Permalinks Customizer are <a href="https://github.com/yasglobal/permalinks-customizer" rel="nofollow ugc">welcomed on GitHub</a>. Please note GitHub is not a support forum, and issues that aren’t properly qualified as bugs will be closed.

Permalinks Customizer

Does not work

This plugin should be on top and deserves more downloads than the plugins which do not work for WooCommerce Taxonomies/Categories.

Thanks!

The only free plugin which works

Permalinks Customizer helps you to set the different permalink structure for different PostTypes and Taxonomies which are publicly available.

WebFactory

A perfect plugin for creating a new site from an old site or changing the domain name, and managing all of the redirects and broken URLs by using redirection.
Find the link to 301 Redirects in the main Settings menu. 
404 error log can be found on the same page, and on the admin dashboard.
301 Redirects plugin creates a new table in the WP database called ‘WP_PREFIX_ts_redirects’ that stores all of your redirect rules and redirections. On plugin deactivation the table is not deleted. When you delete the plugin then the redirection table is deleted forever.
Why is the 404 error log limited to the last 50 errors? 
By default, the 404 error log is limited to the last (chronologically) fifty 404 errors. Since the 404 log doesn’t use a custom database table for storage but rather an array saved in WP options, 50 is a safe number that ensures the 404 log works on all sites, that it doesn’t take up too much space in the database and that it doesn’t slow down the site. 
The code imposes no limits on the log size and you can easily overwrite the default limit by using the 301_redirects_max_404_logs filter or by using the following code snippet to raise the limit to 200:
<pre><code>add_filter('301_redirects_max_404_logs', function($log_max) { return 200; }, 10, 1);
</code></pre>
GDPR compatibility 
We are not lawyers. Please do not take any of the following as legal advice. 
301 Redirects does not use any 3rd party services or CDNs. It does create a 404 error log which saves the following info when a non-existing (404) page is opened: timestamp of the event, URL of the 404 page, user agent based on the user agent string from the user’s browser. No IP related data or any other identifiable user data is saved or processed. Based on that, we feel it’s GDPR compatible, but again, please, don’t take this as legal advice.

301 Redirects & 404 Error Log

Create & manage 301 redirects. Easily test redirects. Includes 404 error log.

Permalinks Customizer vs 301 Redirects & 404 Error Log