“Pages” all give 404 errors

  • ajkessel

    (@ajkessel)


    15 years, 7 months ago

    Using 2.6.1, serving from my own Debian server. At some point, all of my “pages” (i.e., not the posts) stopped working. Instead I get a 404 error for all of them. The posts and everything else seem fine. I’ve tried creating new pages and following the links to them and still I get a 404. I have a standard .htaccess file aside from some extra stuff for Gallery/wpg2 that doesn’t seem to have anything to do with this issue. I’m not even sure how to begin troubleshooting. Apache error log offers no insight. Any recommendations?

Viewing 15 replies - 1 through 15 (of 31 total)
1 2 3
  • Thread Starter ajkessel

    (@ajkessel)

    15 years, 7 months ago

    Just pinging this group again. I can’t for the life of me figure out why none of my “pages” work.

    ripose

    (@ripose)

    15 years, 7 months ago

    Check in Dashboard > Settings > General . Are the 2 URL’s correct?
    Check wp-config.php are the // ** MySQL settings ** // settings at the top correct?

    Hope this helps. Have a great day!

    Lorelle

    (@lorelle)

    15 years, 7 months ago

    And see this: http://wordpress.org/support/topic/189058

    Thread Starter ajkessel

    (@ajkessel)

    15 years, 7 months ago

    Thanks for your responses. The URLs in the dashboard are correct and the MySQL settings in wp-config.php are also correct. Note that everything works in the installation (i.e., posts, RSS feeds, the dashboard, etc.) except pages.

    I checked out the bug report at http://wordpress.org/support/topic/189058 and fixes discussed there. First, it appears the problem was fixed in 2.6.1, and I’m using 2.6.2. I also tried moving index.php out of the way but that disabled the entire blog (even though I’m using a linux server). I also added category and tag bases, and that didn’t help either.

    I’m still stumped.

    Thread Starter ajkessel

    (@ajkessel)

    15 years, 7 months ago

    By the way, here’s the debug output for a broken page (with the parent path removed). Does this help anyone?

    Notice: get_settings is deprecated since version 0.0! Use get_option() instead. in (PATH HERE)/wp-includes/functions.php on line 2146

    Notice: get_settings is deprecated since version 0.0! Use get_option() instead. in (PATH HERE)/wp-includes/functions.php on line 2146

    Warning: Cannot modify header information – headers already sent by (output started at (PATH HERE)/wp-includes/functions.php:2146) in (PATH HERE)/wp-content/plugins/bad-behavior/bad-behavior/screener.inc.php on line 8

    Notice: Use of undefined constant livecal_spinner – assumed ‘livecal_spinner’ in (PATH HERE)/wp-content/plugins/livecalendar.php on line 36

    Notice: Use of undefined constant livecal_labeltype – assumed ‘livecal_labeltype’ in (PATH HERE)/wp-content/plugins/livecalendar.php on line 50

    Notice: Use of undefined constant livecal_dir – assumed ‘livecal_dir’ in (PATH HERE)/wp-content/plugins/livecalendar.php on line 57

    Notice: Undefined index: g2_validated in (PATH HERE)/wp-content/plugins/wpg2/wpg2.php on line 89

    Notice: Undefined index: g2_validated in (PATH HERE)/wp-content/plugins/wpg2/wpg2.php on line 101

    Notice: Undefined index: g2_validated in (PATH HERE)/wp-content/plugins/wpg2/wpg2.php on line 163

    Notice: Undefined index: cat in (PATH HERE)/wp-includes/query.php on line 525

    Notice: Only variable references should be returned by reference in (PATH HERE)/wp-includes/taxonomy.php on line 710

    Notice: Only variable references should be returned by reference in (PATH HERE)/wp-includes/taxonomy.php on line 609

    Notice: Undefined index: port in (PATH HERE)/wp-includes/canonical.php on line 187

    Notice: Undefined index: query in (PATH HERE)/wp-includes/canonical.php on line 187

    Notice: Undefined index: port in (PATH HERE)/wp-includes/canonical.php on line 187

    Notice: Undefined index: query in (PATH HERE)/wp-includes/canonical.php on line 187

    Warning: Cannot modify header information – headers already sent by (output started at (PATH HERE)/wp-includes/functions.php:2146) in (PATH HERE)/wp-content/themes/water-10/404.php on line 1

    Warning: Cannot modify header information – headers already sent by (output started at (PATH HERE)/wp-includes/functions.php:2146) in (PATH HERE)/wp-content/themes/water-10/header.php on line 1

    Notice: get_settings is deprecated since version 0.0! Use get_option() instead. in (PATH HERE)/wp-includes/functions.php on line 2146

    Notice: get_settings is deprecated since version 0.0! Use get_option() instead. in (PATH HERE)/wp-includes/functions.php on line 2146

    ripose

    (@ripose)

    15 years, 7 months ago

    This should explain part of the problem: Documentation Link

    Also check your Server Error logs.

    Mobile 1 Pet Wombat Landing Platform: Signing off…

    Thread Starter ajkessel

    (@ajkessel)

    15 years, 7 months ago

    Nothing useful in server error logs.

    I don’t think the “cannot modify header information” is relevant here. The reason we’re seeing that error is with WP_DEBUG on, deprecated functions are triggering error messages. Those error messages are what is causing the “cannot modify header information,” at least in the first several instances. If I silence the deprecated function warning and turn WP_DEBUG on, I get a lot fewer errors. Still not sure if any of these are the clue to my problem of pages all giving 404 errors. Maybe it is the canonical.php issue?

    Notice: Use of undefined constant livecal_spinner – assumed ‘livecal_spinner’ in (PATH HERE)/wp-content/plugins/livecalendar.php on line 36

    Notice: Use of undefined constant livecal_labeltype – assumed ‘livecal_labeltype’ in (PATH HERE)/wp-content/plugins/livecalendar.php on line 50

    Notice: Use of undefined constant livecal_dir – assumed ‘livecal_dir’ in (PATH HERE)/wp-content/plugins/livecalendar.php on line 57

    Notice: Undefined index: g2_validated in (PATH HERE)/wp-content/plugins/wpg2/wpg2.php on line 89

    Notice: Undefined index: g2_validated in (PATH HERE)/wp-content/plugins/wpg2/wpg2.php on line 101

    Notice: Undefined index: g2_validated in (PATH HERE)/wp-content/plugins/wpg2/wpg2.php on line 163

    Notice: Undefined index: cat in (PATH HERE)/wp-includes/query.php on line 525

    Notice: Only variable references should be returned by reference in (PATH HERE)/wp-includes/taxonomy.php on line 710

    Notice: Only variable references should be returned by reference in (PATH HERE)/wp-includes/taxonomy.php on line 609

    Notice: Undefined index: port in (PATH HERE)/wp-includes/canonical.php on line 187

    Notice: Undefined index: query in (PATH HERE)/wp-includes/canonical.php on line 187

    Notice: Undefined index: port in (PATH HERE)/wp-includes/canonical.php on line 187

    Notice: Undefined index: query in (PATH HERE)/wp-includes/canonical.php on line 187

    Warning: Cannot modify header information – headers already sent by (output started at (PATH HERE)/wp-content/plugins/livecalendar.php:36) in (PATH HERE)/wp-content/themes/water-10/404.php on line 1

    Warning: Cannot modify header information – headers already sent by (output started at (PATH HERE)/wp-content/plugins/livecalendar.php:36) in (PATH HERE)/wp-content/themes/water-10/header.php on line 1

    Thread Starter ajkessel

    (@ajkessel)

    15 years, 7 months ago

    By the way, I’m pretty sure the last two “cannot modify header information” warnings are also caused by the insertion of the debug errors immediately above them. I’m also thinking the canonical.php errors are not real issues, since here there is no specified port or query string in the URL.

    ripose

    (@ripose)

    15 years, 7 months ago

    Hmm, perplexing.

    I do have one (or two) obvious question(s) though.

    Did you update your site in the past, from 2.1 > 2.6 or anything similar?
    If so did you delete your old WP files first?

    If not than the only places “deprecated” error messages could be coming from is plugins or themes.
    Using old plugins/themes?

    This assumes of course, that your server is using the correct versions of Apache/MySQL and that your database is not corrupt.

    Thread Starter ajkessel

    (@ajkessel)

    15 years, 7 months ago

    I’ve update many times — I’ve been using WordPress for several years. The updates were generally continuous, though, so I wouldn’t have jumped from 2.1 to 2.6.

    I believe all the deprecated errors are in fact coming from plugins or themes. I did test disabling all plugins and still no “pages” can be displayed. I don’t think there is any reason to think the “deprecated” warnings relate to the “pages” problem, is there?

    Using apache 1.3, PHP 5.2.0, MySQL 5.0.

    Also no sign the database is corrupt. Everything works except pages. If I create a brand new page, it doesn’t work either.

    ripose

    (@ripose)

    15 years, 7 months ago

    Error messages don’t always point out WHERE the error occurred, sometimes they may display another line that is affected by the error. I’m not sure if WP debug does this.

    I found that conflicting settings in some SEO plugins created the missing pages problem. Have you been using All In One SEO or something similar?

    BTW – All In One SEO works great, unless the settings are wrong (go figure).

    Thread Starter ajkessel

    (@ajkessel)

    15 years, 7 months ago

    No SEO plugins.

    Active plugins:

    Advanced Permalinks
    Akismet
    Bad Behavior
    Batch Categories
    Blosxom Rewrite
    CountPosts
    Edit Comments
    Google Code Prettify
    Interlinks
    LiveCalendar
    Markdown
    Search & Replace
    ShareThis
    SimpleTags
    Twitter widget
    Update Manager
    Viper’s Video Quicktags

    But, again, disabling all plugins doesn’t seem to fix the problem.

    ripose

    (@ripose)

    15 years, 7 months ago

    Thanks for the list, it helps.
    It would be helpful if you included links to your site.

    Don’t forget that disabling a plugin does not necessarily undo changes it may have made to your code.
    You need to update plugins and themes to have the old stuff rewritten. But even then they may still leave crap behind, it’s a start though.

    Once again, assuming your site URLs are correct, and settings are correct and that you don’t have different folders than the defaults, than post some of your code for pages that don’t display.

    You could also check for nested folders, there is a plugin for this.

    Thread Starter ajkessel

    (@ajkessel)

    15 years, 7 months ago

    My site is <http://adam.rosi-kessel.org&gt;.

    All of the pages in the righthand column are broken. E.g. <http://adam.rosi-kessel.org/weblog/about&gt;.

    Thread Starter ajkessel

    (@ajkessel)

    15 years, 7 months ago

    Sorry, as links: main site; broken link that used to work.

    I’m pretty sure I don’t have any nested folders. I’m still puzzled at how a plugin or theme could affect only pages and not posts. What I’d really like to see is some sort of trace of how it’s trying to resolve the pages and where the breakage is happening.

Viewing 15 replies - 1 through 15 (of 31 total)
1 2 3
  • The topic ‘“Pages” all give 404 errors’ is closed to new replies.