-
Posts
-
Hi, I recently updated to WP 4.5. on several of my sites. When trying to create a new post or page, I see the default WP editor first. When I click on Advanced Layout Editor I still see the first part of the WP default editor with “Add title” and “start writing” and a + sign to add block, and below it all there is Avia Layout Builder. This can not be right. I tried on two different pages I administrate, on two different hosts, I turned of all plugins, and the results are exactly same. I use latest Enfold (4.7.4), WP 5.4 and PHP 7.3.17 on one site, and PHP 7.2.30 on the other.
Thank you for the tip, but installing a third-party plugin in order to make the theme work is not a sufficient solution for using Enfold.
Hi all,
Please have a look at the following thread:
https://kriesi.at/support/topic/shortcodes-window-after-updating-to-wordpress-5-4/If you need further assistance please let us know.
Best regards,
VictoriaI hate to be a bumper, but the link above from @victoria leads to a 404 page and I still don’t know how to fix this issue. I’m on a deadline and can’t do what I need to without having access to the Advanced Layout Editor. Please advise. Thank you!
Hi,
This link works just fine: https://kriesi.at/support/topic/shortcodes-window-after-updating-to-wordpress-5-4/. I can copy the content for you here as well:
If you are seeing an extra shortcode window before the regular Layout Builder window then please try to activate the Classic Editor in the main page of the theme options as a temporary fix.
———————————————————
If you are having problems with scrolling down below the fold when dragging an element and the Block Editor is active, then please try adding this to your functions.php file:
function avia_block_editor_scrolling_fix() { ?> <style> body.block-editor-page.avia-advanced-editor-enabled .block-editor-editor-skeleton__content{ position: relative !important; } </style> <?php } add_action('init', 'avia_block_editor_scrolling_fix');This fix will be added in the next update of the theme.
Best regards,
RikardDear Rikard, regarding your
“This link works just fine”
Some would find it very arrogant and unfriendly. Please, you can not think that all of us claimed “just for fun” that the link is not working, as we do not have anything better to do. It DID NOT work for several days, and it is confirmed by many users.
Now, I can see that you managed to fix this, whatever it was, and that the link work again – that is great and thank you very much for that, and thank you for copying the content here as well.I had the problem with the extra shortcode box when the bug first showed up, so I switched to classic editor and things were fine…until 2 days ago when I noticed that the document settings to the right had disappeared — everything after “featured image”.
Not sure if the download I just got from Envato and reinstalled is the newest thing, but I did it anyway. I still had the same result. I switched back to block editor and now I have my settings on the right, but the shortcode box is also back.
And that link definitely took me to a 404 for 2 days.
Hi traypup,
If you need further help then please open a new thread and include WordPress admin login details in private so that we can have a closer look at your site.
Best regards,
RikardThanks, Rikard. I just decided that I’d live with the shortcode box until there’s a patch. I have my settings back on the right, so that’s more important right now. If I get aggravated with the shortcode box again, I’ll deal with it then. :) :) :)
Hi traypup,
Ok, please let us know if you need more help or this is resolved.
Best regards,
VictoriaHi, this is not resolved at all, but what we hear is that you will fix this in the next update. In the meantime I solved this temporarily by installing a plug in that turns the new WP block editor off, but obviously that is not a solution.
So if we rephrase your question from “is this solved” to “is there anything we can do now, or should we close the ticket”, the answer is – yes, it seems that you can close it.
Thank you!
- You must be logged in to reply to this topic.