Opened 17 years ago
Closed 17 years ago
#5516 closed defect (bug) (worksforme)
Pretty permalinks redirect to main page after upgrade to 2.3.1
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 2.3.1 |
Component: | General | Keywords: | permalinks |
Focuses: | Cc: |
Description
When I click on a pretty permalink, the individual post is not displayed, instead the main page is shown. This is also true when clicking on page links. Everything works fine with the default ugly links. I have just upgraded from 2.0 to 2.3.1.
This is my site: http://johnmiedema.ca/.
I have searched support. I do not get 404 errors, and I do see any styling problems. I have no problems updating my .htaccess file. It looks like this:
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress
Change History (6)
#3
in reply to:
↑ 2
@
17 years ago
Replying to darkdragon:
So your problem is fixed?
No, I just corrected a miswording.
The original problem still exists: When I click on a pretty permalink, the individual post is not displayed, instead the main page is shown.
#4
follow-up:
↓ 5
@
17 years ago
The reason you see the main page is that some themes default to the "home" page instead of a 404 page. Were you using permalinks prior to your upgrade?
#5
in reply to:
↑ 4
@
17 years ago
Replying to filosofo:
The reason you see the main page is that some themes default to the "home" page instead of a 404 page. Were you using permalinks prior to your upgrade?
I was using permalinks prior to the upgrade without a problem, using the same theme. The problem exists for other themes too. To demonstrate, I have just changed my theme to the default. The problem still exists.
http://johnmiedema.ca (default theme activated)
#6
@
17 years ago
- Resolution set to worksforme
- Status changed from new to closed
Have you recreated the problem in your testing environment? Closing as works for me. Issues of this nature encountered by only one or small amount of members should be isolated on the support forum until a general problem scenario is identified.
My first step would be to ensure that no files from 2.0 still are present, and that all of the 2.3.1 files are in place.
Correction: I do *not* see any styling problems.