• i was in working on a friend’s site – their dev guy split – and was adding a new page. after creating a page draft, i upgraded to version 3.0.1. all page content ceased to display after that. it’s all still in the wp backend, but it just doesn’t show on the live site.

    the url is https://www.brixenivy.com. it’s hosted on hostgator.com

    i’m fairly sure the issue is that it’s just not calling the page properly. i did a repair on the database, after reading a post that suggested that (and it worked for that person). still, not working.

    i cannot change anything in the permalinks. they are greyed out. i wanted to ask in here before doing anything like deleting an .htaccess file and having it remade.

    i’ve built a few sites with wordpress, but all pretty simple and never had to come mess around with anyone else’s code.

    this is the current page.php code.

    <?php
    /**
    * @package WordPress
    * @subpackage Default_Theme
    */

    get_header(); ?>

    <div id=”content”>
    <?php the_content(); ?>
    </div>

    <?php get_sidebar(); ?>

    <?php get_footer(); ?>

    there is a huge event coming in three weeks and i really can’t afford to have any time down. it’s already been 5 hours…

Viewing 10 replies - 1 through 10 (of 10 total)
  • Moderator James Huff

    (@macmanx)

    You may need to repair the database.

    Access your WordPress database via phpMyAdmin (most hosting providers offer this in their control panel), check all of the tables, and choose “Repair tables” from the pull-down menu.

    Thread Starter mychiefs58

    (@mychiefs58)

    thanks for your quick reply. i tried this, but to no avail.

    Thread Starter mychiefs58

    (@mychiefs58)

    actually, i just tried repairing the “information_schema” database. when i try that, whether all tables or any single one i get the following error.

    Fatal error: Cannot redeclare pma_tableheader() (previously declared in /usr/local/cpanel/base/3rdparty/phpMyAdmin/db_structure.php:83) in /usr/local/cpanel/base/3rdparty/phpMyAdmin/db_structure.php on line 118

    Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Turn off all your plugins. You may have one that’s no good with 3.0.1

    Did you upgrade from 2.9 or 3.0?

    Thread Starter mychiefs58

    (@mychiefs58)

    ok…i tried that as well. nothing.

    i don’t know what version i upgraded from, and i now know i should have checked that. i never ran across this with any of the other wp sites i built.

    i have a feeling that if i could reset the permalinks it might work, but they are greyed out with no access to them.

    Moderator James Huff

    (@macmanx)

    actually, i just tried repairing the “information_schema” database. when i try that, whether all tables or any single one i get the following error.

    You can’t repair the information_schema. Have you tried repairing the actual database? The only with wp_posts, wp_comments, etc.

    Thread Starter mychiefs58

    (@mychiefs58)

    i did do a repair on that database and it said it worked. i just ran it again, and also ran the optimization. no changes.

    i really wish i knew wordpress better. my guess is that this will be an easy fix, but it’s taking me hours to figure out. worked until 1 am on it last night, on it again this morning.

    i am clear as to the result of the problem. a “view source” of the site will show the call for the header, rightrail, and footer. there is no completed call for the content.

    the code that makes this call is shown in my first post. i guess i just need to figure out how to backtrack…find the function, etc. i don’t know php…guess it’s time to get cracking on that…

    Moderator James Huff

    (@macmanx)

    Try switching to the Twenty Ten theme to rule-out a theme-specific issue.

    Thread Starter mychiefs58

    (@mychiefs58)

    ok…this is really odd. to me, at least.

    this is the code for page.php that used to work.

    <?php
    /**
    * @package WordPress
    * @subpackage Default_Theme
    */

    get_header(); ?>

    <div id=”content”>
    <?php the_content(); ?>
    </div>

    <?php get_sidebar(); ?>

    <?php get_footer(); ?>

    i switched themes as suggested (already knew based on the preview that it seemed to work) and everything showed up. then switched back and it was still broken.

    the solitary backup from february had the same code as above. however, there was a rough draft of the template the original developer made, and there was more code in that. i made some changes and ended up with the following.

    <?php
    /**
    * @package WordPress
    * @subpackage Default_Theme
    */

    get_header(); ?>

    <div id=”content” class=”narrowcolumn” role=”main”>

    <?php if (have_posts()) : while (have_posts()) : the_post(); ?>
    <div class=”post” id=”post-<?php the_ID(); ?>”>

    <div class=”entry”>

    <?php the_content(‘<p class=”serif”>Read the rest of this page »</p>’); ?>

    <?php wp_link_pages(array(‘before’ => ‘<p>Pages: ‘, ‘after’ => ‘</p>’, ‘next_or_number’ => ‘number’)); ?>

    </div>
    </div>
    <?php endwhile; endif; ?>

    </div>

    <?php get_sidebar(); ?>

    <?php get_footer(); ?>

    what i don’t understand is what could have changed in the upgrade to 3.0.1 that would break the original code, but allow this to work. i’m also wondering if there’s anything unnecessary in this latest iteration. i took out a few things, but still am not sure it’s as streamlined as it can be.

    Moderator James Huff

    (@macmanx)

    It all looks fine to me. It’s really hard to tell the differences etc without seeing all of the theme files and how they relate.

    If the theme files were originally part of the core themes (Classic, Default, and Twenty Ten), they would have been replaced during the upgrade, which is why we recommend using a child theme instead of modifying the core themes.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘upgrade to 3.0.1 and all page content is gone’ is closed to new replies.