-
Posts
-
Hello,
I wrote a post about the problem some time ago, here exactly https://kriesi.at/support/topic/my-avia-advanced-editor-wont-save-content-most-of-the-time/. Now I’m creating another one, I tried a lot of things and it still doesn’t work as it should.
What did I try?
- Deactivation of all plugins
- Checking and tidying up the htaccess file, now it’s totally like basic one
- Checking with child theme and without
- Trying default WordPress theme, without builder. It works then
- Clearing cache everywhere it’s possible
- Showing all errors by turning on errors handling in wp-config during all processes
- Checking logs
- Checking server and database space
I’m 99.99% sure it’s something with that advanced builder. Maybe it’s connected to JavaScript but I’m not sure. I did a lot of trial and error switching between the Editor view and the Shortcode view (I will show it in the video). Something strange is there definitely.
Hey inlinks,
Thank you for the inquiry.
We modified the code in the functions.php file a bit and used a different filter called avf_font_manager_load_font to disable the icon fonts.
add_filter('avf_font_manager_load_font', function($output) { return ''; }, 10, 1);Best regards,
IsmaelHi Ismael,
Thank you for your response.
I did some tests and unfortunately, it didn’t help. The problem still occurs.
I have renewed my support license, please try to prioritise this a bit, without creating new content I have a problem with managing my business.
Additional thing (maybe it will be helpful somehow), the server uses PHP version 8.0.28.
And second thing, we can show you one error we saw yesterday (but I think it resonates with your snippet of code above and as I wrote it didn’t help):
An error of type E_ERROR was caused in line 819 of the file /nas/content/live/inlinksprod/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-font-manager.php. Error message: Uncaught TypeError: asort(): Argument #1 ($array) must be of type array, null given in /nas/content/live/inlinksprod/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-font-manager.php:819 Stack trace: #0 /nas/content/live/inlinksprod/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-font-manager.php(819): asort(NULL) #1 /nas/content/live/inlinksprod/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-font-manager.php(792): avia_font_manager::set_new_backend('new', Array) #2 /nas/content/live/inlinksprod/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-font-manager.php(774): avia_font_manager::get_display_char('new', NULL) #3 /nas/content/live/inlinksprod/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-font-manager.php(925): avia_font_manager::backend_icon(Array) #4 /nas/content/live/inlinksprod/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons/buttons.php(536): av_backend_icon(Array) #5 /nas/content/live/inlinksprod/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-shortcode-template.php(1629): avia_sc_button->editor_element(Array) #6 /nas/content/live/inlinksprod/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/class-template-builder.php(2193): aviaShortcodeTemplate->prepare_editor_element(false, Array, true) #7 /nas/content/live/inlinksprod/wp-includes/class-wp-hook.php(308): AviaBuilder->js_template_editor_elements('') #8 /nas/content/live/inlinksprod/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters('', Array) #9 /nas/content/live/inlinksprod/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #10 /nas/content/live/inlinksprod/wp-includes/media-template.php(1555): do_action('print_media_tem...') #11 /nas/content/live/inlinksprod/wp-includes/class-wp-hook.php(308): wp_print_media_templates('') #12 /nas/content/live/inlinksprod/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters('', Array) #13 /nas/content/live/inlinksprod/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #14 /nas/content/live/inlinksprod/wp-admin/admin-footer.php(78): do_action('admin_footer', '') #15 /nas/content/live/inlinksprod/wp-admin/post.php(369): require_once('/nas/content/li...') #16 {main}Thank you so much in advance!
Best regards,
MaciejHi,
Thanks for your video, please note that when you save an Advanced Layout Builder page and then open it with the Block Editor the two versions of the page are not synced, this can cause errors with your page and we recommend that you don’t do this.
I have tried to recreate your error by creating a draft and previewing it and refreshing the draft page and editing it again but I couldn’t create the error on my test site, I also created a new “test draft” page on your site, and followed the same steps, except saving the page with the Block Editor, and had no issues.Best regards,
MikeHi Mike.
When you say: “when you save an Advanced Layout Builder page and then open it with the Block Editor the two versions of the page are not synced”, How do you suggest we open (or refresh) a page built in “Advanced Layout Builder”? I am looking at this video and I do not understand how you cannot recreate this error. At what point in the video, exactly, are we clicking on the wrong thing, because we now have four people in four different countries replicating this error on two hosting instances on two different continents. All content is stopped whilst we get to the bottom of the issue. If you are saying this is human error, not the theme, please show us more clearly we need to do differently to work with ALB.
(To clarify, the issue was the refresh moment at 1 minute into the video. This is before we went into the block editor.)
Thanks.
Hi,
What I am pointing out in your video (1:57) is when you switch your Advanced Layout Builder (ALB) page to a Block Editor page and then save:
this is not recommended and can cause frontend errors, there is no practical reason to do this, please inform your users to not do this.
Now (2:20) when you switch back from the saved Block Editor page to the ALB page, the two versions of the page are not synced.
I’m not sure why you want to save the ALB page in the Block Editor, but there is no practical reason to do this.
Nonetheless, I believe the core issue you are trying to demonstrate is that saving a Draft page and then Previewing the draft in another tab and refreshing the two tabs doesn’t show the same content. So I edited the draft test page from yesterday that I created which has never been saved as a Block Editor page in a video for you and linked it below.
I saved the draft and opened it in two tabs side-by-side:
and the content matched.
I edited the text again and reloaded both draft tabs:
and the content matched.
I even edited the draft a third time and previewed the refreshed page on the frontend in both tabs and then went back to the backend:
and again the content matched in both tabs:
So I was unable to reproduce the issue. As for your last comment that the first backend draft refresh was at 1:10 before the Block Editor was used, I would ask if you are sure that you have never saved this page with the Block Editor? I imagine that you have done this many times over many days in your testing.
I recommend creating a new page with the ALB and follow the steps in my video, and advise your users to not edit or save ALB pages with any other editor, as there is no practical reason to do so.Best regards,
Mike
- You must be logged in to reply to this topic.