Yeah…this beta release broke my site.
<b>Fatal error</b>: Uncaught Error: Call to undefined function jevelin_allowed_html() in /home/primaryi/public_html/wp-content/themes/jevelin/framework-customizations/extensions/shortcodes/shortcodes/section/options.php:26 Stack trace: #0 /home/primaryi/public_html/wp-content/plugins/unyson/framework/helpers/general.php(770): require() #1 /home/primaryi/public_html/wp-content/plugins/unyson/framework/extensions/shortcodes/includes/class-fw-shortcode.php(129): fw_get_variables_from_file(‘/home/primaryi/…’, Array) #2 /home/primaryi/public_html/wp-content/plugins/unyson/framework/extensions/shortcodes/extensions/page-builder/includes/page-builder/includes/item-types/class-page-builder-item.php(175): FW_Shortcode->get_options() #3 /home/primaryi/public_html/wp-content/plugins/unyson/framework/extensions/builder/includes/option-types/builder/extends/class-fw-option-type-builder-item.php(96): Page_Builder_Item->_storage_load(Array, Array) #4 /home/primaryi/public_html/wp-content/plugins/unyson/framework/extensions/shortcodes/extensi in <b>/home/primaryi/public_html/wp-content/themes/jevelin/framework-customizations/extensions/shortcodes/shortcodes/section/options.php</b> on line <b>26</b>
There is a syntax error being thrown that appears to be related to the jQuery update in WordPress 5.5.
Uncaught Error: Syntax error, unrecognized expression: nav.sh-header-mobile-dropdown li.menu-item > a[href*=#]
I am hoping they rectify this with the next theme update. And hopefully soon.
There hasn’t been a solution proposed. This is a flaw in the theme that has not been addressed. Shufflehound’s support suggestion above your question is just a workaround and not a solution.
I solved my issue by adding CSS to my child theme as well.
I haven’t used WPbakery yet, so I don’t have experience trying to solve it in there.
<div class=”styles-section-title styles-selector”></div>
Thank you, but my question was more specific than that. I know how to change general urls in the database, but the background-images created by Jevelin are handled differently.
I believe I have found them in the postmeta table.
Can I just get a direct, specific answer in regards to the way Jevelin stores the background image info in the database? Then I can solve this because the posts above don’t give me that specific help.
I have footer widgets turned on and have selected 4 columns, but I do not get the multiple footer widget areas to show in the Widgets page. I only have one that says “Footer Widgets”. I have turned it off and on, and selected different column settings, but nothing creates the different footer widget sections. What am I doing wrong?