You can use the same license key on two separate domains, e.g. for your development and production websites. Furthermore, subdomains and domain names that contain the words "dev", "staging" and "test" are not taken into account when considering the two-domain limit. This is because the update server's license validation system has been designed to ignore these types of domain names.

If you have more than two domains, you can use the same license key on all of them for a transitional period of up to 48 hours. During this time, you can switch the domains associated with the license key as often as needed (for example, when moving from a staging site to a production domain).

There is no need to re-activate or deactivate the domain because the old domain will automatically disappear from logs. The update server request logs are carefully inspected and analyzed in order to identify any potential abuse. Should any be found, your license key may be restricted, which will prevent you from using the automatic update feature of the plugin from within your WordPress admin dashboard.

If you are presently using the free version of the plugin and need to upgrade to the Pro version for whatever reason, the procedure is fairly simple. Please install the plugin by following the steps that have been provided here, and then deactivate the Permalink Manager Lite plugin. It is not necessary to keep both plugins enabled.

The procedure is absolutely risk-free, and none of your data, including any custom permalinks or settings, will be lost at any point throughout the migration process.

In general, the plugin can only be used to update existing permalinks, which you may change to almost whatever you want with few limitations. In the first place, given that all custom permalinks are stored statically in an array, you cannot define multiple canonical permalinks for the same page/term. This is primarily intended to decrease server resource consumption and processing time.

For the same reason, when a URL is opened and Permalink Manager parses it to determine which page it belongs to, the plugin ignores the $_GET variables (query parameters). As a result, you may not use the Permalink Manager plugin to rewrite the query parameters. To put it another way, it is not possible to format URLs with query parameters in order to convert them into pretty permalinks.

Standard custom permalink format:

In custom permalinks, query parameters are not allowed:

Additionally, given the same reason, it is impossible to do the opposite of what has been explained above. That is, it is not possible to construct a custom permalink format using Permastructures that include query parameters in the URL. Because of this, all non-alphanumeric characters, like question marks and ampersands, will be automatically removed from the custom permalink's (canonical URLs).

Query parameters in slugs

Please keep in mind that if you used Permalink Manager to save custom permalinks that are different from the original ones, they will not be used anymore after the plugin is removed from your site. This is due to the fact that Permalink Manager overwrites the WordPress core's permalink detecting functionality.

The inbuilt permalink system depends on rewrite rules, which are based on "regular expressions" that determine what content type should be loaded when a URL fits one of a set of permalink patterns. Contrary to this, Permalink Manager keeps all custom permalinks in an array so that they may be identified one by one, rather than using the patterns defined with original rewrite rules.

Yes, you may do so at any moment by visiting the "License info" page. If your license key is still valid, the initial amount you paid will be deducted from the cost of the upgrade.

When the Permalink Manager was first designed, it was supposed to be used for a typical WordPress website, which usually has less than a few thousand subpages. As a result, all custom permalinks are saved in a single row in the database in order to avoid slowing down the pageload with multiple SQL queries to the database. This is the most effective approach for small and medium-sized websites, without affecting site speed.

While this data structure works for the vast majority of WordPress sites, it may not be optimal if you want to use the plugin to rewrite tens of thousands of permalinks. What works well for a smaller website may not scale well for a megasite. When the number of addresses on your site exceeds tens of thousands, the custom permalinks array may become quite huge, and any operations on it can have an effect on pageload time.

To summarize, the plugin is suitable for small and medium-sized websites. It will not slow down your pageload time or affect its usability in any way. However, if you want to use it on a much bigger website with thousands of permalinks (more than 60.000), please consider excluding content types that do not require customized permalink format in order to lower the custom permalinks array. For further details on the plugin's performance, please visit this post.

Permalink Manager does not collect or transfer any personal data from your website; they are not gathered since there is no need to.

When the plugin is activated, Permalink Manager Pro send requests to the update server that include just necessary (non-sensitive) info to authenticate the license keys and provide direct access to automatic updates.

A sample request looks like this:

[2018-05-10 11:15:02 +0000]       GET     get_metadata    permalink-manager-pro 4.9.5  action=get_metadata&slug=permalink-manager-pro&license_key=XYZ-123-456-789&installed_version=