WordPress自定义主题网站图片无法加载，访问图片URL报500错误

Alright, let's tackle this two-fold issue you're facing with your WordPress site on IIS 7 + XAMPP—missing images (returning 500 internal server errors) and permalinks forcing index.php into every URL. These problems are tightly linked, so let's break down the fixes step by step:

1. Reset Permalink Settings First #

The index.php showing up in all links is a clear sign your permalink rewrite rules aren't working properly, which is also likely causing the image 500 errors (since media URLs might be getting incorrectly routed through index.php instead of serving directly).

• Log into your WordPress admin dashboard, go to Settings → Permalinks.
• First, switch to the Plain permalink structure (the default ?p=123 format), click Save Changes. This resets any broken rewrite rules.
• Then switch back to your preferred permalink structure (e.g., /%postname%/) and save again. This forces WordPress to regenerate the necessary rewrite configuration for IIS.

2. Ensure You Have a Valid web.config File #

Unlike Apache (which uses .htaccess), IIS relies on a web.config file to handle rewrite rules. If this file is missing or misconfigured, permalinks will fail, and static assets like images will throw errors.

• Create a new file named web.config in your WordPress root directory, paste this code:

  <?xml version="1.0" encoding="UTF-8"?>
  <configuration>
    <system.webServer>
      <rewrite>
        <rules>
          <rule name="WordPress Rewrite Rule" stopProcessing="true">
            <match url=".*" />
            <conditions logicalGrouping="MatchAll">
              <add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" />
              <add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" />
            </conditions>
            <action type="Rewrite" url="index.php" />
          </rule>
        </rules>
      </rewrite>
    </system.webServer>
  </configuration>
  

• Critical: Make sure the IIS URL Rewrite module is installed on your server. If it's missing, the rewrite rules won't work—you can install it via the IIS Manager or Web Platform Installer.

3. Verify File/Folder Permissions (Windows-Specific) #

500 errors on images often stem from permission issues on Windows servers. The IIS application pool user needs proper access to your wp-content/uploads folder (where all media is stored).

• Navigate to your WordPress wp-content/uploads folder in File Explorer.
• Right-click the folder → Properties → Security → Edit.
• Add the IIS application pool user (usually IUSR or ApplicationPoolIdentity) to the permissions list.
• Grant the user Read & Execute, List folder contents, and Read permissions (add Write too if you need to upload new media).
• Click Apply and OK to save changes.

4. Check Media Library URL Configuration #

Sometimes broken permalinks can corrupt the base URL for media files. Double-check this setting:

• In WordPress admin, go to Settings → Media.
• Ensure the "Full URL path to files" field is set to your site's base URL (e.g., http://example.com), not something with index.php appended. If it's incorrect, fix it and save.

5. Diagnose the Exact 500 Error Cause #

If the above steps don't fix things, dig into the error details to pinpoint the issue:

• Enable WordPress debugging: Open wp-config.php in your root directory, find the line define('WP_DEBUG', false); and change it to:

  define('WP_DEBUG', true);
  define('WP_DEBUG_LOG', true);
  

• Visit a broken image URL, then check the wp-content/debug.log file for specific error messages (e.g., permission denials, script errors).
• You can also check IIS's server logs (usually located at C:\inetpub\logs\LogFiles) for the 500 error's subcode (e.g., 500.19 means invalid web.config syntax, 500.0 is a general PHP error).

内容的提问来源于stack exchange，提问作者Sagar Singh Verma