Forum Replies Created
-
Posts
-
The correct CSS to fix the issue and show the shadow is:
.av-styling-circle .avia-image-container-inner, .av-styling-circle .avia_image, .av-styling-circle .av-image-caption-overlay, .av-styling-circle div.av-caption-image-overlay-bg { overflow: revert !important; }I did some more testing, and it only happens on the Image element when the Circle is chosen, and then Shadow is set to Outside, it happens. If there is no Shadow set, it is not an issue.
This is across many sites, not just one. I have CSS/JS merging and compression disabled, and I’ve cleared the page cache, the issue still exists.
Sorry my license seems to have expired, I will have to figure out how to revalidate.Chiming in… You need to change the background color of the Socket, which is different from the Footer area. The Socket is the bar under the Footer. Look at the Preview area above the color setting area at Enfold > General Styling > Footer (tab) and Enfold > General Styling > Socket (tab).
I updated to Enfold v4.7.5 and the problem was still there, just to confirm.
This file you linked to with the conditional check fixes the problem, the Customizer works without Fatal error now. Thank you.
Just chiming in, this may help, regarding page changes not saving:
Works properly when Block Editor is selected, and Classic Editor disabled. The Classic Editor plugin was not installed before I reported the issue.
So it’s how Enfold is turning off Gutenberg which produces the error, different from how the Classic Editor plugin is doing it, which produces no error. And only when visiting the Customize area and only when Page Caching or Gravatar caching is enabled, which is very weird. :-)
Ah I have realized it’s Enfold’s option of choosing Classic Editor or Gutenberg in the theme options causing the issue… if I use the Classic Editor plugin, the error goes away!
I hope Enfold is updated accordingly, thank you!
Hmm, I’ve got the error on both 7.3 and 7.4. I’ve dropped that site down to 7.3, same error.
I realized it’s either Gravatar caching or Page caching, cause the error. If I turn off both, error goes away. If I enable one or the other or both, error is back.
Anyways, we’ve replicated the error across sites with and without child theme, error exists… can we get it fixed in Enfold, since it is in the enfold/config-gutenberg/class-avia-gutenberg.php file?
It’s weird because Classic editor is enabled, and so Uncaught Error: Call to undefined function gutenberg_can_edit_post_type() makes sense, there is no gutenberg function to call then? But why is it still trying to call it from that file, that should be disabled?
Hmm… ok, I will look into that. I have other Enfold sites that do not use Child theme at all, same issue and error. I will create an Admin link for you and send you the same Customize.php error URL for that site.
I’ll include login info in the Private Content area of this post so you can see the issue in action on a specific page that refuses to update unless I enable my workaround code.
Also note, I’ve also enabled Debug mode, and tried No Parsing, check shortcodes, and Auto-repair mode, none of them show any errors that I see or make a difference.
