WordPress中找回指定permalink页面及强制设置permalink的方法

Let’s break down your two questions clearly—this is a super common permalink snag in WordPress, so I’ve got practical steps to help you out.

Yes, you can—but first you need to resolve the underlying conflict that’s making WordPress auto-rename it to 2017-2. Here’s how:

• First, rule out obvious conflicts: WordPress adds the -2 suffix because it thinks the 2017 slug is already in use. Since you can’t find it in the backend or via the List all URLs plugin, the issue is likely an orphaned database entry or a built-in archive conflict.
• Check for date archive overlap: A big gotcha here—WordPress uses mysite.com/2017 by default as the date archive for all posts from 2017. Visit that URL directly: if it loads a list of posts from 2017, that’s the conflict. To fix this, you can add code to prioritize your page over the date archive (more on that below).
• Clean up orphaned database entries:
  1. Use your hosting’s database tool (like phpMyAdmin) to access your WordPress database.
  2. Search the wp_posts table for post_name = '2017'—look for any posts, pages, or custom post types (even trashed, draft, or private ones) using this slug. If you find one, delete it permanently (empty the trash if it’s there) or change its slug.
  3. If no entry exists, flush your rewrite rules: Go to Settings > Permalinks and click "Save Changes" (no need to edit anything—this refreshes WordPress’s URL mapping).
• Force the slug with code (temporary fix):
  If the above steps don’t work, add this snippet to your theme’s functions.php file or a custom plugin to bypass the unique slug check for your page:

  add_filter('wp_unique_post_slug', 'force_2017_slug', 10, 6);
  function force_2017_slug($slug, $post_ID, $post_status, $post_type, $post_parent, $original_slug) {
      // Only target pages trying to use the '2017' slug
      if ($original_slug === '2017' && $post_type === 'page') {
          return '2017';
      }
      return $slug;
  }
  

  Important: Remove this code after you’ve successfully set the permalink to avoid future conflicts. Always back up your database before editing code or database tables.

Since the backend and plugin aren’t showing anything, dig deeper with these steps:

• Check the trash folder: Sometimes pages get trashed but not permanently deleted. Go to Pages > Trash and look for any page with the 2017 slug. If found, restore it to change the slug or delete it permanently.
• Search the database directly:
  • In wp_posts, search for post_name = '2017'—this covers all post types (pages, posts, custom post types) even if they’re hidden from the admin.
  • Check wp_terms and wp_term_taxonomy—could a category, tag, or custom taxonomy be using the 2017 slug? WordPress reserves slugs for taxonomies too.
  • Verify the date archive: As mentioned earlier, visit mysite.com/2017—if it loads a year archive of posts, that’s the "missing" entry you’re looking for (it’s a built-in WordPress feature, not a page).
• Use a database search plugin: If you’re not comfortable with phpMyAdmin, try a plugin like WP-DBManager (backup first!) to search your entire database for the 2017 slug.

Bonus: Fixing the date archive conflict #

If the issue is the built-in year archive, add this code to your functions.php to make WordPress load your page instead of the archive when someone visits mysite.com/2017:

function prioritize_page_over_year_archive($query) {
    if ($query->is_year() && !$query->is_admin() && $query->is_main_query()) {
        $year = $query->get('year');
        // Check if a page exists with the year as its slug
        $page = get_page_by_path($year);
        if ($page) {
            wp_redirect(get_permalink($page));
            exit;
        }
    }
}
add_action('pre_get_posts', 'prioritize_page_over_year_archive');

内容的提问来源于stack exchange，提问作者GG gg