<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Chrome fop2 extension: popup content not showing]]></title><description><![CDATA[<p dir="auto">Hi<br />
The fop2 chrome extension (v 2.0.0) does not display the content that is returned when calling the URL<br />
in 'popup content'. It used to work fine but now it displays generic popup content "Ïncoming call - Chrome Fop2 extension"</p>
<p dir="auto">The 'Fop2 Extension options' -&gt; 'Popup settings' -&gt; 'popup content' field contains : <a href="http://192.168.10.3/cgi-bin/popup?number=#%7BCLIDNUM%7D" rel="nofollow ugc">http://192.168.10.3/cgi-bin/popup?number=#{CLIDNUM}</a></p>
<p dir="auto">When I use this url in Chrome like <a href="http://192.168.10.3/cgi-bin/popup?number=1234567890" rel="nofollow ugc">http://192.168.10.3/cgi-bin/popup?number=1234567890</a><br />
my cgi produces :</p>
<blockquote>
<p dir="auto">Content-type: text/html</p>
<p dir="auto">Mr. J. Doe is calling from 1234567890</p>
</blockquote>
<p dir="auto">The Popup <strong>link</strong> works fine, as does clicking the popup balloon.<br />
Has the format changed? Which content will  the fop2 extension accept?</p>
]]></description><link>http://localhost:4567/topic/2868/chrome-fop2-extension-popup-content-not-showing</link><generator>RSS for Node</generator><lastBuildDate>Tue, 27 Oct 2026 05:49:05 GMT</lastBuildDate><atom:link href="http://localhost:4567/topic/2868.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 14 Jul 2020 12:25:58 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Chrome fop2 extension: popup content not showing on Thu, 16 Jul 2020 09:00:22 GMT]]></title><description><![CDATA[<p dir="auto">SOLVED:  Nothing changed in the fop2 extension. For some, unknown to me, reason the script failed, resulting in an internal server error when called by the fop2 extension. Restoring a backup versions of the script solved the problem.</p>
]]></description><link>http://localhost:4567/post/11994</link><guid isPermaLink="true">http://localhost:4567/post/11994</guid><dc:creator><![CDATA[ictiucn]]></dc:creator><pubDate>Thu, 16 Jul 2020 09:00:22 GMT</pubDate></item></channel></rss>