12 JULY 2014 - UPDATE

1) We have just released Striking 5.3 maintenance update for those still using the "Original" Striking theme. Please see the theme release thread below for details. This update is only available by the internal update function as this theme is deprecated and no longer available for sale.

2)  Next inline in a few days is Striking MultiFlex. This update is actually "in the can" but we are working on ancillary matters. Expect it sometime in the next few days.

To insert code use <code>...</code>.
Logo disappearing and not centering in responsive mode - FIX ENCLOSED AND IS PART OF NEXT BUILD
  • As per your request, I am posting this here.

    How do you stop the logo from disappearing with the responsive feature enabled? Once you get to a certain point all that is left is the menu and no logo.

    We loaded a mobile logo as well and it still disappears. What settings can we change to ensure the logo always shows on mobile? Also, we have found that the mobile logo is not centering as stated in the notes.

    We are using some custom CSS, but don't think it should affect what is going on.

    You mentioned you found a bug that may cause this to happen to some people and that you could provide an updated skin file that will be in the next update.
  • 4 Comments sorted by
  • Hi Pronet

    Thanks for crossposting from Themeforest per my request.

    The other thread also has some customization that is not applicable to the matter you are posting about.

    Here is the custom css to put into the Striking General Panel/ Custom CSS tab/custom css field:

    @media only screen and (max-width: 767px) {
    #header {
    height: auto !important;
    }

    #logo ,
    #logo_text{
    bottom:0px;
    }
    }



    this is fixed in the forthcoming update 1.0.2 (should be this weekend). Its actually a little mistake on our part. We have the css in the css file, but forgot to include it in the skin.php file. This happened as we were making some adjustments to the loading order in the php file, and we cut, and forgot to paste it back in! :D

    Sorry about the error.

    Best Regards
    Striking Team
    James
  • It is working fine now. Thanks.

    So we should remove this custom CSS after we apply the next update as it won't be needed, correct?
  • Hi Pronet,

    Yes you should remove that code in the next update definitly !! We included the fix so that wont be needed anymore.

    Best regards,
    Striking Team,
    Paul