WordPress.org

Ready to get started?Download WordPress

Forums

Twenty Eleven Accessible child theme error (13 posts)

  1. tapkae
    Member
    Posted 1 year ago #

    Hi. I'm not exactly new at WordPress but I have jumped ship for a couple years. Recently I've been asked to do some work to make sense of a national church site that has particular accessibility needs. I heard that Rian Rietveld's Twenty Eleven Accessible theme would be worth checking out. Only thing is, I get an error code that keeps me from seeing the installed theme. Site is mostly invisible below the header and menu. It goes like this:

    Fatal error: Call to undefined function twentyeleven_content_nav() in /home/uccdm/public_html/wp-content/themes/accessible-twenty-eleven-theme-master/index.php on line 24

    Now, I've looked at these forums for that error code but I've found it all very fragmented and I don't really know what I need to do to satisfy this. I have the PHP doc open here so if there is a line that needs fixing, I just need whatever magic anyone has that would help make the theme work, even to evaluate it.

    Using different themes I have found that there must be some template hierarchy issues going on, as there have been issues with everything being 404'd if a category search is done. That too I could use some guidance on. I read the lit. I just don't know what is really being asked for.

    Oh, and another bit. This site has been someone else's creation and has degraded over time, so I don't know what kinds of funk has accumulated. I did back up the data from the MySQL dbase and have updated to 3.5.1. But I recall from my earlier work that some things are not exactly changed during such version updates and may remain. Is that right? If so, there might be wonkiness I'd not be able to know about until I compare it with a totally new installation. That's something I might do, but not yet since my involvement hasn't been really approved officially.

    Help with the theme and error notice would be handy for now. Thanks.

  2. Joe Dolson
    Member
    Posted 1 year ago #

    Rian's accessibility theme for Twenty Eleven is a child theme; does the site in question have the original Twenty Eleven theme installed? Using a child theme requires that the parent theme be present in order to work.

  3. tapkae
    Member
    Posted 1 year ago #

    Hi Joe. Thanks for replying.

    To be sure, I had Twenty Eleven there but just deleted and reinstalled it anew.

    Because I am experimenting with this stuff, I also have tried a combination of Twenty Ten Five (html5) and a child, Twenty Ten Five Accessible, which I guess relate in the same way.

    Everything is wonky on this site. Either it's gonna be major surgery or replacement and manual copying and reposting just to be certain any of us managing it now would be fully aware of what is installed and how things are done. But since I am a volunteer with limited permission to do things and new at the requirements of accessibility, I can't just do it my way.

  4. tapkae
    Member
    Posted 1 year ago #

    I just did a secondary, parallel installation of WP in a dev folder. Installed the Twenty Eleven and the Accessible Child too. Same error, out of the box with no other complicating settings or data.

    :-(

  5. Joe Dolson
    Member
    Posted 1 year ago #

    Looking at the files at the github repository, I think your solution is to delete the function.php file from the child theme. It shouldn't be in the child theme, because the way child themes work is to load the child theme files instead of the original theme when they're present -- because the functions.php file is present, it's being loaded, but doesn't include any of the theme's custom functions.

    I also note that the theme isn't set up with a parent theme reference; it's just got standard theme info, so I think that you'll also need to edit the stylesheet to make it a legitimate child theme.

    It needs the line 'Template: twenty-eleven' in the stylesheet header.

  6. tapkae
    Member
    Posted 1 year ago #

    Hmm... I did both. The stylesheet editor accepted the adjustment. I ditched the functions.php. Still no change.

    Doesn't look like it did any harm though.

  7. Joe Dolson
    Member
    Posted 1 year ago #

    Hmmm. I think actually the twenty-eleven slug is 'twentyeleven' -- the slug should be the directory that the theme is in.

  8. tapkae
    Member
    Posted 1 year ago #

    I did notice that and made the shift prior to the last post. Still not working right. Same error notice.

    I even tried the same changes at my new installation, with none of the old ghosts lingering. Still no luck.

    Could we be barking up the wrong tree?

  9. Joe Dolson
    Member
    Posted 1 year ago #

    Well, if everything is set up right - both themes uploaded appropriately, the child theme active as the live theme, etc., then even if you were still getting an error, I would expect it to have changed: the error you're getting is pretty clear: the function being called in the child theme doesn't exist.

    That function is defined in the original theme's 'functions.php' file, so what seems to be happening is that the child theme isn't acting as a child theme -- it's not pulling in the parent theme's code.

    Hey - I was just reading the Child Theme info page: http://codex.wordpress.org/Child_Themes

    I noticed a note that says that you need to switch to a different theme and back to the child theme if you change the 'Template' line in the child theme header -- try that. Presumably means that it only parses the header of the theme to identify it as a child on activation.

  10. tapkae
    Member
    Posted 1 year ago #

    DUDE!!!

    That's it. (I had to pinch myself to make sure I wasn't imagining stuff.)

    Or rather, a combination of the bunch of things you brought up:

    • Blast the child theme's functions.php
    • Fix the child theme's missing template name
    • Load an unrelated theme and then return to the desired one

    I managed to get it to work on the newly created dev site which will lurk in the background for some time still, but it's nice to know some of these damned demons have been sent away.

    I've seen that codex page you linked to but as I said, I'm sort of out of the WP loop and it's hard to know what to prioritize when looking at all these things at once.

    Thanks so much.

  11. Rian Rietveld
    Member
    Posted 1 year ago #

    @Ed, thanks for trying out the child theme
    @Joe, Thanks so much for answering and debugging

    This child theme was a rough attempt to make some accessibility improvements, didn't have a clue that someone would actually use it.
    I will make the proper adjustments on the theme at the github.
    Kind regards,
    Rian

  12. Rian Rietveld
    Member
    Posted 1 year ago #

    A new version of the Child theme has been added to the github:
    https://github.com/RRWD/accessible-twenty-eleven-theme

    It should work out of the box now.

    Note: it's not a fully WCAG 2 accessible child theme. I just made some adjustments.
    The accessibility work I do next to my job, in my free time. Still trying to get some funding for time to do a decent study on this subject.

    If you find more bugs, please let me know.

  13. vneha44
    Member
    Posted 11 months ago #

    It is clear that function twentyeleven_content_nav() is not accessible.Look at the functions.php file. There you will find some clue. Function.php in child theme works in parallel to function.php in parent theme.So Check this function belong to which theme parent or child then locate the function and check for errors.

Topic Closed

This topic has been closed to new replies.

About this Topic