pcprajapat

PhoolChand Prajapat

PCP Linkflow Engine gives you complete control over every URL on your WordPress site. Whether you need to remove the <code>/product/</code> prefix from WooCommerce products, add a custom base to a taxonomy, or restructure your page URLs — this plugin handles it all from a clean, modern admin interface.
No code required. Changes take effect immediately with automatic rewrite rule flushing.
<h3>🔑 Key Features:</h3>
Post Type URL Control 
– ✏️ Set a custom slug for any public post type (e.g. <code>/shop/</code> instead of <code>/product/</code>) 
– 🗑️ Remove the slug entirely — serve products, posts, or CPTs at root level (e.g. <code>/jacket/</code> instead of <code>/product/jacket/</code>) 
– 📄 Full support for hierarchical post types like Pages (e.g. <code>/pages/about/team/</code>) 
– 🛒 WooCommerce compatible — works correctly with the shop page, product archives, <code>is_product()</code>, and all WooCommerce template hooks
Taxonomy URL Control 
– ✏️ Set a custom base for any public taxonomy (e.g. <code>/topics/</code> instead of <code>/category/</code>) 
– 🗑️ Remove the base entirely — serve term archives at root level (e.g. <code>/clothing/</code> instead of <code>/product-category/clothing/</code>) 
– 🌳 Full support for hierarchical taxonomies — sub-terms work correctly (e.g. <code>/clothing/accessories/</code>) 
– ✅ Correct <code>is_tax()</code>, admin bar links, and taxonomy templates when base is removed
Developer Friendly 
– 🔌 Filter hooks: <code>pcplfe_post_type_slug</code>, <code>pcplfe_taxonomy_slug</code>, <code>pcplfe_permalink_structure</code>, <code>pcplfe_remove_post_type_slug</code>, <code>pcplfe_remove_taxonomy_slug</code> 
– 🌐 REST API — read and write settings via <code>/wp-json/pcplfe/v1/</code> 
– 📦 Import / Export — back up and restore all settings as JSON 
– 🧩 PSR-4 autoloaded OOP architecture under the <code>PCPLFE\</code> namespace
Modern Admin UI 
– 🎨 Clean, Tailwind-inspired design with toggle switches 
– 📑 Tabbed settings for Post Types and Taxonomies 
– 🔄 POST → Redirect → GET pattern — no duplicate saves on refresh 
– 💾 Active tab preserved across saves and page refreshes
<h3>REST API</h3>
PCP Linkflow Engine exposes a REST API under the <code>pcplfe/v1</code> namespace. All endpoints require the <code>manage_options</code> capability.
Authentication
Use WordPress Application Passwords (WordPress 5.6+). Generate one at Users → Your Profile → Application Passwords, then pass it with every request:
<pre><code>-u "your-username:xxxx xxxx xxxx xxxx xxxx xxxx"
</code></pre>
<h4>Endpoints</h4>
GET /wp-json/pcplfe/v1/settings
Returns all saved post type and taxonomy settings.
<pre><code>curl -u "admin:xxxx xxxx xxxx xxxx xxxx xxxx" \
 https://yoursite.com/wp-json/pcplfe/v1/settings
</code></pre>
Example response:
<pre><code>{
 "post_type_settings": {
 "post": { "enabled": true, "custom_slug": "articles", "remove_slug": false }
 },
 "taxonomy_settings": {
 "category": { "enabled": true, "custom_base": "topics", "remove_base": false }
 }
}
</code></pre>
POST /wp-json/pcplfe/v1/settings
Save post type and taxonomy settings from a JSON body.
<pre><code>curl -u "admin:xxxx xxxx xxxx xxxx xxxx xxxx" \
 -X POST \
 -H "Content-Type: application/json" \
 -d '{
 "post_type_settings": {
 "post": { "enabled": true, "custom_slug": "articles", "remove_slug": false }
 },
 "taxonomy_settings": {
 "category": { "enabled": true, "custom_base": "topics", "remove_base": false }
 }
 }' \
 https://yoursite.com/wp-json/pcplfe/v1/settings
</code></pre>
GET /wp-json/pcplfe/v1/permalink?post_id=X
Returns the custom permalink record for a given post ID.
<pre><code>curl -u "admin:xxxx xxxx xxxx xxxx xxxx xxxx" \
 "https://yoursite.com/wp-json/pcplfe/v1/permalink?post_id=123"
</code></pre>
Example response:
<pre><code>{
 "post_id": 123,
 "post_type": "post",
 "default_permalink": "https://yoursite.com/articles/hello-world/",
 "custom_permalink": "https://yoursite.com/my-custom-slug/",
 "record": { "permalink": "my-custom-slug" }
}
</code></pre>
POST /wp-json/pcplfe/v1/permalink
Save a custom permalink for a specific post. Send an empty <code>permalink</code> value to remove the override.
<pre><code>curl -u "admin:xxxx xxxx xxxx xxxx xxxx xxxx" \
 -X POST \
 -H "Content-Type: application/json" \
 -d '{
 "post_id": 123,
 "post_type": "post",
 "permalink": "my-custom-slug"
 }' \
 https://yoursite.com/wp-json/pcplfe/v1/permalink
</code></pre>
To remove a custom permalink override:
<pre><code>curl -u "admin:xxxx xxxx xxxx xxxx xxxx xxxx" \
 -X POST \
 -H "Content-Type: application/json" \
 -d '{
 "post_id": 123,
 "post_type": "post",
 "permalink": ""
 }' \
 https://yoursite.com/wp-json/pcplfe/v1/permalink
</code></pre>

PCP Linkflow Engine

Full URL control for every post type and taxonomy. Customize slugs, remove bases, and define permalink structures - all from a clean admin interface.

Milan Dinić

Change Core Slugs is a plugin that allows you to set custom permalink slugs instead of default ones that are provided with WordPress core. This functionality is already available in WordPress, however it can be used by manually setting new configuration in the code. What this plugin does is that it provides friendly user interface where all site admins can change default slugs.
You can change:
<ul>
<li><code>author</code> base in authors archives</li>
<li><code>search</code> base in searches archives</li>
<li><code>page</code> base in pagination pages of archives or in single posts</li>
<li><code>comments-page</code> base in pagination pages of single posts comments</li>
<li><code>comments</code> base in comments feeds</li>
<li><code>feed</code> base in feeds</li>
</ul>
When you change any slug, you will not get redirection from the pages that used old slug. Same goes if you again change any slug. If you want redirection, you must set it through server rules or with other plugins.
If you disable this plugin, old, default slugs will be restored and URLs with new slugs will stop working. The only way to keep new slugs is by manually setting them in the code.
NOTE: because of two bugs in WordPress core, in some cases setting custom slugs will not work properly. These cases are when <code>page</code> or <code>comments-page</code> include any non-ASCII character (ticket <a href="https://core.trac.wordpress.org/ticket/41891" rel="nofollow ugc">#41891</a>), or when <code>feed</code> or <code>comments</code> bases are set (ticket <a href="https://core.trac.wordpress.org/ticket/43274" rel="nofollow ugc">#43274</a>). Until these two bugs are fixed, you can use <a href="https://github.com/dimadin/redirect-canonical-fix" rel="nofollow ugc">temporary plugin</a> that includes fixes. You do not need that plugin if you do not use features that trigger bugs from above.
And it’s on <a href="https://github.com/dimadin/change-core-slugs" rel="nofollow ugc">GitHub</a>.
<h3>Usage</h3>
Got to Settings > Change Core Slugs page.

Change Core Slugs

Set custom permalink slugs instead of default ones.

PCP Linkflow Engine vs Change Core Slugs