Download the PHP package samiahmedsiddiqui/custom-permalinks without Composer

On this page you can find all versions of the php package samiahmedsiddiqui/custom-permalinks. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of samiahmedsiddiqui/custom-permalinks

Informations about the package custom-permalinks

Custom Permalinks

WordPress Plugin Version Tested up to WordPress Active Installs WordPress Rating License: GPLv3

Take full control of your WordPress site's URLs. Custom Permalinks lets you set a unique, custom URL for any post, page, tag, or category — instead of being limited to WordPress's default permalink structure. When you set a custom permalink, the original URL automatically redirects to your new one, so nothing breaks.

Table of Contents

Key Features

Screenshots

Editor All custom permalinks
Post type structures Category, tag, and term permalinks

Installation

You have two ways to install Custom Permalinks:

From within WordPress

  1. Go to Plugins > Add New in your WordPress dashboard.
  2. Search for "Custom Permalinks".
  3. Click "Install Now" and then "Activate" the plugin from your Plugins page.

Manually via FTP

  1. Download the custom-permalinks folder.
  2. Upload the custom-permalinks folder to your /wp-content/plugins/ directory.
  3. Activate Custom Permalinks through the "Plugins" menu in your WordPress dashboard.

Getting Started: Plugin Settings

Custom Permalinks adds a Custom Permalinks menu to your WordPress dashboard:

To set a permalink for an individual post, page, category, or tag, edit that item and look for the Custom Permalink field near the top (or in the sidebar) of the editor screen — enter the URL path you want and save.

Available Tags for Permalink Structures

When setting up your custom permalink structures, you can use a variety of tags that will dynamically populate the URL. Here's a breakdown of what's available:

Tag Name Description
%year% The year of the post in four digits, eg: 2025
%monthnum% Month the post was published, in two digits, eg: 01
%day% Day the post was published in two digits, eg: 02
%hour% Hour of the day, the post was published, eg: 15
%minute% Minute of the hour, the post was published, eg: 43
%second% Second of the minute, the post was published, eg: 33
%post_id% The unique ID of the post, eg: 123
%category% A clean version of the category name (its slug). Nested sub-categories will appear as nested directories in the URL.
%author% The post author's username (login name). Note that this makes usernames visible in your URLs.
%postname% A clean version of the post or page title (its slug). For example, "This Is A Great Post!" becomes this-is-a-great-post in the URL.
%parent_postname% Similar to %postname%, but uses the immediate parent page's slug if a parent is selected.
%parents_postnames% Similar to %postname%, but includes all parent page slugs if parents are selected.
%title% The title of the post, converted to a slug. For example, "This Is A Great Post!" becomes this-is-a-great-post. Unlike %postname% which is set once, %title% automatically updates in the permalink if the post title changes (unless the post is published or the permalink is manually edited).
%ctax_TAXONOMY_NAME% A clean version of a custom taxonomy term's slug. Replace TAXONOMY_NAME with the actual taxonomy name.
%ctax_TAXONOMY_NAME_name% The custom taxonomy term's name (instead of its slug). Replace TAXONOMY_NAME with the actual taxonomy name.
%ctax_parent_TAXONOMY_NAME% Similar to %ctax_TAXONOMY_NAME%, but includes the immediate parent term's slug in the URL if a parent is selected.
%ctax_parent_TAXONOMY_NAME_name% Similar to %ctax_TAXONOMY_NAME_name%, but includes the immediate parent term's name if a parent is selected.
%ctax_parents_TAXONOMY_NAME% Similar to %ctax_TAXONOMY_NAME%, but includes all parent term slugs in the URL if parents are selected.
%ctax_parents_TAXONOMY_NAME_name% Similar to %ctax_TAXONOMY_NAME_name%, but includes all parent term names if parents are selected.
%custom_permalinks_TAG_NAME% Developers have the flexibility to define their own custom tags (replace _TAG_NAME with your desired name). To ensure these tags resolve to the correct permalinks, simply apply the custom_permalinks_post_permalink_tag filter.

Important Note: For new posts, Custom Permalinks will keep updating the permalink while the post is in draft mode, assuming a structure is defined in the plugin settings. Once the post is published or its permalink is manually updated, the plugin will stop automatic updates for that specific post.

Frequently Asked Questions

What happens to the original URL when I set a custom permalink?

Custom Permalinks automatically redirects the original (default) URL to your new custom permalink, so existing links, bookmarks, and search engine rankings keep working.

Will this affect my site's SEO?

It shouldn't hurt it — since the original URL redirects to the new one, search engines and existing backlinks continue to resolve correctly. Using clean, descriptive custom permalinks can also make your URLs more readable, which is generally good for SEO.

Can I set custom permalinks for categories and tags, not just posts and pages?

Yes. Custom Permalinks supports posts, pages, any public custom post type, and categories/tags (and other custom taxonomy terms).

Does it work with custom post types, like WooCommerce products?

Yes. You can set an individual custom permalink on any public custom post type, or define an automatic permalink structure for the entire post type from Custom Permalinks > Post Types Settings.

Is Custom Permalinks compatible with WPML or Polylang?

Yes, the plugin is compatible with both WPML and Polylang, including translated posts that each have their own custom permalink.

Can I use non-English characters in my permalinks?

Yes. Permalinks in non-Latin scripts, such as Arabic, Thai, Cyrillic, or Chinese, work as you type them. Browsers request these URLs percent-encoded, and Custom Permalinks matches them either way.

Where do the plugin's translations come from?

From translate.wordpress.org. WordPress downloads them automatically for your site's language. If the plugin shows in English on a translated site, update the translations from Dashboard > Updates. You can also help translate it there.

Can I let a non-administrator manage permalinks?

Yes. The plugin adds a dedicated Custom Permalinks Manager role (and matching capabilities) so you can let specific non-admin users view or edit permalinks without giving them full administrator access.

Can I use accented letters, uppercase letters, or extra hyphens in my permalinks?

By default, Custom Permalinks sanitizes permalinks the same way WordPress core does (lowercase, no accents, no repeated hyphens). Developers can lift these restrictions with the custom_permalinks_allow_accents, custom_permalinks_allow_caps, and custom_permalinks_redundant_hyphens filters — see Advanced Customization and Filters below.

A page builder's front-end preview (Cornerstone, etc.) breaks or loses its editing mode on pages with a custom permalink

Some page builders load their live/front-end preview in an iframe using a POST request carrying special values the builder needs (for example Cornerstone's cs_preview_time). If that page also has a custom permalink, Custom Permalinks may redirect the request, and since redirects are followed as GET, the builder's POST data is lost and the preview breaks.

You can tell Custom Permalinks to skip its redirect for that request with the custom_permalinks_avoid_redirect filter, added to your theme or a site-specific plugin:

What happens to my custom permalinks if I deactivate or uninstall the plugin?

Deactivating the plugin keeps all your saved custom permalinks in the database — reactivating it restores them immediately. Uninstalling (deleting) the plugin permanently removes all saved custom permalinks and plugin settings, and your URLs will revert to WordPress' default permalink structure.

My custom permalink isn't saving, or the page isn't redirecting — what should I check?

Advanced Customization and Filters

Custom Permalinks offers developers a robust set of filters and actions to precisely control its behavior. This section outlines how to leverage these features for tasks like generating permalinks programmatically and fine-tuning URL structures.

Setting a Custom Value in Your Post Type Permalink

Let's say you have a custom post type named "Press" and you want to include the year and month from an ACF (Advanced Custom Fields) date field directly in its permalink.

If your post type's permalink structure is about/newsroom/press-releases/%custom_permalinks_year%/%custom_permalinks_month%/%postname%/, here's how you can achieve that with a custom value:

This custom_permalinks_post_permalink_tag filter allows you to dynamically insert values into your permalink structure. The example retrieves the year and month from your ACF date field named press_date and inserts them where %custom_permalinks_year% and %custom_permalinks_month% are defined in your permalink structure. You can integrate this code into your theme's functions.php file or a custom plugin to retrieve those values and return them for the respective permalink tags.

Manipulate Permalink Before Saving

Make changes to a permalink string just before it's saved to the database. This is useful for enforcing specific formatting, like ensuring a trailing slash:

Allow Accented Letters in Permalinks

Enable the use of accented characters in permalinks:

Allow Uppercase Letters in Permalinks

Enable the use of uppercase characters in permalinks:

Allow Redundant Hyphens in Permalinks

Allow permalinks to contain redundant hyphens (e.g., --):

Generating Custom Permalinks

This section outlines how to generate custom permalinks for your WordPress posts, either individually or for an entire post type. This functionality allows site owners and developers to programmatically create or regenerate permalinks without manual updates.

Generate Permalink for a Single Post ID

To generate a custom permalink for a specific post, you can use the following action hook, replacing $post_id with the actual ID of your post:

This simple line of code triggers the permalink generation process for the specified post.

Generate Permalinks for an Entire Post Type

For bulk updates or after structural changes, you might need to regenerate permalinks for all posts within a specific post type. Here's an example demonstrating how to do this for a custom post type called product.

This PHP function iterates through all published posts of the specified $post_type and applies the do_action hook to each, ensuring their permalinks are regenerated. You can integrate this code into your theme's functions.php file or a custom plugin, typically running it as a one-time process or via an administrative trigger.

Exclude Post Type from Custom Permalink Form

Remove the custom permalink settings form from the edit screen of a specific post type:

Exclude Specific Posts from Custom Permalink Form

Remove the custom permalink settings form from individual posts based on criteria like their ID:

Exclude Permalink from Processing

Skip processing for specific permalinks, which can be useful for URLs like XML sitemaps:

Add PATH_INFO to $_SERVER Variable

Enable PATH_INFO to be added to the $_SERVER superglobal variable:

Disable All Redirects

To prevent Custom Permalinks from performing any redirects:

Disable Specific Redirects

Prevent a particular permalink from being redirected by checking its value:

Disable like Query

Disable the like query functionality, which can impact URL matching in some specific scenarios:

Note: Use cp_remove_like_query if URLs don't work after upgrading to v1.2.9.

Hide Columns in the Permalinks Lists

Choose which columns (title, type, permalink) are hidden on the Post Types Permalinks and Taxonomies Permalinks screens, on top of each user's own Screen Options:

Keep the Page Number in Requests

By default, Custom Permalinks removes the trailing /page/{number} from the requested URL before matching it and passes the page number to WordPress as paged. If pagination doesn't work on a custom archive page, you can keep the page number in the requested URL instead:

For Assistance:

Development

Contributions are welcome. To work on the plugin you need Node.js 20.19 or later, Composer, and Docker (for the tests).

Command What it does
npm run build Minifies assets/css/src and assets/js/src into versioned .min files. Commit the result; CI checks it's up to date.
npm run lint Runs Stylelint and ESLint.
composer lint Runs PHP_CodeSniffer with the WordPress Coding Standards and PHP 7.4+ compatibility checks.
composer analyse Runs PHPStan.
npm run env:start Starts WordPress in Docker with @wordpress/env.
npm run test:php Runs the PHPUnit integration tests in that environment.
npm run env:stop Stops the environment.

Every pull request runs these checks, plus Plugin Check, and gets a comment with a link to try the change in WordPress Playground, no local setup needed.

Need Help or Found a Bug?

If you experience any site-breaking issues after upgrading, please report them on the WordPress Forum or GitHub with detailed information. You can always revert to an older version by downloading it from https://wordpress.org/plugins/custom-permalinks/advanced/.

All versions of custom-permalinks with dependencies

PHP Build Version
Package Version
Requires php Version >=7.4
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package samiahmedsiddiqui/custom-permalinks contains the following files

Loading the files please wait ...