Viewing 16 posts - 1 through 16 (of 16 total)
  • Author
    Posts
  • #1402287

    Hello, I have arranged some colour sections underneath each other and created an arrow for scrolling, but when I click on the arrow, it does not move completely to the next screen, a “rest” of the previous section remains visible in the header and thus the next arrow is not visible.

    Can you help?
    Thank you very much!

    #1402450

    Hi xela,

    Please post us your login credentials (in the “private data” field), so we can take a look at your backend.

    1. Install and activate ” Temporary Login Without Password “.
    2. Go to ” Users > Temporary Logins ” on the left-side menu.
    3. Click ” Create New “.
    4. Add the email address for the account ( you can use (Email address hidden if logged out) ), as well as the ” Role ” making that the highest possible and the expiry about four days
      ( to be sure that we have enough time to debug ).
    5. Click ” Submit “.
    6. You’ll now have a temporary account. Please provide us here in the private section the URL, so we can login and help you out.

    When your issue is fixed, you can always remove the plugin!
    If you prefer to not use the plugin, you can manually create an admin user and post the login credentials in the “private data” field.

    Best regards,
    Nikko

    #1402604
    This reply has been marked as private.
    #1402735

    Hi xela,

    Thanks for giving us admin access.
    It seems visually it looks like the scroll-down arrow was not functioning correctly however, it seems that the header being totally transparent was causing some visual problems.
    The way our scroll-down arrow works is that the header snaps with the top area of the next section, in order to change this functionality, you will need to modify a core js file (which we do not recommend), wp-content/enfold/js/avia.js line 968 (Enfold 5.5)

    target =  container_offset - fixedMainPadding,

    replace it with:

    target =  container_offset - 0,

    Please try to clear browser cache and check your page.
    Also, with this change, every theme update, you’ll need to replace this part of the avia.js

    Best regards,
    Nikko

    #1402736

    Thanks for your answer.
    I will check it.

    As you do not recommend it: is there a workaround where I can scroll automatically between full-page-sections an d having a transparent header?

    Alex

    #1402741

    I checked it and unfortunately it won’t work…

    #1402742

    Hi Alex,

    Unfortunately, there’s no other method to change it directly on the core js file.
    It’s not recommended because you’ll have to modify it every theme update, which is a bit of a hassle but the risk on the site is very low since it wouldn’t impact anything except the scrolling to the next section.

    Best regards,
    Nikko

    #1402743

    okay, I see, but as mentioned above the solution does not work.

    #1402745

    Hi Alex,

    I have tried this solution on my end and it works, the problem most likely is cached js file.
    Can I request for FTP access? so I can try to check it further.

    Best regards,
    Nikko

    #1402748
    This reply has been marked as private.
    #1402758

    Hi Alex,

    Thanks for giving us FTP access.
    I have inspected it and the changes you made are correct though you are still using Enfold 5.2.1 (which means the line number is not the same).
    I just added this code in line 911-912 to verify if the new code is being fetched:

    console.log('container_offset', container_offset);
    console.log('target', target);

    Then I inspected the page (right click > Inspect) then go to Console (tab) to see if the code will log those values, and it didn’t which means that the browser is still fetching old avia.js file.
    I just cleared the browser cache and it works properly.
    This is what the code should output on desktop:

    container_offset 962      avia.js?ver=5.1.2:911
    target 962      avia.js?ver=5.1.2:912

    If this doesn’t show in your console, then old avia.js code is being fetched.

    Best regards,
    Nikko

    #1402762

    Great, thanks, I can see that it works now.
    I will now update the Enfold-version and see whether I can implement the changes by myself then.

    #1402771

    Hi Alex,

    You’re welcome :)
    Just let us know how it goes.

    Best regards,
    Nikko

    #1402772

    Okay, so here I am again, sorry.

    I updated ENFOLD to 5.5 and edited the avia.js as mentioned, but the changes that worked before won’t anymore.
    could you check again, please :/

    • This reply was modified 1 year, 1 month ago by xela.
    #1402786

    ——— it works now.
    I don’t know whether you changed sth. or the server “needed time” to get the new aria.js-file, I don’t know.
    I deleted all caches etc. but it did not work at first place, but: now it does…

    #1402791

    Hi Alex,

    I’m glad to hear that it worked now.
    There are two ways to see it (as I could think of at the moment).
    1. Go to Enfold > Performance > disable Javascript File Merging And Compression, open your website, right click and View Page Source. Then find avia.js and click on the link, it should show the whole code of avia.js and check the part where you added the code, and if it’s not added, it means it’s fetching old js file.

    2. Adding console.log to print the values in the console, then inspect your site and view the console and see if those values appear (just like what I did above).

    Best regards,
    Nikko

Viewing 16 posts - 1 through 16 (of 16 total)
  • You must be logged in to reply to this topic.