Mobile Menu Issue After Update - by Shezad

This topic has 10 replies, 2 voices, and was last updated 2 years, 8 months ago ago by Olga Barlow

  • Avatar: Shezad
    Shezad
    Participant
    July 26, 2021 at 19:46

    Hello,

    I am having an issue with my mobile menu after performing the new update. It seems that the arrows for the dropdown menu disappear and the text (created using static blocks) seems to align incorrectly/displays incorrectly. Please see the screenshots below for further reference. (I have rolled back my website to the pre-updated version)

    After Update Menu (no dropdown arrows)
    https://snipboard.io/CAKPj7.jpg

    After Update Menu (menu not aligned)
    https://snipboard.io/m8ySK2.jpg

    Before Update Menu (dropdown is correct)
    https://snipboard.io/hj3EKy.jpg

    Before Update Menu (arrows displayed properly)
    https://snipboard.io/7UlnoC.jpg

    Please, contact administrator
    for this information.
    9 Answers
    Avatar: Olga Barlow
    Olga Barlow
    Support staff
    July 27, 2021 at 14:24

    Hello,

    Provide us with FTP access to your site. We’ll check the issue in more detail.

    Regards

    Avatar: Olga Barlow
    Olga Barlow
    Support staff
    July 27, 2021 at 16:04

    Hello,

    We were able to upload files via Dashboard. Check the mobile menu now.

    Regards

    Avatar: Shezad
    Shezad
    Participant
    July 27, 2021 at 19:33

    Thank you for doing that, would you mind if I ask you to repeat those steps again as I had an unrelated issue with the website and had to rollback the website to how it was previously (therefore what you did to update properly was undone)

    Avatar: Olga Barlow
    Olga Barlow
    Support staff
    July 28, 2021 at 14:44

    Hello,

    Theme and XStore core plugins updated. Do the backup of these files in case you need to restore the previous backup again.

    Regards

    Avatar: Shezad
    Shezad
    Participant
    July 28, 2021 at 18:42

    Thank you for your help. This time I noticed that the css that applies to the pricing of products turned gray. I went ahead and added “!important” to the theme custom css to resolve this. I also did notice that the mobile menu now is slower compared to what it was previously. While the search bar works instantly (both on iOS and android devices) the menu will sometimes lag when you open and close it a few times, or if you refresh the page then try to open the menu it sometimes takes about 8-10 seconds to open up. Is there something that can be configured for this issue?

    Avatar: Olga Barlow
    Olga Barlow
    Support staff
    July 29, 2021 at 14:07

    Hello,

    I don’t see that menu is slower. Some minimum delay of the menu icon is related to avoiding false clicks. But as a rule, real users don’t make open-close-open-close clicks one after another.

    Regards

    Avatar: Shezad
    Shezad
    Participant
    July 29, 2021 at 16:55

    Hello,

    It seems that the menu actually became slower when opening after this recent theme/plugin update. I was wondering if there was a way to either increase the performance of the menu in some way so it opens quicker and does not delay. If not, could it be a future improvement? As the menu is an important part of the website.

    Avatar: Shezad
    Shezad
    Participant
    July 29, 2021 at 23:15

    Also I am seeing huge delays once again when opening the mobile menu, it often doesn’t open as well. Can you take a look as to what could be causing this issue.

    Avatar: Olga Barlow
    Olga Barlow
    Support staff
    July 30, 2021 at 12:58

    Hello,

    You may try to add the below code to custom CSS to speed up the transition of the off-canvas menu

    .et-off-canvas>.et-mini-content {
        transition-duration: .2s;
        transition-timing-function: linear;
    }

    Also, you can add the padding for the mobile menu icon to increase the area of the click of your menu.

    Regards

  • Viewing 10 results - 1 through 10 (of 10 total)

The issue related to '‘Mobile Menu Issue After Update’' has been successfully resolved, and the topic is now closed for further responses

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.