Forum Replies Created

Viewing 11 posts - 1 through 11 (of 11 total)
  • in reply to: Fonts cut off at the bottom in widget's titles #241253
    bozomax
    Member
    Post count: 16

    So the problem is resolved.

    in reply to: Fonts cut off at the bottom in widget's titles #241251
    bozomax
    Member
    Post count: 16

    That’s great! This has worked, thank you!

    in reply to: Fonts cut off at the bottom in widget's titles #241124
    bozomax
    Member
    Post count: 16

    Hi!

    Thanks! In the end it has worked only when explicitly setting line height of h3:

    h3.spb-heading{
    line-height:10px !important;
    }

    However I still got a question about how to resize the font size for mobile devices. In custom CSS bit I have added this:

    @media handheld {
    h3.spb-heading{
    font-size:16px;
    }
    }

    but that has no effect on the font size on mobile… Any suggestions would be much appreciated!

    Thanks!

    Max

    in reply to: Fonts cut off at the bottom in widget's titles #240722
    bozomax
    Member
    Post count: 16

    Hi!

    Sure. Check here http://www.ocoach-fitness.co.uk/packages-prices/ Look for widget headers: ‘Get FREE tips’, ‘Online Coaching’, ‘Available Packages and Prices’

    Max

    in reply to: Fonts cut off at the bottom in widget's titles #240715
    bozomax
    Member
    Post count: 16

    Hi!

    That is good on the one hand, since you did not notice, or everything works fine in your browser. 🙂

    So, here are the attachments. sc-1 and sc-2 are from my PC, running Win 10 and Chrome 47.0.2526.111 m. sc-3 and 4 are from iPhone 5c’s Safari, with iOS 9.2. I have underlined with red lines places where bottom bits of certain letters are cut off.

    The font used is a Google Font — Playfair Display 700. <h3> size is set to 22px, as I mentioned before changing h3 lineheight in the theme’s settings has no effect. The same thing happens with any font I use, this is clearly an issue with font size, rather than font itself. If I set <h3> size to, for example, 16px everything fits nicely, but I would like to use larger sizes.

    Also, this may be a separate question. Is there a way to have different font sizes for different devices? One size for desktops and the other, smaller, for mobile devices.

    Thanks,

    Max

    Attachments:
    You must be logged in to view attached files.
    in reply to: Polylang plugin integration #139339
    bozomax
    Member
    Post count: 16

    Hi! Thanks for the feedback. I just wanted to mention, that this thing only works for the normal menu, I didn’t change anything in the mobile menu, since, as I mentioned earlier, existing code is able to get the flags and links from the Polylang somehow…

    in reply to: Dante Feature Request #138835
    bozomax
    Member
    Post count: 16

    Hi!

    I’d like to ask you to extend language support.

    At least to make the function sf_language_flags() from ../includes/sf-theme-functions.php (lines 200 – 228) overridable in the child theme by adding conditional function definition:

    if (!function_exists('sf_language_flags')){	
    	function sf_language_flags() {
                ...
            }
    }

    Currently it doesn’t check if the function was defined before. So it is not possible to use any other language plugin except for WPML without modifying the parent theme code.

    in reply to: hatom-entry errors on pages #129550
    bozomax
    Member
    Post count: 16

    Hi, Ed!

    Thanks again for the update. Now it seems that everything works fine, at least I can’t see any errors!

    Thanks for the prompt replies!

    Max

    in reply to: hatom-entry errors on pages #129428
    bozomax
    Member
    Post count: 16

    Hi, Ed!

    Thanks for this. It appeared that some files somehow were getting corrupted while unzipping by the default mac hidden folder! But I’ve realised how to go around this.

    So, yes, the update has worked, now all static pages do not have any structured data errors. However, I noticed that when I set blog element in swift-page builder to blog type ‘standard’ I get these errors from the test:

    hatom-feed
    hatom-entry:	
    entry-title:	Some title 1
    updated:	October 31, 2014
    Error Missing required hCard "author".
    entry-title:	Some title 2
    updated:	October 27, 2014
    Error Missing required hCard "author".
    entry-title:	Some title 3
    updated:	October 16, 2014
    Error Missing required hCard "author".

    And this only happens if blog type is set to ‘standard’, there are no errors when I try to use ‘mini’ or ‘masonry’ blog types.

    Cheers,

    Max

    in reply to: hatom-entry errors on pages #128991
    bozomax
    Member
    Post count: 16

    Hi Ed,

    Many thanks for the update, but something must have gone wrong. This is what I am getting:

    Mac OS X  2�ATTR�d�d-com.macrabbit.Espresso.metadata.uncompressedbplist00�_'com.macrabbit.TextEditor.SelectedRanges�X{524, 0} 57@Mac OS X  2�ATTR�e�e-com.macrabbit.Espresso.metadata.uncompressedbplist00�_'com.macrabbit.TextEditor.SelectedRanges�Y{1122, 0} 57A

    blank page and just this text

    Max

    in reply to: Image Compression and Optimization #128528
    bozomax
    Member
    Post count: 16

    You can try EWWW Image Optimizer. It worked great for me. The only downside was I had to re-attach site favicons after they were optimised, but this is a very quick job.

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