Top-menu-bar Social Icons

  • Author
    Posts
  • #2372

    Andrew Misplon
    Keymaster

    Hey Paul

    Thanks for the effort involved here.
    No, wasn’t aware of any issues.
    Sorry for the hassle updates might have caused.

    ultra-icons had one or two icons in it from another pack. I landed up not using them. By moving to font-awesome and shifting to a standard “font-awesome” handle in functions.php we ensure that if a plugin uses Font Awesome and abides by the same standard handle, we won’t be double loading the library. Assuming we both have a the same Font Awesome version number. A long shot! But, still, it’s best practice.

    Ultra 1.0.1 brought about quite a big change. You can now add a social icon to any menu location and at the same time, you can use the social icon menu positions for regular menu items too. So in essence, I did away with the idea of a social icon menu. All menu locations now have this ability.

    Ultra 1.0.1 also brought above a change in that the top bar now has an option responsive feature. It can collapse at the same breakpoint you have set for your main mobile menu. It’s a default OFF option. You can turn it on at Appearance > Theme Settings > Navigation > Responsive Top Bar.

    Ok, so onto the problem. Is the site online? Can you perhaps create a new user account for me to test with so I can get past the maintenance mode plugin if you’re using one?

    [email protected]

    #2399

    Andrew Misplon
    Keymaster

    Hey Paul

    A quick follow-up to see how things are going on your side. Let me know when you have time, I’m keen to get your challenge resolved.

    Ultra 1.0.2 is in the WordPress.org update queue. As part of my initial WooCommerce integration there is a crucial change that will affect all child themes. I’m going to do my best to notify everyone on every support thread regarding child themes that I can access. The change is simple but wide reaching. In every template file there was previously a div closure for the container class:

    </div><!-- .container -->

    That closure must now be moved to footer.php where is should have always been. That’s my bad.

    If you have template files in your child theme or footer.php, a change will need to happen. I’m standing by to assist anyone that needs help with this. I don’t mind doing the change if I get sent a link to the child theme in use.

    Chat soon.

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

You must be logged in to reply to this topic.

Scroll to top