Forum Replies Created

Viewing 29 posts - 1 through 29 (of 29 total)
  • Author
    Posts
  • in reply to: Make "Send us mail" text bigger in Flashlight #81014

    It did! Excellent. Thank you so much, Devin.

    in reply to: Different fonts for h1, h2? #60337

    Please? I suspect the wants and needs of all us users can be overwhelming, so I try my best not to harass you good support people. But I would so love to have one bold, one medium font.

    Hope to hear from you sirs. You’re doing great work.

    in reply to: Background color #61694

    I believe that is under Flashlight Theme Options > General Settings > Background color.

    in reply to: make landscape pictures bigger #61562

    I am simply another happy customer, so I apologize if I intrude. But I have a couple of thoughts on this, since I sometimes struggle with the same problem. The reason our ’portrait’ pictures become bigger is that they are scaled to the width of the content area. This gives them almost twice the size compared to landscape pictures. It’s a fairly common function in WordPress themes and web design in general. As to the slidwshow lightbox in Flashlight, it scales pictures in relation to the screen’s size, so landscape pictures still get bigger.

    I think there are only two solutions to this:

    1) Upload pictures of equal size (e.g. 900px x 675px) and don’t allow WordPress to scale them. Instead, center all images in the column. You get more blank space around portrait pictures, but at least they’re the same size as the landscape ones.

    2) Crop all pictures to squares.

    Very pretty pictures, too.

    in reply to: Different fonts for h1, h2? #60336

    Thank you for your response, Chris!

    Yes, It seems the code I use (pasted a few posts earlier here) replaces the Cufonery. Before that, I selected “No custom fonts” in Flashlight Theme Options, of course.

    I think you are at least partly right. But with the code of my Quick CSS, as it looks right now (see below), h2 is only rendered as a smaller h1. I think of two possibilites: either my code contains conflicting declarations, or Flashlight needs more finesse to deliver h2′s in a different font.

    If you would take a look below and find where I’ve gone wrong, I would be immensely grateful.

    My css:

    .sidebar .widgettitle{font-size:13px;}

    .cufon_headings {

    font-family: "tarzanarbol-071211005EmigreWebOnly", Verdana, sans-serif;

    }

    @font-face{

    font-family: 'tarzanarbol-071211005EmigreWebOnly';

    src: url('wp-content/themes/flashlight/fonts/tarzanarbol-071211005EmigreWebOnly.eot');

    src: url('wp-content/themes/flashlight/fonts/tarzanarbol-071211005EmigreWebOnly.eot?#iefix') format('embedded-opentype'),

    url('wp-content/themes/flashlight/fonts/tarzanarbol-071211005EmigreWebOnly.woff') format('woff');

    }

    @font-face{

    font-family: 'tarzanar-071211005EmigreWebOnly';

    src: url('wp-content/themes/flashlight/fonts/tarzanar-071211005EmigreWebOnly.eot');

    src: url('wp-content/themes/flashlight/fonts/tarzanar-071211005EmigreWebOnly.eot?#iefix') format('embedded-opentype'),

    url('wp-content/themes/flashlight/fonts/tarzanar-071211005EmigreWebOnly.woff') format('woff');

    }

    #top .post-title, #top .entry-mini h1.post-title, h1 {

    font-family: 'tarzanarbol-071211005EmigreWebOnly', Verdana, sans-serif !important;

    }

    h1 { font-family: 'tarzanarbol-071211005EmigreWebOnly', Verdana, sans-serif; }

    h2 { font-family: 'tarzanar-071211005EmigreWebOnly', Verdana, sans-serif; }

    in reply to: Terribly tiny text #61372

    Yes, that works. Thank you Chris!

    in reply to: Different fonts for h1, h2? #60334

    Please sir?

    in reply to: Different fonts for h1, h2? #60333

    Here’s one very nooby idea: Would it be possible to combine the h1, h2 rules with the very first lines of the CSS there?

    What I mean is, it was when you gave me the “cufon headings” line that I got my web fonts to work. Could I construct two of those? Sort of like:

    .cufon_headings 1 {
    font-family: "tarzanarbol-071211005EmigreWebOnly", Verdana, sans-serif;
    }

    .cufon_headings 2 {
    font-family: "tarzanar-071211005EmigreWebOnly", Verdana, sans-serif;
    }

    I know this can’t be correct, but perhaps something is this direction might work? What do you think?

    in reply to: Different fonts for h1, h2? #60332

    Oh! Now we’re talking. I will go try.

    [...]

    Sorry, no. I put back my old @font-face declaration (pasted below), and added your last suggestion. Doing this, I get Tarzana Narrow Bold on all headings. No Tarzana Narrow Regular (the thin variety).

    Then, I went into my welcome page and put <h2>, </h2> around the page title. This page is in Mini Content Area layout, so the difference should show up in the little box on the right. It does — but it’s still Tarzana Bold, only smaller type.

    So the next question, I guess, would be if my @font-face rule is wrongly written. From what I can tell, I’m still only telling Flashlight to let @font-face replace Cufon headings in general (i.e., no distinction between h1 and h2).

    My Quick CSS:

    .cufon_headings {

    font-family: "tarzanarbol-071211005EmigreWebOnly", Verdana, sans-serif;

    }

    @font-face{

    font-family: 'tarzanarbol-071211005EmigreWebOnly';

    src: url('wp-content/themes/flashlight/fonts/tarzanarbol-071211005EmigreWebOnly.eot');

    src: url('wp-content/themes/flashlight/fonts/tarzanarbol-071211005EmigreWebOnly.eot?#iefix') format('embedded-opentype'),

    url('wp-content/themes/flashlight/fonts/tarzanarbol-071211005EmigreWebOnly.woff') format('woff');

    }

    @font-face{

    font-family: 'tarzanar-071211005EmigreWebOnly';

    src: url('wp-content/themes/flashlight/fonts/tarzanar-071211005EmigreWebOnly.eot');

    src: url('wp-content/themes/flashlight/fonts/tarzanar-071211005EmigreWebOnly.eot?#iefix') format('embedded-opentype'),

    url('wp-content/themes/flashlight/fonts/tarzanar-071211005EmigreWebOnly.woff') format('woff');

    }

    #top .post-title, #top .entry-mini h1.post-title, h1 {

    font-family: 'tarzanarbol-071211005EmigreWebOnly', Verdana, sans-serif !important;

    }

    h2 { font-family: 'tarzanar-071211005EmigreWebOnly', Verdana, sans-serif; }

    _______

    As before, the site in question is http://hikki.se/

    in reply to: Different fonts for h1, h2? #60330

    I mean, it’s clear that Flashlight knows how to render headings and paragraphs in different fonts.

    My question is if Flashlight can be told to use certain fonts for certain levels of headings — h1 different from h2. If that is possible, then I can move on to how to make the actual fonts work.

    in reply to: Different fonts for h1, h2? #60329

    OK, I’m back now. Thank you Chris and Dude.

    Unfortunately, none of the kind suggestions you have given me so far have worked. This might be an font issue rather than (the rest of the) CSS, but I haven’t lost hope yet. (I still haven’t seen Tarzana Regular on the page, so it might be my @font-face rule (above) that’s messed up).

    I could be wrong, but I think the problem lies in how to… instruct Flashlight to deploy the first font for h1 headings… and the second font for h2? Could that be right?

    Because only telling Flashlight “do this bold, and that regular” would require the same font in two accompanying variants, rather than the two separate fonts I’ve got. This is only speculation, but I would love your input.

    in reply to: Different fonts for h1, h2? #60327

    No, didn’t take either. Thanks for your patience.

    I’m not insightful enough to know, but I think that if we could figure out if Flashlight makes a distinction between Heading 1 and Heading 2, and if so, where – then maybe we’re in business. I dare not think how much work Kriesi has put into this fine creation.

    There might be a few other things going awry with my page right know (file permissions, stalled updates) so I’m gonna tear it apart right now. We’ll get back to this, kay?

    in reply to: Different fonts for h1, h2? #60325

    Thank you very much for responding, Dude. That code didn’t change anything (although it didn’t break anything either).

    I’m still very uncertain on how Flashlight handles all the styling, but I think it loads the Quick CSS last of all, so any tricks may be pasted there. If that isn’t always the case, please correct me.

    Here below is what I have in my Quick CSS right now. It does load the Tarzana Narrow Bold, but it does so in every heading, and Tarzana Narrow Regular is never seen. Would you, Dude, be able to conclude why that is?


    .cufon_headings {

    font-family: “tarzanarbol-290711001EmigreWebOnly”, Verdana, sans-serif;

    }

    @font-face{

    font-family: ‘tarzanarbol-290711001EmigreWebOnly’;

    src: url(‘wp-content/themes/flashlight/fonts/tarzanarbol-290711001EmigreWebOnly.eot’);

    src: url(‘wp-content/themes/flashlight/fonts/tarzanarbol-290711001EmigreWebOnly.eot?#iefix’) format(‘embedded-opentype’),

    url(‘wp-content/themes/flashlight/fonts/tarzanarbol-290711001EmigreWebOnly.woff’) format(‘woff’);

    }

    @font-face{

    font-family: ‘TarzaNar-290711001EmigreWebOnly’;

    src: url(‘wp-content/themes/flashlight/fonts/TarzaNar-290711001EmigreWebOnly.eot’);

    src: url(‘wp-content/themes/flashlight/fonts/TarzaNar-290711001EmigreWebOnly.eot?#iefix’) format(‘embedded-opentype’),

    url(‘wp-content/themes/flashlight/fonts/TarzaNar-290711001EmigreWebOnly.woff’) format(‘woff’);

    }

    h1 { font-family: ‘tarzanarbol-290711001EmigreWebOnly’, Verdana, sans-serif;

    }

    h2 { font-family: ‘TarzaNar-290711001EmigreWebOnly’, Verdana, sans-serif;

    }

    #top .post-title, #top .entry-mini h1.post-title {

    font-weight: normal !important;

    }

    .main_menu .menu li a strong {

    font-weight: normal !important;

    }

    in reply to: Different fonts for h1, h2? #60323

    Thanks Dude, I’ll try it. The page, by the way, is http://www.hikki.se/

    [Edit] Well, no, that didn’t make a change. I’m trying to get these two fonts to work, and the first one (Bold) does, but it goes everywhere. The second font (Regular) doesn’t load.

    I would love it if I could make the sidebar use the first font, and headlines in the content area use the second font. Is that possible?

    “Every gallery is treated as brand new and, right now, cannot be updated unless you re-upload every image – even if they’re the exact same images you loaded into the media library some time earlier.”

    Aw christ, is that what’s happening? That might explain some the difficulties I’ve been having. And I was just about to rip my whole wordpress installation out, to start from scratch. If you’re semi-new to wordpress, like me, it can be a huge pain trying to figure out what is wrong: if it’s the file permissions on the server, something wonky with your installation, or something in the theme… Maybe I’ll just calm down for a bit, practice patience.

    in reply to: Flashlight @font-face? #57869

    I might have been a bit over-demanding, but at least the site is up and running live now. http://www.hikki.se/

    I want to point out that I can under no circumstances recommend building a wordpress site locally – at least if you’re not some sort of elite developer. It’s really hard to say the secrecy is worth all the terrible hassle. Terrible, I tell you! :D

    Notes: I haven’t been succeeded in telling Flashlight to use Bold for h1 and Medium for h2 yet. Also, if I delete the css from the Quick CSS box, it seems to go away completely, even though it’s also stored in the custom.css file. Still, damn this theme scales beautifully.

    in reply to: Background shouldn't with content #58576

    Okay, I found it. Background image should be set to “Fullscreen” in Theme Options. Silly me.

    in reply to: Flashlight @font-face? #57868

    3. Variation

    I tried duplicating the first cufon line and put in the second font, like this:

    .cufon_headings {

    font-family: “TarzaNar-290711001EmigreWebOnly”, Verdana, sans-serif;

    }

    but that only changed all menu items and content headers to the second font (Tarzana Medium). That’s not the solution, then.

    Also: how do I, for instance, keep menu titles bold but use medium on certain page headers? Using <h2> in the title box doesn’t work.

    in reply to: Flashlight @font-face? #57867

    Allright, let’s ramp it up a bit.

    1. Not a real problem, but odd:

    Right now, I have the same CSS (for my fonts, seen below) pasted in my custom.css and in the Quick CSS box in the Theme Options. I have found that if I delete it from the Quick CSS frame, the custom css will not load either. Isn’t that a bit weird?

    2. Ambition:

    After succeeding in loading @font-face, I want both my font variants to work, but I can’t figure how. I have Tarzana Bold and Medium, and I would like Bold on h1 headings and Medium on h2′s. Below is my code, which does not do the trick. As seen earlier, it does load the first (Tarzana Bold, “tarzanarbol”) both in the menu and as content heads, but not the second (Tarzana Medium, “TarzaNar”). Can you help me figure out why?

    .cufon_headings {

    font-family: “tarzanarbol-290711001EmigreWebOnly”, Verdana, sans-serif;

    }

    @font-face{

    font-family: ‘tarzanarbol-290711001EmigreWebOnly’;

    src: url(‘wp-content/themes/flashlight/fonts/tarzanarbol-290711001EmigreWebOnly.eot’);

    src: url(‘wp-content/themes/flashlight/fonts/tarzanarbol-290711001EmigreWebOnly.eot?#iefix’) format(‘embedded-opentype’),

    url(‘wp-content/themes/flashlight/fonts/tarzanarbol-290711001EmigreWebOnly.woff’) format(‘woff’);

    }

    @font-face{

    font-family: ‘TarzaNar-290711001EmigreWebOnly’;

    src: url(‘wp-content/themes/flashlight/fonts/TarzaNar-290711001EmigreWebOnly.eot’);

    src: url(‘wp-content/themes/flashlight/fonts/TarzaNar-290711001EmigreWebOnly.eot?#iefix’) format(‘embedded-opentype’),

    url(‘wp-content/themes/flashlight/fonts/TarzaNar-290711001EmigreWebOnly.woff’) format(‘woff’);

    }

    h1 { font-family: ‘tarzanarbol-290711001EmigreWebOnly’, Verdana, sans-serif;

    }

    h2 { font-family: ‘TarzaNar-290711001EmigreWebOnly’, Verdana, sans-serif;

    }

    in reply to: Flashlight @font-face? #57866

    It does work. Now I’m gonna try to screw it up by adding the other font variants. And I’m still working locally, so we’ll see how many paths I break when I launch the page.

    Hopefully, this might help anyone else who wants to use webfonts through @font-face, with the Flashlight theme, on WordPress. And even more hopefully, Kriesi thinks it works fine and won’t alter the code in an update down the road. The awesome guy.

    in reply to: Flashlight @font-face? #57864

    (phew)

    Okay, so the trick is to lead Flashlight to load @font-face through the Cufon headings… or something. Here’s what it looks like for me (in the Quick CSS box)

    .cufon_headings {

    font-family: “tarzanarbol-290711001EmigreWebOnly”, Verdana, sans-serif;

    }

    @font-face{

    font-family: ‘tarzanarbol-290711001EmigreWebOnly’;

    src: url(‘wp-content/themes/flashlight/fonts/tarzanarbol-290711001EmigreWebOnly.eot’);

    src: url(‘wp-content/themes/flashlight/fonts/tarzanarbol-290711001EmigreWebOnly.eot?#iefix’) format(‘embedded-opentype’),

    url(‘wp-content/themes/flashlight/fonts/tarzanarbol-290711001EmigreWebOnly.woff’) format(‘woff’);

    }

    Jaysis. Finally.

    in reply to: Flashlight @font-face? #57863

    Thank you Dude. Is there a certain place where I should put that? I tried pasting into the Quick CSS box. That only gave me Verdana, BUT it works in the custom menu too, which is a first. Great! So, I tried pasting the @font-face declaration

    (double checked the path) into the Quick CSS box, but it’s still just Verdana. Oh, wait… Changed the font family name to the weird code name…

    Gaah! It works! Nerdgasm!!

    in reply to: Flashlight @font-face? #57861

    Dear Dude,

    In another thread ( http://kriesi.at/support/topic/font-change-1 ), you gave member Glark this advice: “apply your font-face font/webkit font to the .cufon_headings class”. That sounds a bit different than the various method I have tried to get my web fonts to run. I don’t know enough about CSS, but I’ve sort of been suspecting that all the Cufons are picking a fight with the @font-face declaration. Could you elaborate a bit on the cufon_heading, kindly?

    Also, in another thread ( http://www.kriesi.at/support/topic/font-face-kits-available), davestewart talks about updating the class-style-generator.php file. Could it be related to the troubles I’m having? Or am I just simply wrong?

    in reply to: Changing size in "Mini Content Area" #58053

    That’s very neat. But it makes the text transparent as well!

    in reply to: Flashlight @font-face? #57860

    Thank you for wanting to help me. At the moment I can’t give you a link – my client wants me to work locally until everything is ready for launch. Which really is too bad, because I think I need someone else to look at this.

    But the tarzana… files are the only font material I got when I purchased a web font license from Emigre. And they’re terribly strict on these licensing matters.

    Oh wait – you’re saying that the font-family name could be the culprit? I gotta check.

    Edit: Nope. I changed the font name, in the font-family line, to “Tarzana Narrow Bold” which is the official name of the font. But no luck.

    in reply to: Flashlight @font-face? #57858

    Hey Dude.

    Yes, I believe I did. My whole custom.css looks like this:

    @font-face{

    font-family: ‘tarzanarbol-290711001EmigreWebOnly’;

    src: url(‘fonts/tarzanarbol-290711001EmigreWebOnly.eot’);

    src: url(‘fonts/tarzanarbol-290711001EmigreWebOnly.eot?#iefix’) format(‘embedded-opentype’),

    url(‘fonts/tarzanarbol-290711001EmigreWebOnly.woff’) format(‘woff’);

    }

    But I only see Helvetica. I tried to add some tags, like this:

    h1 { font: 48px/1 tarzanarbol-290711001EmigreWebOnly, Verdana, sans-serif;

    }

    h2 { font: 24px/1 TarzaNar-290711001EmigreWebOnly, Verdana, sans-serif;

    }

    But that only turned content area headlines to Verdana. Can’t say whats wrong. Hopefully you might.

    in reply to: Flashlight @font-face? #57856

    So am I, Dude. I love good support.

    Even so, I’m sorry to say I’m still missing something. I’ve put the @font-face declaration into the custom.css, but nothing’s happening on my site (and here I should probably point out that I’m running it local, since my client (friend) want it to launch only when everything is in place).

    It’s like the rest of the css doesn’t pick up on my “use this font family!” command. Hmm.

    Edit 1: Tried to open my localhost page in Firefox with Error Console turned on. Wow. Lots of warnings about “Declaration dropped”. Wish I was smarter. :´(

    Edit 2: Next, I tried to add declarations for h1 and h2 in my custom.css. That only made content headlines use Times intstead of Helvetica Neue. What have I done wrong?

    in reply to: Flashlight @font-face? #57854

    Great. It works too. Thank you kind Sir!

    in reply to: Flashlight @font-face? #57852

    Hello Chris, thank you for your response.

    1. Right, disabling the custom fonts, that works. Next: the only custom.css file I can find is in wp-content > themes > flashlight > css.

    At the moment, all that this file says currently is: “/* Have fun adding your style here :) – PS: At all times this file should contain a comment or a rule, otherwise opera might act buggy :( */” I guess this is where any code I add in the Quick CSS box ends up.

    But you are suggesting I put the @font-face declaration into this custom.css file, is that correct?

    2. I found the style.css and the text-transform line you suggested, and changed ’uppercase’ to ’none’. That got rid of uppercase in the content areas, but I still have uppercase in the menu (which is a custom menu, as you can do in Flashlight).

    I found that style.css contains several instances of “text-transform: uppercase;”. Should I change all of them to “none”?

Viewing 29 posts - 1 through 29 (of 29 total)