brinksa5man

Is Anyone else having this problem or have you moved to another alternative. Would like to know about another alternative. We’ve been unable to post sermons in the last two weeks.

site affected: https://www.wumc.com/

@alusion – Can you refer me to a link on how to disable adblocker on my website?

I am a newbie trying to learn SEO and having the same difficulty everyone else is.

Thanks alusion.

Thank you, Avantart! I got it to work on the Stargazer theme using this:
.cycloneslider-slide{ background:transparent !Important; }

Thank you K.T. That does what I wanted to do. (Had to drop the -x)

Janet4now, thank you for your response. I know how to get to header.php but have never modified one and don’t know how or where to make the modification.

https://www.bestnetlook.com/tlg is site

The URL is https://www.bestnetlook.com/tlg and I am still in development.

I think I just figured it out. I used the following media query:

@media screen (max-width: 500px){
.headerclass {background:#f9fcb8}
}

Thanks for your quick response.

Bob

On https://www.pathwaysoffaith.com/My Path/ and https://www.pathwaysoffaith.com/Stories From the Path/. Both pages have posts which extend the transparent page.

Thank you.
Bob

Sorry, the site is https://www.pathwaysoffaith.com and the page is Stories from the Path. Please excuse placeholders, we are still in development.

I have a background image (1200px 1200px) set to fixed and that works just fine for an average-sized monitor. On a tablet (or a phone) the background image scrolls along with a transparent overlay that I created. And it leaves an ugly grey color at the bottom of those pages that are long.

I have tried using a media query to set the background-size various ways but no luck.
Any ideas anyone?

Thank you Patrick for your reply. I thought since Posts in Page shows compatibility through WP 3.5.2 and I am on 3.9.1 that there might be some incompatibilities that caused the posts_loop_template.php to become inactive. I will certainly use your comments in the future.

For now I was able to find the object that was affected in the underlying theme and resolved it by adding some CSS to the child theme.