Tagged: avada button link anchor bug
wvickParticipantJune 5, 2021 at 7:12 pmPost count: 10
After some further experimentation, I think this is a bug in Avada, or at least an undesirable side effect on how Avada buttons have been implemented.
In summary, it appears that internal or “page jump” anchor links on Avada buttons don’t work properly. They cause a page refresh, rather than a page scroll, and parameters are lost in the process.
My workaround for this is to use a HTML <button> tag with some custom CSS styling to make it look like an Avada button. Not exactly an elegant solution, but it’s a solution for now.
@ThemeFusion – I hope you’ll fix this issue. It’s easy to reproduce.
1) Create a page with a container including a button at the top. Make the button link point to “#end”.
2) Artificially lengthen the page, perhaps with a series of images + separators.
3) Finally, add a container with, say, a text block “This is the #end” and make the id “end”.
View the page, hit the button and you’ll see a reload+scroll rather than just a scroll.
Load the page with a random GET parameter on the URL “…/?hello=world”. Hit the button and see the parameter get lost due to the reload.
visuelleParticipantJune 14, 2021 at 11:29 amPost count: 1avadadukeParticipantSeptember 7, 2021 at 1:26 pmPost count: 1
I have the same issue when using anchor links in Avada buttons and images. Please resolve the bug.KimUitslagParticipantOctober 4, 2021 at 2:49 pmPost count: 1
I’ve got the same issue when using anchor links in Avada buttons.mulpha_webdevParticipantOctober 18, 2021 at 6:52 amPost count: 1andrew.f8ParticipantJanuary 14, 2022 at 1:56 pmPost count: 3
I had the same issue, however I solved it by url encoding the anchor and placing a “?” before it.
Original link “/wp-content/2022/01/file.pdf#page=31”, this ended up as “/#_page=31”
New link that works “/wp-content/2022/01/file.pdf?%23page%3D31”
Hope someone finds this useful.
- You must be logged in to reply to this topic.