Thread Starter
RBX
(@rbx)
I realized that I needed to reconnect with WordPress.com after re-enabling Jetpack, doing which reintroduced the problem.
Edit: I disabled all of Jetpack modules, but the problem remained, and got fixed as soon as I disconnected from WordPress.com.
I have enabled it again so you can diagnose it.
Also, the WP version is 4.2.4, I mistakenly set it to 4.3.
And the problem seems to be with labels instead of inputs.
Where was the script cited above coming from?
Right now, it doesn’t seem to be occurring for me, with input being computed as inline-block.
Cheers!
Thread Starter
RBX
(@rbx)
Yes, the script is included in the theme and is probably unrelated to the error. I have tried disabling other features as well including caching and minification, but they don’t seem to be contributing to this. What triggers this is integration of Jetpack with WordPress.com.
Could you add this to your theme’s functions.php or a core functionality plugin:
apply_filters( 'jetpack_implode_frontend_css', '__return_false' );
function bk_remove_grunion_style() {
wp_deregister_style('grunion.css');
}
add_action('wp_print_styles', 'bk_remove_grunion_style');
I figured out what’s happening. Jetpack concatenates all CSS by default to save the time for all of the various HTTP calls that would be needed for each individual module’s CSS.
When you connect to WordPress.com, we enqueue our jetpack.css, which include our contact form’s CSS. We both are using the same class for the contact form, so our contact form’s CSS is being applied to your contact form.
Assuming you don’t want to use Jetpack’s Contact Form feature, the above code will prevent the concat process and forcibly ensure that the contact form CSS is not included.
Cheers!
Thread Starter
RBX
(@rbx)
Sorry, this didn’t remove the conflicting CSS.
.contact-form label {
margin-bottom:3px;
float:none;
font-weight:700;
display:block
}
and a few others still apply.
I would have changed the class, but even my theme’s contact form uses it.
Thread Starter
RBX
(@rbx)
I’d like to mention that the problem persists. I wanted to use few features such as social media buttons and comments, but nothing works without wordpress.com integration, so I’ve completely disabled the plugin.