Thanks Ismael, That seems to have fixed it.

Much appreciated,

thanks again, but unfortunately still jumping about!

below is some text from another post on the forum, which i have implemented, and i think it may be working, however the code only works on one specific toogle-id. How do i edit the code to apply to all toggle-ids on the page?

The only solution I could think of is to remove the ID for the toggle, which matches the “fake ID” in the address bar. Since you are not linking to it directly it should not be an issue.
So as a test I added this to your functions.php

function custom_script(){
  ?>
  <script>
 jQuery(window).load(function(){
  jQuery('.single_toggle p[data-fake-id="#toggle-id-5"] + .toggle_wrap').removeAttr('id');
  });
  </script>
<?php
}
add_action('wp_footer', 'custom_script');

this removes the ID from the one button…

Hey Ismael,

I have removed that line, disabled the compression, emptied the cache and deactivated my cache plugin, but the accordions are still jumping about in chrome.

Any other ideas?

the same tabs.js file does have a comment on line 124 saying:

//check if tab title is in viewport. if not scroll up

is there any lines within this section I should delete as well? I have noticed that sometimes the browser does jump up much higher than other times, so it is slightly more random than always acting like an anchor tag.

Hi Rikard,

I have tested opening the accordion elements on various devices in chrome, and they all seem to cause the same issue. So to replicate the problem I recommend refreshing the page then keep clicking to open and close different accordions and i’m sure some ( about 75% jump on when I do this) will jump up to the top of the page.

Below are some other recent posts on your forum which sound like the same issue, and I feel that mike’s solution to remove the ID for the toggle should work, but I believe his php code is specific to that site. I am unsure how to edit the toggle-id-# within his code to work on all accordions within my site?

I can always save a screen recording if you feel it necessary?

Thank you

Ismael,

I had already selected the classic editor in the theme options. I also previously used the classic editor plugin, but thought the whole point of updating enfold and having this editor selection built into the theme was that I could remove the additional plugin.

So as it stands, regardless of which editor is selected in the enfold theme options, the original ‘line 529’ error appears because the url directed to is:
http://sitename/wp-admin/post.php?post=1234&action=edit

However, if the classic editor is selected in the theme options and I view the page first then use the ‘edit page’ link within the wordpress admin header bar, then the advanced layout editor does load, as the url directed to is:
http://sitename/wp-admin/post.php?post=1234&action=edit&classic-editor=1

However, my Client is not happy with this, so I need to understand what the ‘line 529’ error is? To be honest, I could just revert to an older version of enfold and re activate the classic editor plugin, but that seems a bit backwards to me.

If I use the classic editor plugin as well as selecting the classic editor in the theme options, then the correct url is used when clicking a page or post directly from the dashboard, but should the block editor ever be needed in the future, the original error would prevent it from ever being an option.

Any other ideas why line 529 could be causing me this conflict? Or do I revert to the older version of enfold?

Hi Ismael,

I replaced the original class-avia-gutenberg.php file but the error still occurs. The original thread you linked me to did mentioned the error warning was line 329, however my error says line 529 – so it may be a different error?

Any other ideas?

Now fixed, the code i had copied from an earlier thread didn’t correctly reference the slide query hook. Maybe it was from an older version of enfold, but I have changed it to:

avia_post_slide_query

and it seems to work as expected.

Thanks and please close this question.

please close it thanks.

Hey Ismael,
Thanks for your suggestion, I did try this but it did not seem to affect anything. Plus, if it did work, then the result would likely not be what I am after, as the left and right columns would not be correctly aligned. Please let me know if you have any other thoughts?

Hi Basilis, here is the code that was added to my css to make the 3 columns stay as two on mobile devices:

.page-id-21 .av_one_third {
display:inline-block !important; 
}
@media only screen and (max-width: 767px) {
.responsive #top #teamgrid .container .av-content-small, .responsive #top #wrap_all #teamgrid .flex_column, .responsive #top #wrap_all #teamgrid .av-flex-cells .no_margin {
    width: 50%;
    float: left;
    clear: none;
}}

Thanks,

Thanks Mike, worked a treat.

Thanks for looking into it Nikko, I guess I will just keep all the pdf links in the portfolio item post type for now.

It was uploaded to google drive, so not sure why the link didn’t work. But here’s a go with dropbox: