Hi @Victoria,

Thank you but it didn’t work.

As I document in my entries above, this is a feature in your current Avia Builder. When you use the ADD/EDIT GALLERY feature in your Masonry Gallery, you can see the caption or add a caption. This caption DOES NOT display in the Lightbox. This perfectly documents how it was once working correctly, before someone changed it. Has this been noted and is there a plan to fix it? Is there a function.php patch?

Here is the CSS that governs this:
div .mfp-title {
line-height: 1.4em;
font-size: 13px;
}

Here is the section:
<div class=”mfp-bottom-bar”>
<div class=”mfp-title”>This is the title</div>
<div class=”mfp-counter”>1 / 5</div>
</div>

Thanks

Hello @ismael and @Basilis,

I have found addition supporting images on what is happening with the Image Galleries NOT displaying the Caption and instead of the Title of the images. As you will see in the new image, I added the CAPTIONS to the images using the input within your own Edit Gallery window. Then when I look at the Gallery on the front end, you do not see the CAPTION but instead, you get the TITLE.

So even in your own editing inside the Avia Gallery component, you provide for the Caption but display the Title.

This is huge in terms of using the Theme for past clients and future one too. What can we do?

Thanks,
Leyden

Here is the login. I didn’t use the plugin, I’ll remove it later.

I look forward to seeing what the issue is so we can fix all our websites.

Thanks

@Ismael and @gocreative, I’m happy to report it worked. We were also using outdated code to register the ALB in CPTs.

Thank you all for your help!

Hi all,

We are using outdated code as well. Here is what we are using:

function add_builder_to_posttype($metabox)
{
foreach($metabox as &$meta)
{
if($meta[‘id’] == ‘avia_builder’ || $meta[‘id’] == ‘layout’)
{
$meta[‘page’][] = ‘exhibition’;
$meta[‘page’][] = ‘YOUR CUSTOM POST NAME’;
$meta[‘page’][] = ‘YOUR CUSTOM POST NAME’;
}
}
return $metabox;
}

This is what you recommend in the link:

function avf_alb_supported_post_types_mod( array $supported_post_types )
{
$supported_post_types[] = ‘YOUR CUSTOM POST NAME’;
$supported_post_types[] = ‘YOUR CUSTOM POST NAME’;
return $supported_post_types;
}
add_filter(‘avf_alb_supported_post_types’, ‘avf_alb_supported_post_types_mod’, 10, 1);

@Ismael I will let you know if this fixes my issues. @gocreative glad this worked for you.

Thanks!

Nikko,

It could be that this is not affecting your test because you’re not using a CHILD THEME and your creating this content without any past use of the Avia Page Builder with CSS modifications in the child theme. It’s all fresh on Enfold 4.5.7.

I have just updated another client website to 4.5.7 from 4.5.2 and it went from working fine, to having layout issues. In the private content, I linked images you can look at. You will see Color Sections and Columns in the Avia Page Builder that look normally stacked in the admin but when you view the page, the Color Section and columns a fixed up.

Example: A GRAY Color Section with two 1/2 columns that contain videos. The gray was fine only showing in the Color SEction with the videos. After the update, the GRAY continues beyond the section and down the rest of the page.

Am I correct to assume that there have been significant changes to the Avia builder and the grid.css file to where I will need to strip whatever CSS adjustments I made to all my sites and start all over again?

Thanks

I don’t understand why he should start a new thread if his issue is just like mine.

Both of the columns sets below are the same, but they are rendering different. Here is what I see:
————————
Custom Post Type: This half column is rendering as a full column all the way across.
#top .flex_column_table {
display: table;
table-layout: fixed;
width: 100%;
}
#top .no_margin.av_one_half {
width: 50%;
}
————————
Page: This half column is rendering fine as a half column.
#top .flex_column_table {
display: table;
table-layout: fixed;
width: 100%;
}
#top .no_margin.av_one_half {
width: 50%;
}

Hi there,

Here are links to two of more than three websites with this issue. Again, it only seems to affect custom post types and not pages.

Thanks,
Leyden