Boost C++ Libraries: Ticket #2317: Implement live patching of web site release content. https://svn.boost.org/trac10/ticket/2317 <p> Augment the various doc display code to allow for patching of individual files in the release ZIP archives. Do this by checking if a replacement exists in a designated location in the svn repo, and using the svn repo content if it exists. Location for such patches should be "/website/patch/&lt;archive.zip&gt;/". And inside the replacement must use the same hierarchy as present in the ZIP archive file. </p> <p> Note, implementing this will require doing remote HTTP reading with PHP. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/2317 Trac 1.4.3 Daniel James Sat, 21 Feb 2009 17:55:05 GMT <link>https://svn.boost.org/trac10/ticket/2317#comment:1 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/2317#comment:1</guid> <description> <p> If this is ever done, <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/2350" title="#2350: Bugs: broken image on Boost.Test 1.36.0 documentation webpages (closed: fixed)">#2350</a> could be reopened. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Daniel James</dc:creator> <pubDate>Mon, 07 Jun 2010 22:30:50 GMT</pubDate> <title>status changed; resolution set https://svn.boost.org/trac10/ticket/2317#comment:2 https://svn.boost.org/trac10/ticket/2317#comment:2 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> </ul> <p> Oh, I've done this, but in a simpler manner for Boost.Range (<a class="changeset" href="https://svn.boost.org/trac10/changeset/62007" title="Don't use php to display the documentation if the file is present.">[62007]</a>, <a class="changeset" href="https://svn.boost.org/trac10/changeset/62008" title="Check in a copy of the range docs, as some of the files are missing in ...">[62008]</a>). Might change it later to use the display code, although I was thinking of just preprocessing the html files if I ever wanted to do that. </p> Ticket