-
-
I’m trying to create just a simple page to show FAQ’s, but the automatic scrolling that is programmed into this theme is a major problem. It scrolls too far down, and there are no settings for this. Here’s my page.
https://mariposa.svsimagery.com/faq/
If you click on any FAQ items in the top half of the page, you’ll see that it scrolls past what you’re trying to read.
What’s the trick to fixing this?
-
I’ve been waiting a couple of days for some assistance with this. I would really appreciate some support.
-
Hello,
Sorry for the late response. Please edit the file ‘tower/js/main.js’.
Find the lines:
function codelessOnePageContent(){ "use strict"; $('.composer_content').onePageNav({ currentClass: 'current-menu-item', changeHash: false, scrollSpeed: 750, scrollThreshold: 0.5, }); }
and delete theme or comment they out.
Best regards!
-
Thank you for the response. Unfortunately, I just now saw it after manually checking my posts. I didn’t receive an email update.
This is something that should only be done in the child theme, correct?
-
I’ve installed the child theme so I can create a new version of the <span style=”color: #393d40; font-family: ‘Open Sans’, ‘Helvetica Neue’, Helvetica, Arial, sans-serif; font-size: 14px; line-height: 22px;”>main.js with your code fix, but when I switch over to the child theme all my sidebar widgets are lost. How do I get all of my sidebars and widgets to work in the child theme without recreating it all?</span>
I’m assuming I have to use a child theme to do these code changes otherwise, they’ll get wiped out in the next theme update, correct?
-
Hello,
Not all of the changes suggested will be wiped out from the next theme update. Some changes, like the code in the reply above, will be added in the next theme update so that the issue solved from it will not be lost. As for the css code, if you have added it in your custom css box, that will not be affected by any theme update.
Sorry but you have to add the sidebar widgets once again at your child theme. There is no option to import them.
Let us know.Best regards!
-
This problem has been solved with the update of version 1.7.
Thank you for the quick fix!
-
You must be logged in to reply to this topic.