Missing Toolbar

  • matt3006


    This is related to my recently changing my wordpress install to another directory and something seems to have broken despite the fact, I have deleted graphene and reinstalled it.

    In the user profile, the checkbox for “Toolbar” is enabled. When that is enabled, I notice the entire theme shifts downward to accommodate the toolbar and it doesn’t when you don’t have it checked off.

    I cannot figure out what is responsible for making it work. When I change the theme to the 2011 theme, it works fine but when I go back to Graphene, it is gone again.

    Please advise. Thanks.



    Not entirely sure what you mean here.

    Are you referring to the toolbar that displays across the top of the page when a user is logged in? This is normal. I’m sure we could find a way to disable it, but it would prevent your “members” from being able to easily navigate between the front-end and the back-end of the website.

    This bar is not visible, unless you are logged in.



    Again, I found the problem. It was a “bad” text widget in the footer sidebar with bad code that interfered with displaying the admin toolbar. Basically, that one code messed up two parts of the Graphene theme.



    Haha… yep. Last night, I spent three hours trying to find the problem in one of my plugins… and it was a misplaced semi-colon.

    Glad you got it resolved!



    I had no idea themes could be so sensitive to stray characters in these text widget boxes. I guess they are not as “self-contained” as they may appear.

    I am really beginning to rethink about some of the code I may use. Adding bells & whistles can be a costly inconvenience.


    Kenneth John Odle


    I had no idea themes could be so sensitive to stray characters

    It’s not just themes; it’s anything to do with coding. There’s no such thing as “close enough” when it comes to writing code. Either it’s correct:

    .sidebar {width: 240px;}

    or it’s not:

    #side_bar (witdh; 24Ops:)

    There are nine differences between the two lines of code. They may not mean much to human eyes, but they mean tons to computers. (Most of these are common mistakes I have found in my own code and the code of others.

    I have an ice-cold chocolatey Yoo-Hoo for the first one to spot all nine differences!



    Well, I often refer to it as one of my favorite conumdrum’s… How much is too much?

    Bells and whistles are certainly nice to have… but only in moderation. I once had a link to the worlds worst web page, and it was quite the site!

    Graphene is so powerful, you can add almost any type of code, wherever you like. When coded properly, we can turn Graphene into almost any other site out there.

    One thing I would suggest when adding code or performing modifications is this… MAKE SURE to fully test the change before moving to the next. If you begin attempting to change this… and that… and those…. and then your site breaks; you have no idea where the problem occurred. If you move slowly, and make sure it’s solid… you’ll have no trouble pushing this theme’s flexibility to the max!


    Kenneth John Odle


    I am really beginning to rethink about some of the code I may use. Adding bells & whistles can be a costly inconvenience.

    The thing is to be careful: change only one thing at a time and take notes.

    And yep, you’re right: a lot of what we do is just bells and whistles, but what is bells and whistles for one of us is an absolute necessity for someone else. My best guidance is to decide what you absolutely have to have and get that working first, then go back and add all the fun stuff.

    I’ll get down off my soapbox now…



    I have an ice-cold chocolatey Yoo-Hoo for the first one to spot all nine differences!

    Can I play too??


    Yeah, don’t get discouraged. TRY TRY TRY. If you make a mistake along the way, we will be here to help you fix it. And most of the time, you’ll find it on your own. The best way to get it down, is to practice and make these mistakes that make you more aware of what to look for in code.



    Most of my prior problems related to bad plug-ins so I am always wary of adding new plug-ins my base installation.

    And because of the flexibility of Graphene, I am trying things now I never did before with prior Themes. I don’t usually do my own code. I simply cut and paste code given to me. However, in my recent case, I did not go back to the source. (Stupid) I just took a code snippet from a static html page. Obviously, that was bad form that literally costed me several hours from last night until today. Ugh.

    Thanks for the support. I appreciate it very much.


    Kenneth John Odle


    And learn to be aware of the mistakes you typically make in typing. That “ps” thing–I do that all the time. I just can’t get my finger to bend down to the “x”. So when something doesn’t look right, I search for “ps” and sure enough, there it is!

    Of course, you can play, Josh. But all prizes must be claimed in one hour, or I drink them.



    @Ken, you are absolutely correct about what is bells & whistles today become mandatory tomorrow. I have no problems with your suggestions. One at a time makes good sense. I am going slowly as I add things and testing them to make sure they don’t break anything else.

    WordPress 3.3 is really quite impressive. It has so many nice functions built-in that required plug-ins before. I just love the fact that I need way fewer plug-ins today than before.

    Likewise, Graphene is simply marvelous to work with. I am beginning to appreciate its tremendous flexibility. Those widget text boxes are almost too convenient. It is going to get me into more trouble if I am not extra careful. 🙂



    Well, the first thing I noticed is the first one is valid.

    1. Pound instead of Period.

    2. Underscore

    3. Parenz instead of Bracketz

    4. Mis-spelled “width”

    5. Semi-colon instead of Colon

    6. “ps” instead of “px”

    7. Colon instead of Semi-colon

    8. I’m thinking this would be the same as #3

    9. Okay… either I’m missing something, or you mis-counted…

    I really love Yoo-Hoo’s Too, said “Cindy Lou Hoo”. But don’t leave those bottles in your car on a hot summer day, half-drank, with the cap on!! They become like a ticking time bomb. The pressure that builds in them is unbelievable! I’m not sure what it is in the ingredients, but it’s something crazy. If you figure it out (that teacher instinct), let me know.


    Kenneth John Odle


    Matt, are you talking about ordinary text widgets? Yes, those can be a lot of fun.

    But do you know about Graphene’s Action Hook Widget Areas? If not, take a look at this:


    Just don’t go too crazy!



    Wait until you learn about action hooks!

    EDIT: Ooops, Ken beat me to it.

Viewing 15 posts - 1 through 15 (of 16 total)

You must be logged in to reply to this topic.