lowestofthekeys

Got ya, thank you!

Ha, that worked perfectly. I just tested this via functions.php and any time I generate a new post, the AMP option is enabled (the option is disabled on the older posts).

Thank you!

Hi Renee,

I have that set already.

Currently AMP is set to “disabled” on any new posts. I’m wondering if there is a way to change it to “enabled” automatically anytime someone creates a new post.

Holy balls, that worked. I hadn’t realized the media query wasn’t closed.

Thank you so much, that was driving me insane.

Also, as for the CSS in the child theme…I’m actually still working on fixing that.

I’m sorry about that, I made it a habit to remove code I use for testing because occasionally I would forget about it. It’s back in there.

Disabled and I’ve removed all the cached files. I even removed the twentythirteen theme temporarily to see if it’s interfering with the child theme.

Yes W3 Total Cache.

Ah good eye with the brackets. I removed those and I had added the important rule beforehand, but nothing had changed when I did.

For clarities sake, I removed the added gradient css3 classes and added the !important rule back in. Even with caches cleared it does not seem to be working.

There’s more than one, but the primary is the press_kit style located at the bottom of the stylesheet or just do a ctrl-f press_kit. This is the one I tried to change the background color with using the !important tag.

https://pieglobal.com/pie-press-kit/ Here’s the page. If you view it under source, you can see the div in question:<div class="press_kit">. The stylesheet is available here: https://pieglobal.com/wordpress1/wp-content/themes/twentythirteen-child/style.css

Hmm that worked for the manual styles, but when I alter the styles under style.css and add “!important”, things do not change.

Yes. I also tried adding a “style=”background #000000″” to the div and nothing seems to work.

Yes Ma’am.

Found the solution…it just need to only include the in_category(‘blog’) portion.

Yes, I added the “!in_category(‘blog’)” to the function, but it doesn’t work in the sense that the custom content is not filtered to the blog category.

I’ve tried using the slug ID and removing “!is_page” from the function, but I can not seem to get the custom content to appear under only the blog category posts.