Forum Replies Created
-
Posts
-
Thank for the update Rikard.
I’m looking forward to the next release.
Keep up the good work!
Regards,
JefHello Ismael,
I installed the plugin and changed jQuery to the legacy version. That indeed fixed the problem and scrolling was back to normal.
I changed jQuery back to the standard version and this is what the log showed me after navigating on the homepage:jQuery.fn.click() event shorthand is deprecated
Thema: Enfold
https://(url edited).be/wordpress/wp-content/themes/enfold/js/avia.jsjQuery.expr[\’:\’] is deprecated; use jQuery.expr.pseudos
Thema: Enfold
https://(url edited).be/wordpress/wp-content/themes/enfold/js/avia.jsI’ve also (temporary) deactivated all plugins, but the same issue remained.
So it looks like an issue with WordPress 5.6 in combination with Enfold?
Kind regards,
JefHey Ismael,
Thank you for your answer. But even on a Windows PC in Firefox and Chrome there’s still a significant loss of speed when using the back to top button. I’ve tested this on a live site (see link in Private Content): this is a one page website where you can navigate between sections using the top menu. Going from the first (Home) to the next (Werking) section used to be very fast and fluid. Now it takes much longer and, as Octopus described, there’s nog ease-in and -out effect. Can you test this please?
Kind regards,
JefHey Victoria and HLL,
I had an issue that is perhaps related: my shrinking header would not go back to its original state after the first scroll. Happened on all pages and in every browser. Started right after I updated WordPress from 5.5 to 5.6. I had Enfold 4.5.6 installed and upgraded to the latest version 4.7.6.4 which solved my problem.
Kind regards,
Jef@Marcel: You have to make sure that you copy the changes exactly for all lines in red except 4903. I see it worked for others, but not everyone. In any case I hope we should get an update from Kriesi soon to fix this problem.
I found the cause and (temporary) solution to this problem.
See this thread: https://kriesi.at/support/topic/social-buttons-broken-with-wp-5-3-1-update/I found the cause and (temporary) solution to this problem.
See this thread: https://kriesi.at/support/topic/social-buttons-broken-with-wp-5-3-1-update/I found the cause and (temporary) solution to this problem.
See this thread: https://kriesi.at/support/topic/social-buttons-broken-with-wp-5-3-1-update/I found the cause and (temporary) solution to this problem.
See this thread: https://kriesi.at/support/topic/social-buttons-broken-with-wp-5-3-1-update/I found the cause and (temporary) solution to this problem.
See this thread: https://kriesi.at/support/topic/social-buttons-broken-with-wp-5-3-1-update/I found the cause and (temporary) solution to this problem.
See this thread: https://kriesi.at/support/topic/social-buttons-broken-with-wp-5-3-1-update/I found the cause and (temporary) solution to this problem.
See this thread: https://kriesi.at/support/topic/social-buttons-broken-with-wp-5-3-1-update/I found the cause and (temporary) solution to this problem.
See this thread: https://kriesi.at/support/topic/social-buttons-broken-with-wp-5-3-1-update/I found the cause and (temporary) solution to this problem.
See this thread: https://kriesi.at/support/topic/social-buttons-broken-with-wp-5-3-1-update/I found the cause and (temporary) solution to this problem (already posted in thread https://kriesi.at/support/topic/social-buttons-broken-with-wp-5-3-1-update/)
Changes made to the file ‘formatting.php’ in ‘wp-includes’ of the new WP 5.3.1 version are the cause.
I compared this file via diffchecker.com to the previous WP version and saw some differences to the bits concerning how links with ‘target’ and ‘rel’ should be rewritten. On the left is the new version, on the right the old one: https://www.diffchecker.com/6VKr6jb4Look for the changes starting on line 3149. The code in red (on the left) should be replaced with the code in green (on the right). Last line that should be changed is 3222. There are more changes in red starting on line 4903 but don’t touch these or your site will break!
After I made these changes, the social media icons magically reappeared after reloading.
Naturally this should be addressed in the next Enfold update, but for now this fix works (for me).OK, I found the cause and (temporary) solution!
Changes made to the file ‘formatting.php’ in ‘wp-includes’ of the new WP 5.3.1 version are the cause.
I compared this file via diffchecker.com to the previous WP version and saw some differences to the bits concerning how links with ‘target’ and ‘rel’ should be rewritten. On the left is the new version, on the right the old one: https://www.diffchecker.com/6VKr6jb4Look for the changes starting on line 3149. The code in red (on the left) should be replaced with the code in green (on the right). Last line that should be changed is 3222. There are more changes in red starting on line 4903 but don’t touch these or your site will break!
After I made these changes, the social media icons magically reappeared after reloading.
Naturally this should be addressed in the next Enfold update, but for now this fix works (for me).Hello,
Same problem here since the WP 5.3.1 update. Affects only Enfold version 4.6.3.1 (as far as I can check this).
I looked at the code of a site running 4.6.3.1 and compared it to a site running an older version.4.6.3.1
a target=”_blank” aria-label=”Link to Facebook” href=’https://***censored***’ aria-hidden=’true’ title=’Facebook’4.5.6
a target=”_blank” aria-label=”Link to Facebook” href=’https://***censored***’ aria-hidden=’true’ data-av_icon=’’ data-av_iconfont=’entypo-fontello’ title=’Facebook’This crucial part is missing in the newest version: data-av_icon=’’ data-av_iconfont=’entypo-fontello’
No clue so far why this happens.Hi,
I’ve got the exact same issue and it occurred right after the recent WordPress update (5.1). The extra code that has been added (class=”post-page-numbers’) is not broken Enfold code. It’s been added via the _wp_link_page function on line 931 of function-set-avia-frontend.php (found in enfold > framework > php). This function is called from post-template.php found in wp-includes. I compared post-template.php of the older WordPress version with the new one and there’s a difference:
line 911 (old): return '<a href="' . esc_url( $url ) . '">'; line 1035 (new): return '<a href="' . esc_url( $url ) . '" class="post-page-numbers">';Removing the extra code (class=”post-page-numbers’) in post-template.php solved the problem. But there’s probably another workaround that should be considered in a new Enfold update.
Regards,
Jef
