First of all, thank you for this fantastic theme. It’s incredibly robust and easy to use and has made my first experience building a website a wonderful experience!
I have a question about the woo.css file under the “woocommerce” directory. Because I removed category images, it looks bad to have the mobile version have the min height of 315 px, as the original theme has it. So I tried fixing it in my own custom style.css file in my child theme, but that didn’t work. I noticed you had put it in a separate file for the responsive woocommerce theme, so I tried doing that — like the original Fruitful, my custom css for mobile is tagged for the correct media size in a file labeled woo.css under a woocommerce directory.
I tried marking the min-height as “none !important” or doing “max-height: 50 px !important” but none of that worked. Having the same code in my style.css file or the custom css editor on wordpress itself has similarly negligible results.
It seems like the parent theme is loading first, because the original css is still there, and it’s overriding any of my custom changes. I tried temporarily deleting the woo.css file from Fruitful, which fixed it (I moved the rest of the responsive css to my child theme so that would all be preserved) — but that doesn’t seem like a good long-term solution, right? (Safari and Chrome both display a 404 error that they couldn’t find the file, naturally, since it wasn’t there. Even though they both went on to find the correct one, I feel like that’s bound to slow things down.)
How can I get my custom woo.css to load first?
Thanks so much!
(Looks fine on desktop, just has giant boxes on mobile)
- The topic ‘Responsive css loading before child theme’ is closed to new replies.