Searched for the same issue on the forum but didn’t really get an answer.
I’m trying to make a button link to a certain section of a different page but it only takes me to the page and does not scroll down to the anchored id.
I’ve worked on other Bricks sites before and the external page anchor links work fine. That was Bricks 1.53 and the version I’m using for this site is Bricks 1.7.1.
Looks like it works when disabling motion.page. Thanks for the suggestion!
Is there a way to make the functionality work even if motion.page is enabled? I’m curious why motion.page disables the use of external page anchor links. Anchor links on the same page still work fine.
I can’t answer that, because I don’t have any experience with motion.page. Please reach out to their support and get back to me when you get an answer.
I’m experiencing the same issue, and in my case motion.page seems to be causing the problem as well. I contacted motion.page’s support. I’ll update here if I get an answer
For me also it was not working until I rename the element ID
E.g. Renamed the bricks generated name #brxe-bekvzm to #application. Then on the element to click choose Link type: External URL and URL:#application.
Now everything is working
Hello! thanks for the answer. I have only one problem, when I press the button it takes me to the section automatically, that is, it does not scroll to get there. How could I fix it or what am I doing wrong?
Hey team! Thanks to this post i was able to create the content link inside of the page, but the solution isn’t working for linking from an external page
I have a dynamic slider on one page where the slides links to the anchor of another page. When hovering over the link, its generated correctly
When clicking the link, it shows in the url bar for a moment, but then refreshes to the parent page
The content I’m linking to is also in a loop. The id’s are set to be {post_slug} so that it dynamically creates the content anchor.
If the page loads and I place the same link in the url bar again, it directs as expected.
I’m assuming it’s acting this way, because when the page first loads, that content may not be on the page yet so it doesn’t have anywhere to link to.
Could someone please confirm if this is the case and also suggest if there’s a way around that so it’ll allow more time before going back to the parent page link?
I figured it out earlier today. There was a conflict with NextBrick’s Page Transitions enabled. I wasn’t using that feature so when I disabled it, everything worked as expected. Thanks for the reply though!