here’s a workaround in the meantime…
(it’s basically a shortcode that runs a shortcode that pulls in content from another CPT post with Builder content)

1) add a CPT eg “component”

2) install the plugin Custom Content Shortcodes (CCS) https://en-gb.wordpress.org/plugins/custom-content-shortcode/

3) enable the Meta Shortcodes option in CCS settings

4) create a CCS Shortcode called “component” and add this code into the editor [content type=component name={NAME}]
(this uses CCS content function to pull content/fields from another post)

5) add this code to your functions.php to enable the Avia Builder in your CPT’s content editor

// add Avia Builder to CPTs
function avf_alb_supported_post_types_mod( array $supported_post_types )
{
  $supported_post_types[] = 'component';
  return $supported_post_types;
}
add_filter('avf_alb_supported_post_types', 'avf_alb_supported_post_types_mod', 10, 1);

you can now add this to HTML/text blocks etc in your pages, to pull in the content field from your CPT (ie our builder content)
[component name="my-component"]

(You could of course just use [content type=component name="my-component"] but I’ve added the proxy shortcode to keep it a little bit more readable)

thanks that works for me!

it would appear to be part of config-templatebuilder\avia-shortcodes\postslider.php that the Blog Posts actually renders the item with, not blog.php.
$output .= $thumbnail ? "<a href='{$link}' data-rel='slide-".avia_post_slider::$slide."' class='slide-image' title=''>{$thumbnail}</a>" : '';

it’s the $thumbnail part we need to change in this instance to remove the alt

the correct method seems to be passing false to the alt parameter in the third argument
$thumbnail = get_the_post_thumbnail( $the_id, $image_size, array( 'alt' => false ));

we don’t really want to edit core theme files and I imagine this solution would normally be preferable, using a regex

add_filter( 'post_thumbnail_html', 'remove_thumbnail_alt', 10, 5 );
function remove_thumbnail_alt( $html, $post_id, $post_thumbnail_id, $size, $attr ) {
    $html = preg_replace( '/(alt)=\"(.*?)\"\s/', "", $html );
    return $html;
}

however I’m not sure we can run this function for only the blog posts entries

if we need to add a conditional to the core postslider.php file output to remove the alt if a title is available in the pod text, we need to make it a conditional on these render types
title, excerpt_read_more, title_read_more

therefore for now I’ve added a patch to postslider.php

// patch: remove alt on image if there is a title output on the pod
// $thumbnail  = get_the_post_thumbnail( $the_id, $image_size );
$hasTitle = in_array($contents, ['title', 'excerpt', 'excerpt_read_more', 'title_read_more']);
$thumbnail  = get_the_post_thumbnail( $the_id, $image_size, ($hasTitle ? array('alt' => false) : null));

again we’d rather not edit core theme files, but I see no other solution really using filters/hooks

thanks, I did find that av_postcontent shortcode actually in the code base then try get it into our own wpml_config.xml but I don’t believe WPML supports relationship fields (I wanted to have a dropdown with the list of translated posts in it)

I’ll see if I can get it to bring up the shortcode value like this
https://wpml.org/forums/topic/i-need-to-translate-specific-shortcode-attributes

if i can put the relevant “Post Content” page,id in the link value on the translation it might stop it being overwritten when going through the translation process. (theoretical so far!)

thanks
J

Ah thanks @guenni007. This is on version 4.4.1, so upgrading may solve it. Thanks for the info

I’ll dig around the settings to see if there’s something specific in our setup regarding mobile menu

Thanks
J

note the second one is nested under header_main_alternate

this is the one in the source code
<div id='header_main_alternate' class='container_wrap'><div class='container'><nav class='main_menu' data-selectname='Select a page' role="navigation" itemscope="itemscope" itemtype="https://schema.org/SiteNavigationElement" ><div class="avia-menu av-main-nav-wrap"><ul id="avia-menu" class="menu av-main-nav">

the extra one being generated by js is getting placed below <div id='header_main'.....

• This reply was modified 4 years, 11 months ago by codemonkeynorth.

Hi,

yes sorry I think in this case you are right. It was a coincidence that 4.4 and 4.6 were (not) working differently in that the nginx configs on the servers were also different.

I read you’d changed the 404 handling in 4.6 from another issue thread, which is why I thought there was an issue at the Enfold end.

note to anyone coming to this thread though: we had to set an nginx rule for static files pointing to our custom 404 (eg mysite.com/this-doesnt-exist.pdf), and then let WP/Enfold custom 404 setting deal with dynamic pages

thanks
J