Forum Replies Created
-
Posts
-
This is a known issue using Enfold after updating to WordPress 5.3.1.
Luckily, the Kriesi Media development team at Enfold have addressed the issue. The solution to the problem will be included within the next Enfold theme release which is expected sometime after the holidays. In the meantime, they have provided us with a way to patch the issue and restore the social media icon font functionality.
The solution involves simply replacing an existing file, specifically “function-set-avia-frontend.php” located within your “wp-content/themes/enfold/framework/php/” directory.
You may obtain the updated “function-set-avia-frontend.php” file from the following KriesiMedia GitHub repository:
https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_6_3/framework/function-set-avia-frontend.phpThis is a known issue using Enfold after updating to WordPress 5.3.1.
Luckily, the Kriesi Media development team at Enfold have addressed the issue. The solution to the problem will be included within the next Enfold theme release which is expected sometime after the holidays. In the meantime, they have provided us with a way to patch the issue and restore the social media icon font functionality.
The solution involves simply replacing an existing file, specifically “function-set-avia-frontend.php” located within your “wp-content/themes/enfold/framework/php/” directory.
You may obtain the updated “function-set-avia-frontend.php” file from the following KriesiMedia GitHub repository:
https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_6_3/framework/function-set-avia-frontend.phpThis is a known issue using Enfold after updating to WordPress 5.3.1.
Luckily, the Kriesi Media development team at Enfold have addressed the issue. The solution to the problem will be included within the next Enfold theme release which is expected sometime after the holidays. In the meantime, they have provided us with a way to patch the issue and restore the social media icon font functionality.
The solution involves simply replacing an existing file, specifically “function-set-avia-frontend.php” located within your “wp-content/themes/enfold/framework/php/” directory.
You may obtain the updated “function-set-avia-frontend.php” file from the following KriesiMedia GitHub repository:
https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_6_3/framework/function-set-avia-frontend.phpSounds like a permissions issue. Have you tried replacing the file via FTP.
Don’t forget to make a backup. Hope this helps!
This is a known issue using Enfold after updating to WordPress 5.3.1.
Luckily, the Kriesi Media development team at Enfold have addressed the issue. The solution to the problem will be included within the next Enfold theme release which is expected sometime after the holidays. In the meantime, they have provided us with a way to patch the issue and restore the social media icon font functionality.
The solution involves simply replacing an existing file, specifically “function-set-avia-frontend.php” located within your “wp-content/themes/enfold/framework/php/” directory.
You may obtain the updated “function-set-avia-frontend.php” file from the following KriesiMedia GitHub repository:
https://github.com/KriesiMedia/enfold-library/blob/master/temp_fixes/Enfold_4_6_3/framework/function-set-avia-frontend.phpI agree with @env-jim
A quick patch to “mute” error messages on that preg_match_all function would be to add an “@” to the front of line 607.
I’ve tested it and my shortcodes appear to still be functioning. No more error notices upon preview and it doesn’t get reported in my error_log. NICE!
FILE:
/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/shortcode-parser.class.phpLINE 607
@preg_match_all( "/" . ShortcodeHelper::get_fake_pattern( false, $shortcodes ) . "/s", $text, $sc_found, PREG_OFFSET_CAPTURE );
Will try to get a developer to implement this or a better solution for future releases via github. Wish me luck!
Thank you, I know it works because I had removed the array values.
I have also submitted a pull request on github. Hope your team implements this change.
The issue is within the class-avia-gutenberg.php file located under the config-gutenberg directory. Again, with the most recent update someone accidentally changed it to ‘blank’ changing the default function of the ‘edit’ link on the frontend of the website.
See lines: 898 to 905 (line 902 is where blank meta is being called thus altering the default wordpress edit link action)
$menu = array(
‘id’ => ‘edit’,
‘title’ => $title,
‘href’ => $edit_url,
‘meta’ => array( ‘target’ => ‘blank’ )
);$wp_admin_bar->add_menu( $menu );
Thanks for your response. However, you are incorrect (I say that respectfully of course).
This is completely and only enfold theme related. The default WordPress action is to open in _SELF.
The recent enfold upgrade changed this to _BLANK.
Let me know if there is a hook to disable the enfold theme alteration of the frontend edit link.
Thank you.
SWEET! Thank you for that helpful information @Guenni007. You have restored and simplified my post/page list view within the backend!
Thanks for getting back to me Mike.
Upon my further inspection I discovered that it is an issue with the GravityForms plugin. The theme was suspected due to the recently applied update. Turns out it was just coincidence. I apologize for my error.
Posted the solution that I created on my personal website blog.
Sorry, but I cannot give admin access to the site. The issue is replicable on a default installation of WP and Enfold and as you can see others have a similar problem. I apologize for this inconvenience and thank you for your time and support.
Same issue on my sites. All had been updated for some time. Then recently received the following “Instagram has returned invalid data”
