I clearly didn't think this through when writing the filtering. I will log it as a bug.
The general idea with the filtering was that you can have a general C1 Function ensuring open graph tags for all pages - and if a specific function overrides the tags, the specific function's output is used instead.
A workaround is to wrap the <meta property="og:image" /> elements inside <![CDATA[ ... ]]> section. This workaround works fine when the content originate from a C1 Function.
Example of a razor function emitting multiple og:image tags:
The general idea with the filtering was that you can have a general C1 Function ensuring open graph tags for all pages - and if a specific function overrides the tags, the specific function's output is used instead.
A workaround is to wrap the <meta property="og:image" /> elements inside <![CDATA[ ... ]]> section. This workaround works fine when the content originate from a C1 Function.
Example of a razor function emitting multiple og:image tags:
@inherits RazorFunction
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<![CDATA[
<meta property="og:image" content="http://ia.media-imdb.com/images/rock1.jpg" />
<meta property="og:image" content="http://ia.media-imdb.com/images/rock2.jpg" />
]]>
</head>
<body>
<h1>og image tags was added</h1>
</body>
</html>