Hey olifant551,
You can have a staging site as long as it’s on the same domain, using a sub-domain is fine with one license.

Best regards,
Mike

Hey fillance1,
Here is our documentation
To remove the backlink add the below shortcode in the copyright field.

[nolink]

Best regards,
Mike

Hi,
That is great news! Who would have thought such an old version could be patched?
But, please forward the info to the client to purchase a license and update the theme, it could save a lot of headaches later because most WordPress installs auto update now and with their new direction and the block editor, this will most likely break the sites using the older versions.
I know you said the client is not very WP savvy, which is ok because we often help members with updating via FTP.
I will leave this ticket open so if you ever reply again about the user being ready to update I will see it :)

Anyways, well done and have a great day.

Best regards,
Mike

Hey Line,
Sorry for the late reply, this is because the category pages have a different layout, but I added this code to the end of your functions.php file in Appearance > Editor:

//change category page layout to blog single big style
add_filter('avf_blog_style','avia_change_category_blog_layout', 10, 2); 
function avia_change_category_blog_layout($layout, $context){
if($context == 'archive') $layout = 'single-big';
return $layout;
}

to change your category page to the “single-big” layout that shows the image.
Unfortunately, you can not have the masonry on the category page.

Best regards,
Mike

Hey HITFighter,
Sorry for the late reply, the PSD files are for the old default demo, because the demo didn’t include most of the images. Since 2017 the demos include royalty free images and the demos were created with the Advanced Layout Builder in the theme, so no PSD’s were created, nor is there a reason to create them.

Best regards,
Mike

Hi,
Sorry for the late reply, and thank you for the screenshots.
So to review, on a different server everything was fine, on the new server the “no products found” warning is showing, plus other customizations are not working.

I believe this is because when the site was moved and re-saved the automatic generated clases changed, for the “no products found” warning it depends on “.avia-builder-el-5” which is a automatic class, which could change if any elements are moved on the page and then re-saved.

I could not login to check this, please re-new the login so I can check.

If any other css or scripts depend on auto classes like “.avia-builder-el-5” and they don’t work, this would explain it.

BTW, I also see that you are getting 404’s on your site because the google map iframes in your footer doesn’t seem to include the API key You might want to look at that :)

Best regards,
Mike

Hi,
Sorry for the late reply, I took a look at your site and I believe the reason your logo is not shrinking on scroll is because of these custom css:

#header.header-scrolled-full{
height:170px!important;
}
#header.header-scrolled-full #header_main_alternate{ margin-top:60px!important; } 

notice how they are keeping the header size large on header scrolled.
I assume that you wanted this css for a different reason. I recommend removing all of your custom css and clear your cache to see if this fixes your header, then add your css back a little at a time to find all of the css that doesn’t conflict with the header.
Then we can try to solve the remaining issue without out effecting the header.
As I try to read back through your posts it seems that the header not shrinking is fairly new, so we should be able to get back to it working easily.
I also assume there was no new plugins added recently.

Best regards,
Mike

Hi,
Thank you, we will close this now, but feel free to open new topics for anything we can assist with.
Have a great day!

Best regards,
Mike

Hey Michaela,
Sorry for the late reply, I took a look at the W3C validator, and found the issues to be a misunderstanding of the validator, for example, the first 6 say that we don’t need to use the type attribute for our scripts, but this has been standard practice for a very long time, so we choose to do this. Then it says we should not use “roles” but for the same reason above we do.
Then for most of the rest the validator is not reading our builder shortcode correctly, it thinks that it is reading pure html which it is not.
We have had these misunderstandings brought up many times, and the dev team has considered them. Our dev team is in the middle of a complete rewrite to help move the theme forward for the future. For now we ask for your patience while we do this, and your understanding that the validator doesn’t always read our shortcode and scripts correctly.
Thank you.

Best regards,
Mike

Hi,
I couldn’t see the image you linked to on the tinypic site, but I think I understood. I removed the red on-hover overlay and ensured the black overlay was restored.
Actually, I didn’t “remove” the css I just “commented it out” should you ever want to see it again, it’s in your style.css in your child theme.
So Please clear your browser cache and check.

Best regards,
Mike

Hi,
I took a look and the hover over the crosses seems a lot better now, but as you pointed out, just a little off. I see that you are using the columns as the link, instead of the cross image. I would use the images as the link, but I assume that you don’t want to hover background for the images or the green circle, so this should remove it:

#av_section_1 .kreuz_361 a:hover .image-overlay,#av_section_1 .kreuz_manufaktur a:hover .image-overlay {
    background: transparent !important; 
opacity: 0 !important;
}

Let us know if this helps. When you try the 1/1 version, I had a after thought that you might need to add display: inline-block to your css to line the two images up, but we’ll know more when you try.
One question, the two crosses are not in a line with the “moebel” text in the center, is this meant to be a straight line across?

Best regards,
Mike

Hi,
Please try this code in the General Styling > Quick CSS field or in the WordPress > Customize > Additional CSS field:

#top #header .av-main-nav > li ul li:hover > a .avia-menu-text, #top #header .av-main-nav > li ul li:hover > a .avia-menu-subtext {
    color: #fd9351 !important; 
}

Best regards,
Mike

Hi,
Thank you for the login, as I looked closer I found that the error is actually for Google Maps (init_embed.js:172)
which is your map iframe:

<iframe style="border: 0;" src="https://www.google.com/maps/embed?pb=!1m18!1m12!1m3!1d2357.2121961597686!2d-3.0491942839249377!3d53.78571074941063!2m3!1f0!2f0!3f0!3m2!1i1024!2i768!4f13.1!3m3!1m2!1s0x487b4402051c9e99%3A0x5b177425636c9e5d!2sSouth+Shore+Mot+Blackpool!5e0!3m2!1sen!2suk!4v1555064402445!5m2!1sen!2suk" width="400" height="300" frameborder="0" allowfullscreen="allowfullscreen"></iframe>

Removing it solves, but I know you want to use it :) So as I compaire your iframe with the Google Developers Guide it looks like the map iframe requires a API Key, and I don’t see one in yours. Please read the developers guide and get a API Key and add it to your code.

Best regards,
Mike

Hi,
Please check that the code you copied above doesn’t have any “curly quotes” if that doesn’t solve, then Please include an admin login in the Private Content area so we can be of more assistance.

Best regards,
Mike

Hey codecreative,
I took a look at your 404’s and see they are coming from:

https://lh3.googleusercontent.com/a-/s48-c/AAuE7mC9FnMeFkj8hLf6v5P84ynEnq4ZD_X-7zHOOoPO

This seems to be a photo from Google Drive, or perhaps a file.
Have you linked any assets from your Google Drive on your site?
If you can’t find it please include an admin login in the Private Content area so we can be of more assistance.

Best regards,
Mike