WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] Error when assigning Posts Page for twenty twelve Child theme (9 posts)

  1. johnnypass
    Member
    Posted 1 year ago #

    I created a child theme, based on the twenty twelve child theme. I also created a few custom pages templates and some custom headers and footers. Everything is working great except for when I assign the posts to a page.

    When I go to Settings>Readings>Posts Page and assign the posts to a page I created called "Posts", I get a blank white screen. I only get this white screen error when I try to assign the posts to a page, and then it's the only page that appears broken and shows up blank.

    I've done what I think are all the "white screen of death" troubleshooting steps I've read about. Is there a way to generate an error report? Or does anyone have any idea as to how I can trouble shoot this?

  2. Scott Fennell
    Member
    Posted 1 year ago #

    Do you get any errors in debug mode? Tried disabling plugins?

    There maybe be a conflict with naming a page "Posts". Not saying for sure that's a problem here, but I had a problem last year when I named a custom taxonomy "author". Ever since then, I've made a habit terms that are already "WordPress-ish" in creating content.

  3. johnnypass
    Member
    Posted 1 year ago #

    Thanks!
    I tried debug mode
    define('WP_DEBUG', true); in wp_config.php and disabling all the plugins. I also renamed the page "myposts", and none of it seemed to fix anything.

  4. Can you try renaming your page Blog instead? I think that Scott might be right, posts and possibly myposts may be the reason here.

    However, did you also make changes to the index.php in your child theme? It could be that there's an erro on that template.

  5. Scott Fennell
    Member
    Posted 1 year ago #

    To be clear, the title of the page is irrelevant. It's the slug name that would trip you up. If that's even the problem.

    Debug mode isn't intended to "fix" anything, but rather reveal error messages. Inspect the source code to be sure you haven't missed any.

    And does the problem occur if you switch themes?

  6. johnnypass
    Member
    Posted 1 year ago #

    Sorry I meant that the debug mode did not display any error messages. However, when I switched themes, the problem does not occur. So I guess it must be something I did with my child theme! I just can't figure out what.

    I didn't make changes to the index.php - the file is located in the root of the child theme folder and reads `<?php
    // Silence is golden.
    ?>`

  7. johnnypass
    Member
    Posted 1 year ago #

    Ah! So I deleted the custom page templates from the child theme and now the problem is fixed, so I must have done something wrong in the code of my custom page templates.

  8. johnnypass
    Member
    Posted 1 year ago #

    I'm resolving this. Thanks everyone for helping me figure this out! I think the problem was I had copied the full-width.php twenty twelve template to make my own and left this at the top:

    */
    * @package WordPress
    * @subpackage Twenty_Twelve
    * @since Twenty Twelve 1.0
    */

    which I think was messing things up.

  9. Scott Fennell
    Member
    Posted 1 year ago #

    That wouldn't mess anything up if it were written correctly. You have a */ as an opening php comment, which is going to be a fatal error.

Topic Closed

This topic has been closed to new replies.

About this Topic