Missing argument 1 for graphene_title() – help?

  • hanabel

    #4359

    A client moved a site from a development URL to its final domain, and we’re now getting this error that’s breaking the site, even after updating to 1.7:

    <b>Warning</b>: Missing argument 1 for graphene_title(), called in /[filepath]/wp-content/themes/graphene-child/header.php on line 17 and defined in <b>/[filepath]/wp-content/themes/graphene/includes/theme-head.php</b> on line <b>480</b>

    Any help would be greatly appreciated. Thank you!

    hanabel

    #28035

    I changed the title to

    <title><?php wp_title( ” ); ?></title>

    in my custom header file. That got rid of the error, but the site is still totally broken.

    http://bbhousing.org

    I have no idea what happened. This has never happened to me before! I have no idea if it has anything to do with the server/domain move. I wasn’t in charge of that part.

    hanabel

    #28036

    I copied over the header from Graphene 1.7 into my child theme folder and re-customized it and things are looking better. I didn’t realize that customizing specific files in a child theme was so dangerous. I’m primarily a Drupal themer these days, and the pieces work very differently in a Drupal theme.

    I don’t know why this issue showed up only when the site was moved, either. That might be a coincidence/red herring.

    Admin

    Syahir Hakim

    #28037
    Quote:
    I copied over the header from Graphene 1.7 into my child theme folder and re-customized it and things are looking better. I didn’t realize that customizing specific files in a child theme was so dangerous.

    See this:

    http://wiki.khairul-syahir.com/graphene-theme/wiki/Customisation_using_a_child_theme#Special_consideration

    hanabel

    #28038

    Thanks, Syahir. That’s how I would have expected it to work (in Drupal theming, you override base theme template files intentionally). I had read the WordPress documentation and your sticky forum instructions, but missed your documentation page, where the hazards of replacing template files is way more clear. Of course that makes sense given how WP templates are built.

    Thanks to your clear documentation and good code, it was easy to fix, and I will get my few alterations into the functions.php file so this doesn’t happen again.

    Again, thanks for your support and your work. Much appreciated.

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.
Do NOT follow this link or you will be banned from the site!