Yes it's odd, for some reason the CSS added in the blogs template isn't injected into the page anywhere. If you're satisfied with adding custom CSS in the Customizer > Additional CSS area, that could be a quick solution. If you want me to investigate the WPBakery template CSS issue in more detail, I can try to create a clone of the site and do a more in-depth investigation.
Yes for now we are using the Customizer > Additional CSS for
CPT's Blogs and Jobs
I agree it's very odd because our other CTP's Companies and Available space work fine.
If you could investigate, that would be really helpful, especially for when we are adding more CPT's in the near future, it would be good to add the css in the page its self.
It seems to be related to the Bridge theme in my local testing. If I activate Twenty Nineteen, the CSS added in the Content Template begins to appear in the source. But with Bridge it's inconsistent. On my local copy, CSS added to the available-space template is not shown on the post immediately, but on your site it is. I will ask my 2nd tier team to take a closer look at this and let you know what I find out.
Hello, I'm Beda, 2nd Tier Support at Toolset.
I'll handle this case from here on as I already entered in contact with Bridge's Support in past, reporting on an issue which as the Bridge Support did feedback to me, is reported to their Developers, however, I did not hear back from then. https://toolset.com/errata/a-javascript-error-prevents-using-navigation-in-the-bridge-theme/
It would be important, since the issue here likely relies in an integration part of the Theme made for the WP Bakery Page Builder, that you as user of the Bridge Theme would open up a ticket with them, mentioning that Toolset support is reaching out about this issue as well in order to resolve it together.
You can mention that the Bridge theme adds compatibility with the Page Builder's CSS in its functions.php file with:
//include Visual Composer styles
if (class_exists('WPBakeryVisualComposerAbstract')) {
wp_enqueue_style('js_composer_front');
}
This is unusual, usually, a Theme doesn't enqueue the Composer styles again, and it is this precise line causing the conflict with Toolset (toolset replaces the_content with the Content Templates).
I have sent an email to the contact I have as well, so to clarify the code and eventually, we can provide a fix on either side of Toolset.
It'd be great if you can help expedite the communication thru a ticket with the support.
Unfortunately, the Developers at the Bridge Theme have informed me that in the close future there are no plans to change this.
I'll ask our developers if we can add a "fix" on our end, and will inform you here about it.
A child theme could always be a solution, where you simply not call that function (but then you need to design all posts with Content Templates). Or, you could create a custom logic that checks whether a Content Template is assigned or not, and hence load or not the Theme's function.
As said, I'll now also discuss this with our developers.
Please await my news here.
We should not solve this in Toolset, as solving this in Toolset would mean emoving scripts loaded by the theme which for whatever reason, they require.
I can only recommend asking Bridge Theme to solve this, or/and to dequeue that script either in a Child Theme or with custom Code when using Toolset and Bridge and the Builder
Unfortunately we cannot change this from our end, given it would mean as mentioned to remove theme styles (since the theme enqueues it) and that would be a bad practice.
