The LMRedirectToItem plugin is for setting up redirects to items. Primarily meant as a help when migrating to a different URL scheme.
| General Plugin info | |
|---|---|
| Author: | Leo |
| Current Version: | v1.1.0 |
| Download: | NP_LMRedirectToItem_v110.zip |
| Code: | |
| Demo: | |
| Forum Thread: | here |
The NP_LMRedirectToItem plugin was primarily made as a help when migrating to a different URL scheme for a Nucleus blog.
It can set up redirects for all item URLs in the old URL scheme. Then you can migrate the blog to a different URL scheme and all old item URLs can still be used to access the items. The plugin uses permanent redirects by default so search engines should be updated with the new item URLs.
Other uses for this plugin is to set up fixed URLs where you can change the item the URL will show. Ideal where you want to have an URL that shows the newest item of a certain kind. You can also use it to make a short URL for an item. To use permanent or temporary redirects can be configured for each redirect.
The plugin is installed as a normal plugin. It will need the same .htaccess change that fancierURL plugins uses to be able to do redirects:
<IfModule mod_rewrite.c>
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?virtualpath=$1 [L,QSA]
</IfModule>
The plugin has one configurable option: “Delete NP_LMRedirectToItem data on uninstall?”. This option lets you decide if you want to delete the NP_LMRedirectToItem data when you uninstall the plugin.
The redirects are administered from the plugin admin page which can be accessed from either the quick menu in the admin area, or from the admin link for the plugin in the plugin list. Only the blog super administrator can access the plugin admin page.
In the admin area for the LMRedirectToItem plugin you can do the following operations:
When you register a redirect should the redirect from field not include domain, only the absolute path (from the document root) including any query string. No wildcards are allowed. Examples: ”/index.php?itemid=1” or ”/some/path”. If you have Nucleus installed in a sub directory on the web server, must the redirect from always include the sub directory. Examples: ”/nuclusdir/index.php?itemid=1” or ”/nuclusdir/some/path”.
If the redirect from url is the same as the url of the item redirecting to, will the redirect be ignored. The plugin does not check for circle redirect loops.
To set up a redirect you have to have the item id for the item you want to redirect to. This item id can be obtained by checking the edit item URL in the admin area. Example: http://example.com/nucleus/index.php?action=itemedit&itemid=1. For this item is the item id is 1. After you have created the redirect you can check if the redirect is to the correct item as the redirect to item id column in the plugin admin area has an item link.
The plugin can use permanent or temporary redirects. This can be set up for each redirect. If there is a chance a redirect may be changed to a different item is it best to set it up as a temporary redirect.
Using the plugin to redirect from the old URL scheme item links when changing the URL scheme is quite easy:
For additional support and/or bug reports please use the Nucleus forum plugin announce thread or the plugin page comment section.
This version of the NP_LMRedirectToItem is tested against version 3.64 of Nucleus CMS. Minimum version of Nucleus CMS needed for using the plugin is 3.50.