TinyMCE Missing Essential Buttons in Advanced Layout Builder Text Blocks

Connected with the “false” editor is the following behaviour: When I open a page for editing and click on an existing text block, this “false” editor opens, I change some text, then click on the Save button – the changes are not saved. When I click on this text block again, the editor opens without any text at all. After I reload that page for editing (ignoring the WP warning that there are changes), click on that text block, change the text, then save the changes they are saved. Strange, isn’t it?
Stephan

Hi Victoria,

OS: Windows 10 Pro, version 1709, build 16299.371
Browser: Firefox Quantum 59.0.3 (64-Bit) / Chrome 66.0.3359.139 (64-Bit)

Text block editor looks like this:

Thanks,
Stephan

Hi Ismael,

There are no such extensions installed. You can check yourself using the credentials I provided in my first post on April 27, 2018.

Thanks,
Stephan

Hi Basilis,

I’m somewhat disappointed by the quality and professionality of the Kriesi support. Meanwhile I found out by myself what the cause of the editor problem was. Should have been easy for you as well if you just took the time and analysed the script error messages thrown on pageload in the WP backend I gave you credentials for.

Here is what I found out: I use a child theme and overrided js/avia.js (to alter the ajax search functionality). In my function.php I activated this customized version of avia.js by

function wp_change_aviajs() {
   wp_dequeue_script( 'avia-default' );
   wp_enqueue_script( 'avia-default-child', get_stylesheet_directory_uri().'/js/avia.js', array('jquery'), 2, true );
}
add_action( 'wp_print_scripts', 'wp_change_aviajs', 100 );

Now with the latest update of the theme came a new avia.js and the old wasn’t compatible anymore.

I replaced the js/avia.js in the child directory by the (unaltered) new version, but that threw an exception: “TypeError: $.avia_utilities.supports is not a function”. I had to comment out the function wp_change_aviajs() in my function.php to get rid of this.

Now the text block editor works again, but how can I override avia,js in my child theme to customize it?

Thanks,
Stephan

• This reply was modified 6 years, 7 months ago by Stephan_H. Reason: corrected a typo

Hi Victoria,

This is off topic, but following this hint I just commented out line 56 (new $.AviaAjaxSearch({scope:'#header'});). In the latest avia.js this is to be found in line 35.

Following another hint I added the function wp_change_aviajs() to my function.php in order to use the altered avia.js file.

However, if I copy the unaltered (latest version of) avia.js into the child theme folder (js subdir) and leave the function wp_change_aviajs() in my functions.php (also in the child theme folder) then the WP backend throws an exception error (“TypeError: $.avia_utilities.supports is not a function”) and stops at line 513 in avia.js. It’s the avia.js in the child theme folder, identical with the avia.js in the theme folder.

If I comment out the function wp_change_aviajs() and the add_action command no error is thrown. But then, the child theme copy of avia.js isn’t used at all. How can a customized avia.js be used?

Should I start a new topic about this?

Original problem that lead to customize avia.js is: How can I deactivate the Ajax search?

Interesting additional issue now: Why does a copy of avia.js not work in the child theme dir?

Thanks,
Stephan

• This reply was modified 6 years, 7 months ago by Stephan_H.

Hi Victoria,

I followed your advice but the error persists.

I placed the following files in my child theme folder:
\themes\enfold-child\functions.php
\themes\enfold-child\js\avia.js
\themes\enfold-child\js\shortcodes.js

In functions.php I have the following function:

function wp_change_aviajs() {
   wp_dequeue_script( 'avia-default' );
   wp_enqueue_script( 'avia-default-child', get_stylesheet_directory_uri().'/js/avia.js', array('jquery'), 2, true );
}
add_action( 'wp_print_scripts', 'wp_change_aviajs', 100 ); 

When I log in to my WP backend, I get the error as described above. See screenshot of the backend in the private content section of this reply.

Thanks,
Stephan

Hi Victoria,

Yes, that fixes the problem with the “TypeError: $.avia_utilities.supports is not a function”. Thanks a lot!

But now: How can I disable the ajax search feature? The search field that shows up when clicked on the magnifier icon in the menu bar should just receive keyword(s) and do nothing until Enter is pressed or the magnifier icon to the right of it is clicked.

The tip to comment out the line “new $.AviaAjaxSearch({scope:'#header, .avia_search_element'});” (line 35 in avia.js) doesn’t work.

Thanks,
Stephan

Hi Ismael,

Great, that works! :-) Thank you very much!

Cheers,
Stephan