1.2.x Update Breaks Layout in CSS3 Web Pricing Tables Grids

Support
#1

If using the popular plugin CSS3 Web Pricing Tables Grids, Pro’s theme CSS modifies its tables by using the same class names as the plugin.

Specifically:

#cs-content *, #cs-content *:before, #cs-content *:after {
-webkit-box-sizing: border-box !important; 
-moz-box-sizing: border-box !important;
box-sizing: border-box !important;

If the box-sizing line is commented out, the layout is fixed and looks as it did prior to 1.2.x. Not sure if Pro or the plugin author is guilty of not using best practices or if it’s just a coincidence and we’re at a stalemate to see who balks first, but wanted you to know.

#2

Hi there,

Thanks for writing in.

We can’t cover 3rd party issues but I could help adding this to our issue tracker so our developer could see it. Would you mind providing more details of the issue? And please provide a sample URL.

Thanks!

#3

It sounds a bit smug when you say “We can’t cover 3rd party issues.” Your software runs on a 3rd party’s platform, running a 3rd party’s development language, on 3rd party hardware. Your product depends on multiple 3rd parties just to work. If I’m asking for support on a plugin, that’s one thing. I’m not. I pointed out a compatibility issue between your theme and a popular plugin. Whose fault is it? I don’t know. But I can tell you of the 3 themes we work with, Pro support is the only one to consistently give the “We can’t cover 3rd party issues” response every time.

I provided all the information needed to diagnose the issue. I cannot provide a URL where it shows broken - we can’t leave it broken, so we had to use CSS to void/revert the CSS noted above. But here is a URL with a working Pricing Table on it - https://co50.com/mp/

#4

Hi There,

Although we don´t provide support 3rd party plugins which are not bundled with X or PRO we can take a look at your case and check if we can provide you a CSS fix if it is not complicated.

For that you will need to provide the URL with a sample page with the issue, we cannot fix if we can´t see the error.

Thank you

#5

Joao,

I am not looking for support. If you read my OP, I was just letting you guys know of an incompatibility. I already have a CSS fix for it.

#6

Hi there,

Ah, but we need more information about this so we could forward it to our developer. But sure, I’ll still add this to our issue tracker.

About the support coverage, we can’t really provide support to 3rd party plugins especially plugins that aren’t bundled with the theme. The main reason is, we’re not the author of the plugin and we’re not sure how their features works, and due to that, conflicts are really unavoidable since we’re not sure how they implemented it.

But still, we’re open to idea and fixes that we can include, I’m not saying we’ll just stop here just because it’s a 3rd party plugin, but all we could do is forward it to our developer for further checking.

Thanks again.