Forum Replies Created

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • wvick
    Participant
    Post count: 10

    RESOLVED

    I resolved this problem by disabling the “Find Posts Using Attachment” (v1.0) plug-in. There doesn’t seem to be any other reports of this nature for this useful plug-in, so it’s perhaps an incompatibility rather than an outright bug. I hope this is useful for anyone else having the same issue.

    wvick
    Participant
    Post count: 10

    I occasionally (today!) get this too. 🙁

    It’s really annoying!

    /W

    wvick
    Participant
    Post 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.

    Simple and <button> tags work as expected.

    /W

    wvick
    Participant
    Post count: 10

    Hi Mark,

    I followed your advice and copied/modified the CSS found on the reference site. I even went further by implementing the display of the footer tab on a shortcode, which would only be populated when the current pages was not the “Contact Us” page. So, when you’re on the “Contact Us” page, you don’t see the tab as it would be self referencing and somewhat pointless. You can see the final result on https://www.europa.uk.com

    I think it’s a neat addition to the CTAs on any website, especially when it sits so neatly next to the “toTop” tab.

    Many thanks for your advice.

    /W

    wvick
    Participant
    Post count: 10

    I agree that Avada has got way too fat and slow. I’ll add my vote to trading new features for a period dedicated to putting the theme on a diet in order to improve performance. Google now places greater emphasis on faster sites so it’s now critical that Theme Fusion address this problem. /W

    wvick
    Participant
    Post count: 10

    Hi Jos,

    Have you made the container you wish to reuse “global”? If so, there will be a single representation of it. If you change this container in the library or on any page, it will change on any page that also uses it. If you have not checked “global”, you’ll get a copy, which could be the reason your pages are not updating. Global containers have a small globe icon in the top-right.

    Alternatively, could it be a caching issue?

    Regards,
    Warren

    wvick
    Participant
    Post count: 10

    Back in September, I reported to both Theme Fusion and Yoast the fact that their popular products don’t work well together. Yoast doesn’t have sufficient access to Avada-based content and comes up with a number of incorrect SEO analysis points which can sometimes make a difference between a good (green) and OK (yellow) SEO assessment. It’s quite distracting to mentally ignore those every time I edit a page. Yoast claim that Theme Fusion is not using approved ways to allow access to the processed content. Personally, I think both parties need to work together to resolve this. I’ve already made this suggestion in multiple support tickets.

    I sent a follow-up e-mail to Theme Fusion this week and got a response saying that they’re “in progress” on this but there’s a lot of work to do and they don’t have a timeline. All during this time, there’s a page on the Avada website that claims “Avada Is 100% SEO Ready”. I’ve challenged this since it’s incorrect or, at best, misleading, but they’ve not changed it. Or, perhaps in somebody’s world “ready” doesn’t mean “compatible”?

    Avada is a top WordPress theme, Yoast SEO is a top plug-in. What do we have to do to get them working together correctly? Love the products, frustrated with the companies!

    /Warren

Viewing 7 posts - 1 through 7 (of 7 total)