Header for Blogum Theme

  • Author
  • #696264

    Hey there! Quick question. I’m really struggling to insert an image instead of the theme’s title. I was just wondering, how do you insert an image AND delete the text that is the “header”. I really like this theme and I’m quite satisfied. I just need to know what css codes to write in, in order to add an image.

    I guess I’m sort of an amateur with CSS. I just need the codes to override the original header with a customized one.



    What is your blog URL?

    Note that you can upload a header for the Blogum theme using the Appearance → Header page. Did you want a header different than that one?

    To hide the blog title and description in the Blogum theme, try this:

    hgroup {
         display: none;

    If you do that, you may want to adjust the spacing too:

    hgroup {
         display: none;
    #header {
         padding: 50px 0px 37px 0px;
    #access {
        width: 660px;


    Hm, there is no Appearance > Header page in the theme I’ve just downloaded. Am I missing something?

    Or is there a way to manually (via code) change the site name to a logo/image?




    the theme I’ve just downloaded

    On this forum we provide support only to those who have free hosted WordPress.com blog and who have purchased an annually renewable custom design upgrade. There is no FTP access to free hosted WordPress.COM blogs and we cannot install individual plugins or any themes into them. The themes and plugins found on the internet are for wordpress.ORG installs which run on different software.

    On free hosted wordpress.COM blogs we can only use the themes which have been coded to run on this multi-user software and made available to us here. > Appearance > Themes and no others. We cannot edit either themes or templates on free hosted wordpress.COM blogs. > http://en.support.wordpress.com/themes/editing-themes/

    WordPress.COM vs WordPress.ORG: The Differences


    In regards to the CSS code you have about removing the Blogum text header so that just the image header remains.

    I inserted the CSS and it did remove the text header, however if i want to make the CSS change permanent i have to pay $30 to wordpress. Is there a way to remove it without having to pay.


    with that CSS code, it leaves my “about” and “home” page links hovering above the header, how could i edit the code that have them hover below the header?



    There is no way to accomplish either of those things without the Custom Design upgrade, but yes the menu/navigation can be moved below the header with CSS. In some themes it is trickier than in others, but almost always doable.


    @spearmintictac: You can do it without having to pay. Paste this in a text widget:

    <div align="center" style="position:absolute;top:0;left:0;z-index:11;width:100%;height:300px;background-color:#fff;">

    <div style="position:relative;top:65px;">
    <a href="http://emilyspencer.org/"><img style="max-width:945px;" src="http://emilyspencerdotorg.files.wordpress.com/2011/09/cropped-websitebanner.jpg"></a>
    <div style="position:relative;top:57px;text-align:left;margin-left:160px;font-size:16px;font-weight:bold;">

    <a style="color:#000;text-decoration:none;" href="http://emilyspencer.org/">Home</a> / <a style="color:#000;text-decoration:none;" href="http://emilyspencer.org/about/">About</a>

    You can change the top:65 and top:57 numbers to adjust the vertical positioning of the image and the tabs, but don’t mess with anything else if you aren’t very experienced in coding. If you need any other adjustments, let me know.


    Coding html and css into a text widget is not really an ideal way to make an update like this because it relies on hard coded links instead of the built in function for generating navigation in the theme or using custom menus and it also is not supported if possible future changes are made to WordPress.com that could affect code like that.

    Using the Custom Design upgrade, you can move the top navigation below the header image using CSS like this:

    #header {
    	padding: 150px 0px 37px 0px;
    #header-image {
    	margin: 0px;
    	position: absolute;
    	top: 0px;

    @designsimply: You make changes all the time, and when this happens we adapt our answers accordingly. At the moment my suggestion works, doesn’t it? Avoiding to use something that works now because it might no longer work “if possible future changes are made” is not a plausible argument. (Would you find it reasonable if I started telling users not to use, say, the current gallery shortcode options, or the current audio player shortcode options, or the current image options, or whatever, because things might, possibly, be different in future versions of WP?)


    I wish I had discovered this forum earlier, everyone is so helpful!! Thanks guys :-)
    @panaghiotisadam, I placed your code into a text widget and it worked a charm. Thanks!
    I do have one more question, can I use the same text widget to remove the search bar from the site too?


    Oh and I just thought of another question, how can I change my favicon in Blogum?



    You can update your favicon by setting up a blavatar: http://en.support.wordpress.com/avatars/blavatars/


    @panaghiotisadam, let me try to respond in another way. The solution you posted basically circumvents the paid upgrade for custom design. WordPress.com provides free hosting but we ask for optional payments for some features. Similar to asking you not to remove the footer credits, we ask that you not circumvent paid upgrades like that.



    You’re welcome.

    The searchbox you’re seeing now is part of the Nothing Found message you’re getting because you have deleted the sample “Hello World” post and your blog front has nothing to display. If you publish a post, or if you create an intro page and set your front to display that page (in Settings>Reading), the whole message including the searchbox will disappear.


    In my previous response I tried to be polite and avoided spelling out what your reply was and what the real reason behind it is. I’m dumbstruck you did it yourself.

    Check my front page please: http://wpbtips.wordpress.com/
    You really expect me not to do any of this because you would like me to pay for it while it’s possible for free? I’m afraid this is like me driving my bike in a small country road and suddenly seeing you in the middle of the road asking me not to use that road or tell other drivers about it because you operate a pay-toll highway nearby. Well, we’ll use your highway if and when we need the advantages it offers, not just because you want to collect toll and you hate it that there’s also a passable toll-free road leading to a couple of the thousand destinations the highway does.

    Compared to the CD upgrade, there’s very little you can do with the position property. But anyway it’s a perfectly legitimate (and by no means secret) piece of CSS, so I’m not to blame if it can occasionally deprive you of a few extra bucks. If you ask me not to use it, then what next? When, for example, I give inline CSS solutions to users who cannot fathom why their tables are a mess in some of the newer themes, will you tell me not to because the table CSS can be corrected if you buy the CD upgrade? Or if in a future upgrade you add a table tool, will you then ask me to stop using or suggesting table coding? You can’t be serious!

    “Similar to asking you not to remove the footer credits”? The one is a reasonable request, based on the ethics of giving due credit, while the other is an absurd request, based on greed and involving dishonesty: so, sorry, I don’t see any similarity between the two and I don’t see why I should comply with the second one.


    I’m sorry you feel that way. Asking someone to pay for a service a company has setup instead of trying to get it for free is not dishonest in any way. Please don’t feel distressed, and please try not to deliberately go around the paid upgrades.

    If you find problems with table coding in existing themes that you feel should be working without extra CSS, please let us know and we’ll take a look to see if there’s anything we can do to help.


    Sorry, my bad phrasing led to a misunderstanding: the “dishonest” bit referred to me, not to you. If you ask me not to reveal a technique I’m familiar with, you ask me to deliberately deceive fellow users. That’s what I meant by dishonest. If you check the comments in my blog, you’ll see many replies of the sort “sorry, not possible unless you buy the Custom Design upgrade”. But in the few cases when something is possible without the upgrade, I’m not prepared to start lying for your sake. (Unless you want me to turn my replies in those cases to “well, actually it’s possible but WP doesn’t want me to tell you so you’ll be forced to pay for something you don’t have to” and we’ll all have some fun.)

    I think my readers will enjoy a post about this…



    It’s not that your fixes aren’t correct, just that the style loophole will be closed at some point because it’s a bug, not a feature, and is mostly used by spammers.


    So, so far we’ve got:
    Version 1 – My workaround is not good because it relies on hard coded links and because it may not work if future changes are made.
    Version 2 – No it’s not that, it’s that it circumvents the need to buy the CD upgrade.
    Version 3 – No it’s not that, it’s that it’s a bug although it’s a correct fix.

    I wonder, are you happy with the impression you’re giving?

    As for “loophole that will be closed”, let me remind you that you had promised the same thing long ago. When we asked why, Alex told us “because bad guys use it to do bad things“. But you yourself had clarified that it “will continue to work if you have the CSS upgrade, will get stripped if you don’t“. So apparently bad guys (spammers?) are no longer bad guys if they pay for the upgrade. So I find it very hard to believe that Version 3 is closer to the truth than Version 2.

    PS I’d really like to see what devblog would have to say on (a) hard coded links = bad and (b) position property = bug.


    Matt says,

    It’s not that your fixes aren’t correct, just that the style loophole will be closed at some point because it’s a bug, not a feature, and is mostly used by spammers.

    You aren’t talking about taking away “style” completely are you (i.e. the ability to style post and page elements with inline CSS such as margins, padding, font-family, etc.) are you? With so much of HTML attributes now being depreciated, this could become a big hardship. The example that pops to mind would be HTML tables. Virtually all of the styling attributes are now depreciated so the only way to style them is with inline CSS.


    I think it will be rather tricky to get the right balance, which is partly why I asked politely for workarounds not to be encouraged. I can’t say for certain right now what the changes will be in the future, but I do appreciate your concern and please know that what you bring up will be discussed and considered and reviewed.

    Note: hard coded links are fine in general. However, making hard links in place of existing menus is not a best practice because it takes away the ability to use the built in theme option or custom menu option to edit menus. It causes confusion for people in the same way that copying original CSS does when it breaks the built in header image option.

The topic ‘Header for Blogum Theme’ is closed to new replies.