Hi,

Just one details, the categories still appear below the titles,

Did you remove the avf_masonry_entry_content filter from the functions.php file? You have to remove the code because it inserts the categories below the title.

Hmm I seem to have lost it again, I made some edits to the css and

We are not seeing the categories in the image container anymore. Did you revert the changes in the class-avia-masonry.php file?

Best regards,
Ismael

Hey Jak73,

Thank you for the inquiry.

To make it a bit simple, the width of the image should be close to that of the standard screen resolutions (1920x1080px, 1600x900px), and should have an aspect ratio of 16:9. The image should also exceed the height of the color section to get that subtle image delay when scrolling the document. But please note that the parallax script in the theme will handle the image resizing automatically based on the size of the color section, so you don’t really have to worry about the exact image size.

You can check the image in the private field to get an idea on how big the image should be in a parallax color section. The image is used in one of the demo with the parallax effect. And in case you didn’t know, you can also use the Layer Slider to create a parallax effect.

Best regards,
Ismael

Hey marladesign,

Thank you for the inquiry.

There is no option for this by default but we can add a script to move the sidebar above the content on mobile view. Please try this code in the functions.php file.

function ava_custom_script_mod(){
  ?>
  <script>
        (function($) {
			// move the product category sidebar above the content on mobile view
			function av_move_prodcat_sidebar() {
				var is_mobile = false;
				var is_archive = $("body").is(".tax-product_cat");
				if(/Android|webOS|iPhone|iPad|iPod|BlackBerry|IEMobile|Opera Mini/i.test(navigator.userAgent) ) {
					is_mobile = true;
				}
				
				if( is_archive && is_mobile ) {
					$(".sidebar").prependTo(".template-shop.content");
				}
			}

			$(document).ready(function() {
				av_move_prodcat_sidebar();
			});
		})(jQuery);
  </script>
  <?php
}
add_action('wp_footer', 'ava_custom_script_mod');

Then add this code in the Quick CSS field to make sure that the sidebar container displays on smaller screens.

@media only screen and (max-width: 767px) {
    .responsive .template-blog .blog-meta, .responsive .post_author_timeline, .responsive #top #main .sidebar {
       display: none;
    }
}

Best regards,
Ismael

Hey Michael,

Thank you for the inquiry.

With that option, you will be able to adjust the order of the columns on mobile view. You will have to manually set the order of the column in the Advanced > Responsive > Mobile Breakpoint Position settings. For example, if you want the first column to display as the second or third column on mobile view, you have to set the Mobile Breakpoint Position settings to 2 or 3.

Best regards,
Ismael

Hey Createve_Solutions,

Thank you for the inquiry.

You may need to manually apply the font in the layers’ Style > Advanced Settings > Custom CSS field. Use the font-family property to apply the custom font.

 font-family: 'document-fonts',Helvetica,Arial,sans-serif;

Best regards,
Ismael

Hey Michael,

Thank you for the inquiry.

You can use this css code to adjust the style of the icon in the iconbox element.

#top .iconbox.av-no-box .iconbox_icon {
    top: 0;
    margin: 0 auto 20px auto;
    left: 0;
    width: 90px;
    height: 90px;
    line-height: 90px;
    font-size: 50px;
}

The actual size of the icon is controlled using the font-size property.

Best regards,
Ismael

Hey Tim,

Thank you for the inquiry.

We added the contentURL meta tag to the gallery to fix a schema issue with the imageObject but we have incorrectly included the content value in the html. To fix the issue, please update the enfold\config-templatebuilder\avia-shortcodes\gallery\gallery.php file using the code below.

// https://pastebin.com/uDHPrFhJ

Best regards,
Ismael

Hey!

Thank you for the observation @Guenni007. Yes, you are correct. We should use the URL as the content value, not the page title. We will adjust the changes in the next patch.

Cheers!
Ismael

Hey Munford,

Thank you for the inquiry.

You don’t have to edit the functions-enfold.php file directly. Just use the avia_post_nav_entries filter in the functions.php file and apply the next post or entry to the previous arrow and the previous post to the next arrow.

add_filter( 'avf_post_nav_entries', 'avf_post_nav_entries_mod', 10, 2); 
function avvf_post_nav_entries_mod($entries, $settings)
{
    $entries['prev'] = get_next_post($settings['same_category'], $settings['excluded_terms'], $settings['taxonomy']);
    $entries['next'] = get_previous_post($settings['same_category'], $settings['excluded_terms'], $settings['taxonomy']);

    return $entries;
}

Best regards,
Ismael

Hi,

Weird that it does show on your screenprint.

The fonts are still displaying correctly when we checked the site again today on Firefox Dev Windows 10. The previous screenshot was taken on Chrome MacOS. Have you tried checking it on another device or computer? Are the fonts loading correctly when you accept the cookies?

Best regards,
Ismael

Hi,

Thank you for the info.

We actually thought that this is working when we checked the very first portfolio item yesterday. Today, we noticed that the site is still using an older version of the theme, version 4.5, which is no longer compatible with the latest version of WordPress and contains an outdated version of the avia_post_nav function. You should update the theme to version 4.8.9.1 as soon as possible, then update the filter in the functions.php file with this one.

/*
 * Filter für Portfolioeinträge
 */
function avf_post_nav_settings_cb($settings)
{
	if($settings['type'] == 'portfolio')
	{

		$settings['taxonomy'] = "portfolio_entries";
		$settings['same_category'] = true;
                $settings['loop_post_nav'] = false;
	}
        return $settings;
}
add_filter( 'avf_post_nav_settings', 'avf_post_nav_settings_cb', 10, 2); 

Best regards,
Ismael

Hey calcuttadioceseonline,

Thank you for the inquiry.

You can start with the following css code. Just add it in the Quick CSS field or in the child theme’s style.css file.

#top a.av-section-tab-title {
  color: #ffffff;
  background: #3561a5;
  margin-left: 13px;
}

#top .av-tab-no-icon.av-tab-no-image .av-inner-tab-title {
  margin-bottom: 0;
}

#top .av-section-tab-title {
  padding: 0;
}

.av-tab-section-inner-container {
    border-top: 5px solid #3561a5 !important;
}

Please make sure to toggle the Performance > File Compression settings after adding the css.

Best regards,
Ismael

Hey Rob,

Thank you for the inquiry.

It seems to be working correctly on our end as shown in the screenshot below. The css rule for the font open sans has been striked through because there is a more specific css rule in the stylesheets. However, that rule sets the font property to inherit, which means that it will still apply the open sans font to the body text.

Best regards,
Ismael

Hi,

Thank you for the update.

We are not seeing any styling difference between the sites anymore — they look exactly the same now. The text in the footer are also similar. Did you figure out what was causing the styling issue?

Best regards,
Ismael

Hey biotechz,

Thank you for the inquiry.

We are not really sure what is causing that issue but the following thread might help. The user asked if the search icon can be removed completely from the main menu, but since you are using a search widget, you may need to manually remove it from the Appearance > Widgets panel.

// https://kriesi.at/support/topic/remove-nofollow-from-search-item-of-main-menu/

Another thing that you could do is to disallow crawling on pages with a specific parameter, which might be the more reasonable solution. You can set this rule in your robot.txt file.

Disallow: /*?s=*

// https://developer.mozilla.org/en-US/docs/Glossary/Robots.txt

Best regards,
Ismael