Photoviews, sorry but Child Themes should be for everyone. That is not an issue to agree or disagree on, it’s proper site setup and there isn’t a theme developer or site wp developer out there that won’t recommend using a child theme. And, there is a child theme provided so it’s not that big of a deal. Upload it, activate it. Or plugins for creating a child theme can be run. This is not something that is a preference or opinion of mine, it’s wordpress basics, and anyone working with WordPress will tell you the same thing. It’s not a difficult thing to implement, and you are making a big deal out of nothing in that regard. What is being suggested may be implemented by Kreisi in the future. But in the meantime, a simple fix was provided if you really want to use it. And I stress simple. I am only trying to be helpful, and your replies are very harsh.

freepixeweb, Fusion Builder has come a LONG way in the time I have been using Avada. I would categorize the current version of it as one of the better in theme builders. And their Patch and update manager system prevents these exact issues we are having with LayerSlider. You don’t have to update their whole theme to update a plugin or do a patch. But back to builders, Enfold’s builder is incredibly easy to use for users without much technical knowledge so there is a trade off. I personally have really been enjoying SiteOrigin’s Builder. It’s fully functional free, and the Premium version adds some cool addon for very reasonable license fees. I find it the best of both worlds.

I do agree this is a bigger issue than support seems to acknowledge. When a client logs into a site and sees these errors, it does not look good. At this point I only have 2 sites using Enfold, and one is my own site. The other is a client that I do updates for and they never access the site. But if I was in your case, with that many licenses and clients, it would be a deal breaker for sure.

PS and thanks, I will give the options you mention a good look later. At a glance OceanWP plus SiteOrigin Builder seems like a good combo.

Photoviews7, to be fair when it’s a major security update issue, Kriesi will update. A security plugin just notifies you when any plugin is out of date generally. It doesn’t mean there is a major security issue with the plugin. So I haven’t seen an issue there. But there was clearly an issue with the plugin and theme updates in this case which this thread shows. And that is not good. If this is a bundled plugin, make sure everything is compatible with the theme.

I am not trying to be overly critical of Kriesi, but I do find them much slower updating bundled plugins than any other premium theme framework I use. And I have never had an issue with a bundled plugin incompatibility that lasted as long. It’s very understandable why people are upset.

Rikard, in my case I am reporting the issue because it didn’t occur until after the last Enfold and Woo update. The fonts were all completely fine before that. So it may be something that needs an option in the theme admin if this is something new. I had already figured out the CSS fix, I was just posting that I saw the exact same issue with the huge font sizes on some Woo pages as the OP after the updates. I never needed CSS to try to match up product titles across Woo pages through years of using the theme. Thanks.

Just to reply before I duck out of the conversation, I use a child theme. It was not a case of my CSS being replaced by the update. It was AFTER the update that I had to manually set a bunch of Woo titles with CSS because the font sizes were way way off from Woo page to page. I am using Woo with other themes, and I did not see this issue after recent updates. It’s the exact same issue Annie is talking about, and that I have see mentioned other places in the forum.

Annie, I had the same issue with the font sizes in Woo. I am not at my main computer so I can’t send it, but I had to manually set them with CSS. I’d check your other shop pages too because I also ran into fonts that were way too small on pages shows lists of products (not categories). The titles were a completely different size after the updates. Huge fonts on category listing pages, small fonts on product listing pages.

No problem Sandra, glad it helped. I’d say it’s likely that it may have been specific settings in W3 causing issues, but I sure couldn’t find what they were. Disabling it was a much easier fix hah.

I had both the font size issues, and the slider issues you had on a single site install. I had to set font sizes with CSS in several WooCommerce sections because the product title fonts were huge on my shop page and category pages, and tiny on pages that listed products.

Other theme frameworks I use have had issues with this Woo update. The LayerSlider issue is a bit annoying though because I am guessing it being so out of date in this case might be contributing. I don’t recall a time since I have used the theme where it’s gotten this far behind on the LayerSlider version.

• This reply was modified 7 years, 8 months ago by torndownunit.

My site is running PHP 7 and I am seeing these same issues.

I ran into the exact same issue and had fixed it with CSS already. The font size on archive pages was huge, and the font on pages displaying just a product grid was a complete different size, and too small. The issue is fixed, but I just thought I should add a report because clearly other people are seeing the issue as well.

I was running into a lot of odd display errors that were resolved when I disabled W3 Total Cache. I see several posts in various places on the forums where people mention they are running it so I thought I’d contribute. I went through my site enabling and disabling plugins testing, and every time I’d activate W3 I’d have issues. I had no issues until I updated Enfold and Woo to current versions. I have been running PHP 7 on my hosting account for awhile now too. I don’t know if it’s W3, Enfold, Woo, or a combination of multiple issues in my case, but disabling W3 has solved all problems for me.