Flare 2019 r2 build 7283, Windows 10.
I looked for this issue, but couldn't find anything. Ever since updating to this build, we've been getting 'Master page doesn't contain a body proxy' warnings in the build logs. My master pages most certainly do have a body proxy, so I was pulling my hair out trying to resolve this one.
Turns out that MadCap have slightly changed the way they insert the <Madcap:bodyProxy> custom tag in master pages; this tag now includes a link to the MadCap.xsd namespace. (This is still inserted by default on all new topics in the <html> parent element, as far as I can tell.)
Body proxy used to be:
<MadCap:bodyProxy />
Body proxy is now:
<MadCap:bodyProxy xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd" />
The trouble is that if you have HTTPS enforced for your website, you've already gone through and changed all http references to https, including all Madcap inserts. When building, it looks like Flare treats the https as non-conforming content and produces the build log warning.
It's only a warning, and your output isn't affected, but it's still annoying. I'll create an issue report for Madcap to get all such http references updated to https, which is pretty much the standard at this point. Any instances of http in your source code, and you'll get the broken padlock in the browser.
Build 7283, body proxies, and HTTPS enforcement
Re: Build 7283, body proxies, and HTTPS enforcement
This text:
xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd"
is also being inserted into condition and variable custom tags, making me think it might be a bug instead. There's no reason for that text to be there.
xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd"
is also being inserted into condition and variable custom tags, making me think it might be a bug instead. There's no reason for that text to be there.