anadnet

<p><strong>Current Version 5.2.4</strong></p>
<p>This plugin has two redirect functionalities – <strong>“Quick Redirects”</strong> and <strong>“Individual Redirects”</strong>:</p>
<h4>QUICK REDIRECTS (301 Redirects)</h4>
<p>Quick Redirects are designed to be quick and simple to add. You do not need to have an existing page or post set up to add one. You just put the Request URL and the Destination URL and the plugin will redirect it. This type of redirect is great for fixing typos when a page was created, redirecting old URLs to a new URL so there is no 404, and to redirect links from an old site that has been converted to WordPress.</p>
<h4>INDIVIDUAL REDIRECTS (for existing pages/posts)</h4>
<p>For pages/posts that already exist, the plugin adds an option meta box to the edit screen where you can specify the redirect location and type (301, 302 or meta). This type of redirect is useful for many things, including menu items, duplicate posts, or just redirecting a page to a different URL or location on your existing site.</p>
<p>For best results use some form of WordPress Permalink structure. If you have other Redirect plugins installed, it is recommended that you use only one redirect plugin or they may conflict with each other or one may take over before the other can do its job.</p>
<h4>What You CAN Do (aka, Features):</h4>
<ul>
<li>Works with WordPress Nav Menus</li>
<li>Works with WordPress Custom Post Types (select setting on options page)</li>
<li>You can set a redirected page or menu item to open in a new window (Quick Redirects require <strong>Use jQuery?</strong> option to be set)</li>
<li>You can add a <em>rel=”nofollow”</em> attribute to the page or menu item link for the redirect (Quick Redirects require <strong>Use jQuery?</strong> option to be set)</li>
<li>You can completely re-write the URL for the redirect so it takes the place of the original URL (rewrite the href link)</li>
<li>You can redirect without needing to create a Page or Post using Quick Redirects. This is useful for sites that were converted to WordPress and have old links that create 404 errors (see FAQs for more information).</li>
<li>Destination URL can be to another WordPress page/post or any other website with an external URL.</li>
<li>Request URL can be a full URL path, the post or page ID, permalink or page slug.</li>
<li>Option Screen to set global overrides like turning off all redirects at once, setting a global destination link, make all redirects open in a new window, etc.</li>
<li>View a summary of all redirected pages/posts, custom post types and Quick Redirects that are currently set up.</li>
<li>Plugin Clean up functions for those who decide they may want to remove all plugin data on uninstall.</li>
<li>Import/Export of redirects for backup, or to add bulk Quick Redirects.</li>
<li>Built-in FAQs/Help feed that can be updated daily with relevant questions.</li>
<li>Optional column for list pages to easily show if a page/post has a redirect set up and where it will redirect to.</li>
<li>Helper functions for adding or deleting redirects programmatically (see ‘filters-hooks-helper_functions.txt’ file in plugin folder for help and usage).</li>
</ul>
<h4>What You CANNOT Do:</h4>
<ul>
<li>This plugin does not have wild-card redirect features.</li>
<li>This plugin DOES NOT modify the .htaccess file. It works using the WordPress function wp_redirect(), which is a form of PHP header location redirect.</li>
<li>You cannot redirect the Home (Posts) page – unless you set a page as the home page and redirect that.</li>
<li>If your theme uses some form of custom layout or functionality, some features may not work like open on a new window or no follow functionality UNLESS you have the <strong>Use jQuery?</strong> option to set.</li>
</ul>
<p>This plugin is not compatible with WordPress versions less than 4.0. Requires PHP 5.2+.</p>
<p><strong>PLEASE NOTE:</strong> A new page or post needs to be Published in order for Page/Post redirect to happen for Individual Redirects (existing page is not necessary for Quick Redirects). It WILL work on a DRAFT Status Post/Page ONLY, and I mean ONLY, if the Post/Page has FIRST been Published and the re-saved as a Draft. This does not apply to Quick Redirects.</p>
<h4>TROUBLESHOOTING:</h4>
<ul>
<li>To include custom post types, check the setting on the plugin option page – and you also can hide it from post types you don’t want it on.</li>
<li>If you experience jQuery conflicts with the plugin, try turning off the <strong>Use jQuery?</strong> setting in the options page. BUT, please note that if this option if off, the new window and no follow functionality may be inconsistent (this mainly depends on how your theme is set up)</li>
<li>If you check the box for “Show Redirect URL below” on the edit page, please note that you MUST use the full URL in the Redirect URL box. If you do not, you may experience some odd links and 404 pages, as this option changes the link for the page/post to the EXACT URL you enter in that field. (i.e., if you enter ‘2’ in the field, it will redirect to ‘http://2’ which is not the same as ‘http://yoursite.com/?p=2’).</li>
<li>If your browser tells you that your are in an infinite loop, check to make sure you do not have pages redirecting to another page that redirects back to the initial page. That WILL cause an infinite loop.</li>
<li>If you are using the Quick Redirects method to do your redirects, try to use Request URLs that start with a ‘/’ and are relative to the root (i.e., ‘http://mysite.com/test/’ should be set to ‘/test/’ for the request field).</li>
<li>If your site uses mixes SSL, use relative links whenever possible (i.e., ‘/my-page/’). The plugin is designed to detect the incoming protocol and try to apply the appropriate protocol to the destination URL.</li>
<li>Links in page/post content and links that are created using get_permalink() or the_permalink() will not open in a new window or add the rel=nofollow UNLESS you have the <strong>Use jQuery?</strong> option set.</li>
<li>If your page or post is not redirecting, this is most likely because something else like the theme functions file or another plugin is outputting the header BEFORE the plugin can perform the redirect. This can be tested by turning off all plugins except the Quick Page/Post Redirect Plugin and testing if the redirect works. Many times a plugin or bad code is the culprit.</li>
<li>We try to test the plugin in many popular themes and alongside popular plugins. In our experience, (with exception to a few bugs from time to time) many times another plugin is the cause of the issues – or a customized theme. If you do notice a problem, please let us know at info@anadnet.com – along with the WP version, theme you are using and plugins you have installed – and we will try to troubleshoot the problem.</li>
<li>Check the FAQs/Help located in the Plugin menu for more up to date issues and fixes.</li>
</ul>


Quick Page/Post Redirect Plugin

We've stopped using this because it has apparently been taken over by people who exploit it to add advertising to the sites that use it. Please remove from this catalog.

Adware/malware added recently.

Easily redirect pages/posts or custom post types to another page/post or external URL by specifying the redirect URL and type (301, 302, 307, meta).

Whodunit

Kantari Samy

<p>The plugin allows to highlight the CPT in the same way as would the WordPress core functionality for posts.<br />
You can highlight new content created for your CPT.<br />
It is also possible to highlight the content quickly thanks to bulk actions.</p>
<p>Start example</p>
<pre><code>$args = array(
    'post_type'      => ['project'],
    'post_status'    => 'publish',
    'posts_per_page' => -1,
    'post__in'       => get_option( 'sticky_posts' )
);
$stickyProject = new WP_Query( $args );
</code></pre>
<p>Hook available</p>
<pre><code>add_filter( 'sticky_cpt_add_cpt' , 'add_cpt' );

function add_cpt( $post_types ) {
    $post_types['newcpt'] = 'newcpt';
    return $post_types;
}
</code></pre>


Sticky CPT

Great job dude, i love it ! 

:)

As a little feature request for the next version, i guess you should prepare your plugin for GlotPress native i18n. See : https://translate.wordpress.org/projects/wp-plugins/sticky-cpt , the plugin is not well prepared for internationalization.

The load_plugin_textdomain() function is missing, as well as the language textdomain metadata in the plugin main file comments, and a better use of WP translation strings ;)
E.g : instead of __( "Make this post sticky" ), you should rather use __( "Make this post sticky", "sticky-cpt" )

But very nice work by the way, as usual :)

Good job! (small feature request inside)

Add the possibility of "sticky" CPT. (Gutenberg compatibility)

Quick Page/Post Redirect Plugin vs Sticky CPT