I’m not actually doing that myself, a company is handling the implementation for us, and here’s what they wrote, after using your [av_button] custom_class feature:

The problem is, we want to use Google Tag Manager to track clicks on the buttons, and the classes are applied to the DIV element, not on the A tag. And GTM don’t recognize the selector when the class isn’t on the button(link) itself.

• This reply was modified 7 years, 2 months ago by champlainconted.

You have to log in first. See private content.

Ok, please try again.

• This reply was modified 7 years, 4 months ago by champlainconted.

Problem solved. Thank you, Victoria!

Yes, if you just click on this link, you’ll get a 404. It’s a page that’s only visible to admins. Please see the credentials in the Private Content section. Once logged in, this URL will no longer return a 404 – you’ll see the page. (In the previous reply I included a YouTube video proving that I reproduced the bug.)
http://champlainconted.com/kriesiat/

You’ll need to use the EDIT url directly to edit it, so I’ve included that too (the bug prevents access to the toolbar).

• This reply was modified 7 years, 6 months ago by champlainconted. Reason: more info

Please see the first post in this thread (blockquoted below), where I did those tests preemptively, knowing I’d be asked to do that. At the time, everything was fully up to date, WordPress, Enfold, plugins, etc. I even disabled plugins, stopped using a child theme, etc, etc. So unless something suddenly changed in WordPress 4.7.1 or 4.7.2 that fixed this, or Enfold changed in some way to fix this, I’m not sure why re-testing would heed different results. Plugins were eliminated and so was the child theme, so those were innocent as per my tests. Though, it is odd that you can’t seem to reproduce it. Anyway. I’ll see if I can revisit this in the future – workload is too high right now and I am able to circumvent this issue by avoiding massive page titles.

In any case, thanks for looking into this.

We’re running WordPress 4.7 and the latest versions of all our plugins.

Here’s what I already tried:

• Deactivating all plugins
• Updating to the latest version of Enfold
• Switching from using an Enfold Child Theme to using a pure Enfold parent theme
• Deleting W3 Total Cache and all traces of it
• Looking for errors via WP_DEBUG_LOG – nothing seen
• Looking for errors via Firebug/Chrome Developer tools – nothing visible

The problem is still reproducible despite this.

Sure, see private content.

Ok, we’ll just wait for you guys to offer your own support license feature, and will buy into that. If there’s some sort of an advantage for us to buy ThemeForest’s in anticipation of that, do let us know, though. (Aka if you will offer a rebate for those that already have ThemeForest licenses.)

Unfortunately, neither of those snippets fix the problem. I tried in my child theme’s style.css, and also in the quick css tab as you suggested, and, each time, I wiped the cache prior to refreshing. Still no luck.

To be clear: the behavior I expect to see is the images resizing along with the window, so they’re always next to the text, not under it like in the screenshot.

Hey, I didn’t try this, but am satisfied with the response/service. You can close the ticket, I’ll refer to it later when I get back around to this task.

Thanks,

Matt

So, it seems I managed to resolve this, thanks for the assistance! I’ll try restore the shrink-to-custom-size modification later on, higher priority tasks right now.

Thanks,

Matt

Yes, that fixes it… my modification to “avia.js” in the child theme is actually fairly minor. I just changed “el_height/2” to “el_height/1.25” in two locations. Any idea what might be causing a JavaScript error if my child theme isn’t actually messing up the JavaScript?

Here’s my functions.php, but it seems innocent enough. Maybe that 100 needs to change to something else? Perhaps Gravity Forms’ JS should load after or before or something?

add_theme_support('avia_template_builder_custom_css');

add_action('avia_builder_mode', "builder_set_debug");
function builder_set_debug()
{
	return "debug";
}

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 );

Sounds good. Can I stick it in my “enfold-child” theme using the same structure? So enfold-child/js/avia.js? I ask because I tried and for some reason it doesn’t seem to be working.

Thanks,

Matt

Ok, so I added this to my functions.php, child theme:

add_action('avia_builder_mode', "builder_set_debug");
function builder_set_debug()
{
	return "debug";
}

It says Avia, is that OK?

As for creating an element, do I do it like this? Create a custom shortcode? Or is there a simpler way?

Add new or replace Advanced Layout Builder elements from Child Theme

• This reply was modified 9 years, 9 months ago by champlainconted.