So I modified the code you sent me slightly as the view ID appears to have changed (I took the view in and out of the template maybe it changes when you do that?):
Its fairly obvious I think if you just look at "Country of Origin" you can see the issue compared to other points on the page (e.g. Genre above thats how it should look).
Looking at the source it appears that you have inserted the label "Country of Origin:" in its own p tag, and then View div is then added after. (See screenshot.)
So the closing of the p tag starts a new line before our View div is rendered, meaning changing its display property is ineffective.
It looks like you are inserting these with page builder modules, you should try inserting the shortcode for the View immediately after the Country of Origin label so that the div appears inside the same p tags.
Strange although I do have a page builder installed and do use it, I am not using it on this Toolset template.
I have attached a screenshot of the code editor for this template so you can see the code from admin side, as you can see from the screenshot theres no P tag or anything in-between.
The markup you can see in my screenshot includes markup generated by WP Bakery/Visual Composer from what I can see, but in any case can you check the Content Template settings for Output mode which should be Manual paragraphs to avoid the additional p tags being inserted.
I am not using WpBakery on this page though and output mode is set to manual paragraphs as well. Do you have any other ideas what could be causing this?
I will mark your next reply as private so that I can get log-in credentials from you—you may want to create a temporary admin user for me to use that you can later delete. And be sure to have a current backup of your site, even though I don't intend to make any changes.
OK, the VC markup appears because the content template is built with VC shortcodes, even if you are not using the VC editor.
Anyway, the issue with the broken markup for the View inside the p tag is that... it is not valid HTML to include a div inside a p tag (even if you change its display property to inline or inline-block), and so although it appears correct in the source code, the browser itself "fixes" this invalid HTML.
So the solution is for this line where you want to insert a View to replace the p tags with divs.
You should be able to add some CSS to get the line spacing you require after replacing the p tag with a div. Give the div a classname to be able to target it, and then just assign the same properties as the neighbouring p's whose spacing you want to match.
Or... the next Views update which is currently in testing so will probably be released early next week includes a 'raw' output mode which doesn't add a wrapper div. You'll be able to use that inside the existing p if you prefer that.
Because of some code it has in common with the next Types update the next version of Views is being held until the Types update is ready, and that is just completing testing. Once we have run them on our own systems for a day or two to confirm there are no issues they will be good to go, so that should now be possible next week.
