Home Page Features Not Working

[borinqen]

Hello:
I have noticed recently on my site that some of the elements are not working. I have a feature image on the homepage that had letters that would start to glide across the image as the user scrolls down the page. This feature is not working on the site currently. When you view the site that particular area on the screen looks blank now. I am not sure why. Also, I have an area that says “What We Do” in that particular section the classic images are not aligned when you go to the live site. When you view it in the inspector they look somewhat aligned but when you view the live site they do not. Could this be a plugin causing the issue? I do’t know what else to check. Tks!!

2018-07-24_0747

2018-07-24_0749

This is what I see in the image that I have on the home page instead of seeing the image with the letters coming across it.

2018-07-24_0758

This shows how the images on the page are not showing up aligned:

2018-07-24_0800

When you view the site on mobile it shows up fine. This only happens on desktop.

[Alaa]

Hello @borinqen

To fix the alignment issue, please make sure the gap element in the second and third columns has a value of 50px not 40px:

The background issue seems to be related to the parallax function, please try switching to the parent theme and recheck this issue, If this didn’t help, then please provide us with WordPress Dashboard login details in a “Secure Note” so we can investigate this issue.

Thanks.

[borinqen]

The gap element was set to 50, I only switched it now because I wanted to see if it would help. I switched the value a few times to see what would help. As far as the background, I will send you the login info because I have yet to figure out the problem. Tks!!

[christian]

Hey @borinqen,

There’s currently a known conflict with the Parallax background and Slider Revolution.

Fortunately, there’s a temporary fix. I’ve added this code in your Global CSS.

.x-slider-container {
    z-index: 1;
}

Now your background shows up.

Hope that helps.

[borinqen]

Ok, thank you. This known conflict is on the side of X or is it something that I can do to fix? ( I know that you have already added a temporary fix but it is just that “a temporary fix.” ) Is there going to be a final resolution or is it something that users can do on our end.

[christian]

This is something in X, regretfully. An official fix might be available in one succeeding releases. Please stay tuned for updates and once an update is available, you can check our Changelog for the included bug fix.

Thanks.