Tell us what you are trying to do? Activate Toolset Layouts - I have made a post type, custom post fields for that type, custom taxonomy for that type. However, when I turn on Layouts to create a layout for the custom post type, my site's css stops being read
Is there any documentation that you are following? Toolset documentation
Is there a similar example that we can see?
What is the link to your site?
simonecampbell.com/funeralpotatoes
I think it's a conflict with Bootstrap, but I am not yet sure.
Please head to the Toolset > Settings > General > Bootstrap loading
There, experiment with different settings.
If that brings no change, I need a copy of the Theme and the steps to replicate this problem.
Then, I can debug it and eventually provide a solution.
You can share the theme with me using Google Drive, for example.
If you are not sure it's due to the Theme and Layouts please confirm this first by disabling all plugins but Toolset, and test again.
If the issue is still there (which I suspect), it's due to the theme.
Thanks for the response.
I tried changing the Bootstrap loading settings, and none of the settings helped solve the problem.
You can get a free version of the theme here: hidden link
Also, in my original post, can you hide my url? I was not sure how to do that.
It's not required to hide the URL; no one can see it but you, me and other Toolset Supporters.
You should be able to verify that by logging out and looking at the thread here.
I verified the problem with this theme, but I fear this is not solvable in Toolset.
If you analyse the code of that theme, you'll notice that the templates are very particular.
For example, they never call the mandatory get_header or get_footer, or a loop in general.
Please compare the theme's files with something like Twenty Seventeen, to see what I mean.
You can pick the "single.php" for example.
Notice how TwentySeventeen calls properly the header and footer functions so other plugins can hook their code in there (for example) but also WordPress itself can work as expected.
I also see in their header.php for example:
- Force plugins to stop stating incorrect errors -
<?php wp_head(); ?>
*/
This is definitely wrong, it will produce issues.
Plugins exactly need that to hook their functions.
If you disable this in a theme - it's up to the developer to be aware of the consequences:
https://wordpress.stackexchange.com/questions/218885/putting-content-into-header-php-without-using-wp-head
I suggest you get in contact with the developer of that Theme and ask for clarifications on why these basic features are not allowed in the theme.
Most plugins won't' work with this theme.
o.k. I changed my theme - looks like it works now. Thanks!
