WordPress.org

Ready to get started?Download WordPress

Forums

124

[resolved] Upgraded to 2.5, now pages don't display...WTF? (108 posts)

  1. c0y0te
    Member
    Posted 6 years ago #

    Upgrade to 2.5 went ahead no problems, then when I test out my site I noticed that all my 'pages' were not found (e..g no post matched criteria) when I clicked on them.

    I've confirmed that the content is still there; tried editing/saving the pages again to see if it would make a difference but it doesn't.

    can someone please tell me how to get my pages displaying again in 2.5 please?

    I've also noticed that 2.5 is MUCH SLOWER than the previous 2.3.3 version. It's taking ages to get anything to load.
    Help?!?

  2. runography
    Member
    Posted 6 years ago #

    I was having this problem and found that I had to change the Custom Permalink Structure.

    Go to Settings->Permalinks

    Custom Structure was checked and I had it set to

    /%postname%

    I changed it to

    /index.php/%postname%

    This seemed to do the trick, not ideal as it has index.php in all the url, but better than just the post id. I haven't a chance to figure out why it did the trick, but glad it did.

  3. ectoplasm
    Member
    Posted 6 years ago #

    I have the same problem. The only way I can view the Pages is to use the default Permalink structure. Anything else returns a 404.

  4. c0y0te
    Member
    Posted 6 years ago #

    It's definitely something to do with permalinks all right, but I can't figure it out.

    I've tried reassigning the permalink and updating .htaccess etc. but in the end I'm just not good enough with all this stuff, so I'll need some help from a more informed soul please.

    My permalink is currently "/index.php/%category%/%postname%" and I'm running a plugin entitled "Deans Permalink Migration" because my original permalink was different.

    When set this way I can see all posts, but not pages. If I change the permalink I can then see pages, but not posts.

    I would love for my entire site to just simply be "/%category%/%postname%" (e.g. no /index.php) but that's never worked for some reason.

    Help?!?

  5. haochi
    Member
    Posted 6 years ago #

    You are running on IIS, which doesn't support mod_rewrite.
    There are more info in the Codex, and it links to several workarounds.

  6. vwoning2
    Member
    Posted 6 years ago #

    I've encountered the same problem. When installing WP 2.5 all posts/pages except the index return a server default error 404. Only when adding /index.php into the Custom Structure do I see my pages.

    /index.php/%year%/%monthnum%/%day%/%postname%/

    I am not hosted on IIS, I am hosted on Apache. I have WordPress installed in a /wordpress/ folder. I have a mod rewrite .htaccess in my root folder to force a www extension and to protect indexless directories and I have pasted the WP .htaccess file into the /wordpress/ folder to enable my settings.

    While troubleshooting this I removed my root level .htaccess and (after dumping cache) tried to view pages without success. So I am reasonably confident I haven't got a .htaccess conflict.

    I have 2.5 RC1 installed and working successfully on another site on the same server. That account has an even more heavily configured .htaccess file in root and there are no problems. I am going to upgrade it to 2.5 and see if it breaks. I'll let you know.

  7. vwoning2
    Member
    Posted 6 years ago #

    OK, it's NOT a WP bug, at least not that I can tell from my upgrade test.

    I have a single VPS account and I have two identically configured websites on it. WP2.5 is on both. Both blogs are in subfolders. On the one that works, it is in a subfolder called /notes/. On the one that's broken, it is in a /wordpress/ subfolder. The .htaccess files are correctly configured for each.

    I'm stumped. There's no reason why one should be different than the other. There are no plugins other than Akismet 1.4 active on either, these are fresh installs.

    To be fair, there may be some hidden problem with the account that is borked. I previously tried installing WP 2.3.3 on that account and got array appearing all over the site. I've never been able to get WP working on that account in 5 minutes.

    I've got better things to do with a Sunday afternoon. And yes, for each install I've nuked the database AND the db-user and started from a clean slate. Far from ideal, but so is a URL hack.

    Anyone else have this experience and find a fix that doesn't involve a URL hack?

  8. man999
    Member
    Posted 6 years ago #

    You need IIS Mod-Rewrite Pro to get rid of the index.php in your URLs. The tool is commercial, but it pays back.

    They also have a detailed step-by-step guide for setting up wordpress clean permalinks on IIS. It involves some tweaking, but it's simple and works fine.

    http://www.micronovae.com/ModRewrite/articles/CleanPermalinksWordpress.html

    I have successfully tested this with WP 2.3.x and 2.2.x, so it's interesting to see if it works with WP 2.5 too, if anybody tries it.

  9. vwoning2
    Member
    Posted 6 years ago #

    OK, I'll fess up.

    I carefully removed my .htaccess files from the server, and examined my local .htaccess files. I had NOT uploaded the correct .htaccess file into the /wordpress/ folder on the borked site...

    Yeah, I know.

  10. unstandable
    Member
    Posted 6 years ago #

    "I have the same problem. The only way I can view the Pages is to use the default Permalink structure. Anything else returns a 404."

    Same thing here for all posts and pages. I switched to the default structure so now people can get to the posts, but it means that all links to my posts are now broken. Anyone know how to fix this?

  11. c0y0te
    Member
    Posted 6 years ago #

    OK - so my options are...

    1) restore to 2.3.3
    2) move to a linux hosted solution
    3) Use IIS/Windows but purchase some tool

    Given that my site was working perfectly (albeit with the /index.php in the URL) and I could access posts AND pages, why am I now forced to choose between the above?

    Is there a problem with WP2.5 or is the problem somewhere else? Why was it working fine in 2.3.3 but not 2.5?

  12. c0y0te
    Member
    Posted 6 years ago #

    One other piece of info... I did a test upgrade of 2.5 first on my test site (http://www.avalon5.com/wptest) and it worked fine, and displayes pages and posts fine.

    I did the same thing on my live site (http://www.avalon5.com) and now I can't display any pages.

    I just don't get it? Why does it work on one installation but not the other?

  13. Pitchslap
    Member
    Posted 6 years ago #

    I'm having the exact same problem, i'm on a windows host have no modrewrite but managed to work around that by using blogname/index.php/postname but now the pages don't work in wordpress 2.5.

    It looks lik anyone on a windows host is going to have this problem so could someone please help or tell us what has changed in wp 2.5 that is causing this?

    once again help please

  14. Aarne Toompark
    Member
    Posted 6 years ago #

    404 error for pages happens also in Apache (2.2.8, Unix and 2.0.54 Linux) hosted sites. The key is /index.php/%postname%/ permalink structure that causes the error.

  15. c0y0te
    Member
    Posted 6 years ago #

    So how do we fix this without breaking all the backlinks? And further - why is it necessary to change when it was all working fine under 2.3.3?

  16. deletedpenguin
    Member
    Posted 6 years ago #

    This sounds very familiar to an issue that I'm having, but I'm not sure if you've got a completely blank page, or if you just don't have any information on the pages. Unfortunately, I can't figure out how my issue may have been related to permalinks. I'd like to think it's as simple as fixing something related to that.

    Here's a thread I started based on my issue. I dunno if it's the same or not...

    http://wordpress.org/support/topic/165191?replies=1

  17. c0y0te
    Member
    Posted 6 years ago #

    To clarify (for deletedpenguin) my posts are no longer visible. The resulting error "No posts matched search criteria" is all that's displayed where the post content should be.

    All the other items (header, footer, sidebar etc.) are all displayed correctly, but my content from every one of my pages is no longer displayed since the upgrade to 2.5

  18. c0y0te
    Member
    Posted 6 years ago #

    Sorry - just realised some typos above but the 'edit' function is not working so to correct it:-

    Posts work fine. Pages do not display. The error message 'no posts matched search criteria' is displayed instead of any content from a page, but all other posts and template functionality is ok

    As a result, anything I had on a dedicated page (e.g. contact form) is no longer displaying/accessible.

  19. Pitchslap
    Member
    Posted 6 years ago #

    Anybody out there?
    I've got 34 pages on my site, so as you can imagine i'm distraught at the moment. Theres no way i can change my permalinks now either as i have over 100 posts and before i changed to index.php/postname they weren't being found by the search engines.

    If anyone has any ideas what to try please reply

  20. jolierouge
    Member
    Posted 6 years ago #

    I'm having the same problem as well. I'm pretty bad at all this fancy stuff, but I'm on a Mac OS X and I would loooove to have my links working again....

  21. deletedpenguin
    Member
    Posted 6 years ago #

    I was able to fix mine. The culprit was the wp-sticky plugin.

  22. c0y0te
    Member
    Posted 6 years ago #

    Deletedpenguin: Unfortunately I don't have the wp-sticky plugin installed so I'm still at a loss.

    Pitchslap - I'm in the same boat. I've over 2 years of content and 800 posts/pages on the site and the thoughts of having to manually backtrack through all that is not appealing.

    Mods/Developers - any ideas on this folks? How can we fix this?

  23. dkappelman
    Member
    Posted 6 years ago #

    I'm having the same problem with pages in 2.5. When I go to any page it, it is not found. I'm on IIS 6.0 and am using /index.php/%postname%/ as my permalink scheme. If I remove the index.php and just use /%postname%/ pages work, but posts do not. Changing the permalink scheme isn't really an option anyway and this works fine in current version I'm using (2.1.2).

    I had to revert back to my previous version until a fix is found.

  24. c0y0te
    Member
    Posted 6 years ago #

    Has anyone from the WP team even acknowledged this error exists yet, or is it just a bunch of us users stumbling around in the dark at the mo?

  25. Justin Tadlock
    Member
    Posted 6 years ago #

    c0y0te, I think it's "just a bunch of us users stumbling around in the dark."

    I've upgraded two blogs fine, have been working with 2.5 trunk for weeks on my local copy (upgrade went well there), and now, when upgrading my main site, things mess up. http://justintadlock.com

    I've tried everything I could possibly think of and have browsed the forums for hours trying out everything I could find but no luck.

    Basically, I can't access anything on my site, except for the dashboard. I just get 404 error messages. I've deactivated all plugins, changed my permalink structure to default, changed to the default theme -- nothing works. I've been using WP for almost 3 years now and have never encountered these type of problems.

    The only reason I upgraded is because it went so smoothly on my other blogs.

  26. c0y0te
    Member
    Posted 6 years ago #

    Well, I've now gone ahead and taken out a new hosting contract with a linux hoster, registered a new domain name and have started another thread looking for help/advice in doing the migration because I can't be arsed with this any more. It just looks like WP is not IIS/Windows happy, and never will be.

    But I have to say in 2+ years of being here on these forums and using WP, this particular upgrade is the worst I've seen for bugs and a lack of response, which is a real shame as it's such a big step up from 2.3

    Like yourself I upgraded my test site (also Windows/IIS) first and it was fine, but when I did the same thing on my live site it buggered the pages but kept the posts for some reason.

  27. Latintop
    Member
    Posted 6 years ago #

    Hi.
    I have the same problem. I upgraded to 2.5 and pages stop working with "no post matched criteria" message on body, headers, footers, sidebar, posts, and everything else works. In my other server with the same configuration it works after upgrade.
    Any clue on this?
    Thanks in advance,
    Jorge

  28. Dan Butcher
    Member
    Posted 6 years ago #

    I'm having a similar problem, except that my site keeps redirecting to https:// for some reason--and Firefox tells me:

    The page isn't redirecting properly
    Firefox has detected that the server is redirecting the request for this address in a way that will never complete.

  29. Dan Butcher
    Member
    Posted 6 years ago #

    Here's another part of the puzzle that makes me think it's something to do with permalinks:
    .../wp/?p=4&preview=true
    will correctly display the page, but
    .../wp/?p=4 redirects to https:.../wp/?p=4 and an error message.

    Why would preview work but not the actual post?

  30. Justin Tadlock
    Member
    Posted 6 years ago #

    I finally got mine fixed (http://justintadlock.com). My database seemed to be the problem because every time I done a new install in a different directory or the root and using that database or a copy of the database, I had the same 404 messages.

    Basically, I had to do a clean install of WP 2.5 and upload my posts with the WP admin import/export feature, which wasn't fun because I had to break all my content down into about 10 .xml files to upload (upload limit at 2MB on my site).

    I still had to keep my users, and luckily, they transferred over fine to a new database, except for about 50 out of 400. Not too big of a loss.

124

Topic Closed

This topic has been closed to new replies.

About this Topic