<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Transition Technology: Ticket Query</title>
    <link>http://localhost:8080/trac/query?status=!closed&amp;cc=~jim&amp;desc=1&amp;order=owner</link>
    <description>Support and issues tracking for the Transition Network Web Project.</description>
    <language>en-US</language>
    <image>
      <title>Transition Technology</title>
      <url>/trac/chrome/site/TransitionNetwork-Logo-Web-Small.jpg</url>
      <link>http://localhost:8080/trac/query?status=!closed&amp;cc=~jim&amp;desc=1&amp;order=owner</link>
    </image>
    <generator>Trac 0.12.5</generator>
    <item>
        <link>http://localhost:8080/trac/ticket/582</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/582</guid>
        <title>#582: TN.org platform and sites</title>
        <pubDate>Mon, 02 Sep 2013 09:30:02 GMT</pubDate>
        
        <dc:creator>jim</dc:creator>

        <description>&lt;p&gt;
The TN.org platform and Drupal site updates are to be tracked in this ticket.
&lt;/p&gt;
&lt;p&gt;
Current PROD platform build = &lt;strong&gt;P009&lt;/strong&gt;
Current STG platform build = &lt;strong&gt;S010&lt;/strong&gt;
&lt;/p&gt;
&lt;p&gt;
Updates pending:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;SECURITY UPDATE - NO RISK: Pressflow core 6.30 is due, but the security holes fixed do not affect us, low priority. Platforms: present in S010, but not in P009.
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/582#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/264</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/264</guid>
        <title>#264: Context changes</title>
        <pubDate>Fri, 17 Jun 2011 12:23:53 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
As discussed at meeting. Contexts not really working. Blocks on a right all over the place. Perhaps need some new page layouts (?) or other piece of work with panels (?) to sort out.
&lt;/p&gt;
&lt;p&gt;
One page to start with is the Training page (and subsection). Ed to meet Trainers and their marketing consultant on 21/6.
&lt;/p&gt;
&lt;p&gt;
Jim please advise Ed what Jim needs to
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/264#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/326</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/326</guid>
        <title>#326: Usability changes as per the usability report</title>
        <pubDate>Mon, 12 Sep 2011 11:10:37 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Report has been circulated around ttech - to READ and then discuss - some will be phase 5 work, some will be the webmaster's responsibility...
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/326#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/384</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/384</guid>
        <title>#384: Enhance Project Profile Content Type and directory</title>
        <pubDate>Tue, 20 Dec 2011 23:25:32 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Laura to re-design IA and interface for admin and public profiles for project profile CT and directory.
&lt;/p&gt;
&lt;p&gt;
Considered as part of PSE Project, hence design in Jan, build in Feb 2012
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/384#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/520</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/520</guid>
        <title>#520: Session 443 config in settings.php</title>
        <pubDate>Fri, 15 Mar 2013 23:16:49 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
There is this warning displaying at &lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/reports/status"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/reports/status&lt;/a&gt;
&lt;/p&gt;
&lt;pre class="wiki"&gt;Settings.php is not setup correctly. With the current configuration of 443 Session module, the following lines must be in settings.php.
      if (!empty($_SERVER['HTTPS']) &amp;amp;&amp;amp; $_SERVER['HTTPS'] != 'off') {
        ini_set('session.cookie_secure', 1);
      }
&lt;/pre&gt;&lt;p&gt;
Based on the check of what is happening with cookies done on &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/371#comment:34" title="maintenance: Piwik Hosting (closed: fixed)"&gt;ticket:371#comment:34&lt;/a&gt; and &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/371#comment:36" title="maintenance: Piwik Hosting (closed: fixed)"&gt;ticket:371#comment:36&lt;/a&gt; things are currently working OK, session cookies do have the secure flag set, so I'm a bit confused by this warning message. I also think that the PHP suggested to add to settings.php looks perfectly sensible and should be included, I'm sure we did have it on the old server, however there are 33 settings.php files on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;wiki:PuffinServer&lt;/a&gt; and I'm not clear which one the live site uses.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/520#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/521</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/521</guid>
        <title>#521: MySQL Unsafe statement warnings in the daemon.log</title>
        <pubDate>Sat, 16 Mar 2013 09:46:57 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
I don't know if these matter?
&lt;/p&gt;
&lt;p&gt;
I found them when hunting for 502 errors.
&lt;/p&gt;
&lt;pre class="wiki"&gt;grep "Unsafe statement written to the binary log" /var/log/daemon.log | wc -l
343
&lt;/pre&gt;&lt;p&gt;
Some examples:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Mar 16 09:28:20 puffin mysqld: 130316  9:28:20 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE FROM notifications_event WHERE created &amp;lt; 1363426040 AND eid &amp;lt; (SELECT MIN(eid) FROM notifications_queue)
&lt;/pre&gt;&lt;pre class="wiki"&gt;Mar 16 05:52:12 puffin mysqld: 130316  5:52:12 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: INSERT INTO notifications_queue (uid, mdid, send_method, sid, module, eid, send_interval, language, cron, created, conditions) SELECT DISTINCT s.uid, s.mdid, s.send_method, s.sid, s.module, 61233, s.send_interval, s.language, s.cron, 1363413132, s.conditions FROM notifications s LEFT JOIN notifications_fields f ON s.sid = f.sid WHERE (s.status = 1) AND (s.event_type = 'node') AND (s.send_interval &amp;gt;= 0) AND ((f.field = 'nid' AND f.intval = 30718) OR (f.field = 'type' AND f.value = 'profile') OR (f.field = 'author' AND f.intval = 16908)) GROUP BY s.uid, s.mdid, s.send_method, s.sid, s.module, s.send_interval, s.
&lt;/pre&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/521#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/457</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/457</guid>
        <title>#457: Projects form - Enhance form entry</title>
        <pubDate>Thu, 08 Nov 2012 18:15:44 GMT</pubDate>
        
        <dc:creator>laura</dc:creator>

        <description>&lt;p&gt;
1 - Entry Form:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Set up new fields and permissions and groupings
&lt;/li&gt;&lt;li&gt;Enhance ‘helper’ texts and any links to other parts of TN listed on form to enhance usability and context.
&lt;/li&gt;&lt;li&gt;CSS and potential of custom templating/panels if needed for style and layouts
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/457#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/461</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/461</guid>
        <title>#461: Spam account war</title>
        <pubDate>Wed, 21 Nov 2012 16:19:10 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Aim:
&lt;/p&gt;
&lt;p&gt;
tell drupal (and server level stuff?) to sniff out and destroy spam accounts without them knowing we did it, and ban them from doing it again
&lt;/p&gt;
&lt;p&gt;
Wiki page:
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://wiki.transitionnetwork.org/Spam_accounts"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://wiki.transitionnetwork.org/Spam_accounts&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/461#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/606</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/606</guid>
        <title>#606: Site upgrade tasks -- pre-migration cleanup</title>
        <pubDate>Fri, 11 Oct 2013 12:00:13 GMT</pubDate>
        
        <dc:creator>jim</dc:creator>

        <description>&lt;p&gt;
This ticket is to track the issues left over from &lt;a class="assigned ticket" href="http://localhost:8080/trac/ticket/590" title="defect: Drupal performance improvements (assigned)"&gt;#590&lt;/a&gt; that need to be considered and tackled prior to migrating the site from D6 to D7 (or 8).
&lt;/p&gt;
&lt;p&gt;
Please feel free to add as needed, but sticky to the
&lt;/p&gt;
&lt;h2 id="CCleanup:Listoffeatureswedontreallyneed"&gt;C) Cleanup: List of features we don't really need&lt;/h2&gt;
&lt;p&gt;
Ed to add his items to following list... Need rational and alternative approaches for each.
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;C.1) Remove 'Geographic region' and related taxonomy and Hierarchical Select modules&lt;/strong&gt; 1 hour, low reward, low risk -- never really been used and is effectively a duplicate of the location field. let's kill it!
&lt;/li&gt;&lt;li&gt;&lt;strong&gt;C.2) Kill Microsites and the Forums&lt;/strong&gt; -- The handful of people using the CMS feature should be migrated to Open Atrium if they need such features.
&lt;/li&gt;&lt;li&gt;&lt;strong&gt;C.3) Remove forums&lt;/strong&gt; --  We could migrate the forum to a simpler setup (not using forum module) that leverages normal commenting, or even Disqus or other services to offload comments and moderation. Also encourage user-submitted ocontent and promote that if it's good or gets interesting debate.
&lt;/li&gt;&lt;/ul&gt;&lt;h2 id="DKeydevelopmenttasks"&gt;D) Key development tasks&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;D.1) All inline PHP must be moved to modules and features&lt;/strong&gt; -- This has great benefit for management, maintenance and developers. &lt;tt&gt;Eval()&lt;/tt&gt;uated code is much slower than PHP in files, especially since it can't be accelerated by APC or Zend Opcode cache... We have a few blocks and many views that are loaded from the database and evaluated. Ideally the blocks would be moved to the 'Transition Extras' module, and the views would be pushed into features. This work is good to do for maintainability and D7 upgrades, too. See: &lt;a class="ext-link" href="http://2bits.com/api/abuse-drupal-best-practices-your-own-peril-poor-performance.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://2bits.com/api/abuse-drupal-best-practices-your-own-peril-poor-performance.html&lt;/a&gt; and &lt;a class="ext-link" href="http://2bits.com/articles/free-your-content-php-moving-php-code-out-blocks-views-and-nodes.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://2bits.com/articles/free-your-content-php-moving-php-code-out-blocks-views-and-nodes.html&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;ul&gt;&lt;li&gt;&lt;strong&gt;D.2) Build in ESI (Edge Side Includes) support from the outset, ensure Drupal renders only what it needs to &lt;/strong&gt; -- BOA packages the &lt;a class="ext-link" href="https://drupal.org/project/esi"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;ESI (Edge Side Includes integration) module&lt;/a&gt;, which makes NginX cache the whole page (as it does now), but also for user-logged in pages (which it does for 5 seconds since the page data changes). This means Drupal renders the ESI component (blocks, panels panes) that are have user-specific data in. Potential boost quickly, but will need time to tweak settings to get best from this across whole site. See &lt;a class="ext-link" href="https://tech.transitionnetwork.org/trac/ticket/590#comment:4"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;comments in 4 &amp;amp; 5 below for discussion&lt;/a&gt;&lt;del&gt;, should be done after proposal F, above&lt;/del&gt;.
&lt;/li&gt;&lt;/ul&gt;&lt;h2 id="EKeyeditorialtasks"&gt;E) Key editorial tasks&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;E.1) More Taxonomy cleanup&lt;/strong&gt; -- try to merge terms with the same names, clear out spammy terms, general spit-and-polish. Ed plus team of busy interns to do this when the time is right.
&lt;/li&gt;&lt;/ul&gt;&lt;h2 id="Zoldstuffforreferencetasksfrom590renderedpointlessbymove"&gt;Z) old stuff for reference; tasks from &lt;a class="assigned ticket" href="http://localhost:8080/trac/ticket/590" title="defect: Drupal performance improvements (assigned)"&gt;#590&lt;/a&gt; rendered pointless by move&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;&lt;strong&gt;Z.1) Find Variable table writes and kill them&lt;/strong&gt; -- seeing plenty of SELECT * FROM variable calls, which imply a cache clear due to a variable being set. In normal use variables shouldn't be set (admin screens tend to do this), so I'd like to try to see what module it causing this and patch/remove it. Will need to run &lt;tt&gt;grep -R "variable_set() * &amp;gt; ~/static/variable_set-calls.txt" in the {{{sites/all&lt;/tt&gt; directory to generate a list, then trawl though it to find candidates/bad modules practice.
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/606#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/671</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/671</guid>
        <title>#671: Replace core Search module with Apache Solr</title>
        <pubDate>Sat, 11 Jan 2014 21:11:14 GMT</pubDate>
        
        <dc:creator>jim</dc:creator>

        <description>&lt;p&gt;
&lt;strong&gt;Issue &amp;amp; background&lt;/strong&gt;
During work on &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/610" title="defect: Aegir database intensive (migrate, clone, restore) tasks hang for larger ... (closed: fixed)"&gt;#610&lt;/a&gt;, it was discovered that of a 1/4GB database dump for TN.org, ~80% (180Mb) of it was related to the Drupal 6 core Search module.
&lt;/p&gt;
&lt;p&gt;
It's worth noting &lt;a class="ext-link" href="https://tech.transitionnetwork.org/trac/ticket/516#comment:3"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;this&lt;/a&gt; was &lt;a class="ext-link" href="https://tech.transitionnetwork.org/trac/ticket/516#comment:6"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;raised&lt;/a&gt; when we migrated the site to the Puffin server in March 2013, but it's generally the case that the core Search module does not scale easily beyond a few thousand nodes.
&lt;/p&gt;
&lt;p&gt;
www.transitionnetwork.org has 23,803 nodes at time of writing -- this is probably approaching the sensible limit of the core module's capability.
&lt;/p&gt;
&lt;p&gt;
Note also, any future D7 or D8 version of the site would also hugely benefit from using Solr, so the server config part is time well spent.
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;Proposed solution&lt;/strong&gt;
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;Add the Apache Solr option to BOA, re-run the installer to get it installed and configured automatically.
&lt;/li&gt;&lt;li&gt;Add the &lt;a class="ext-link" href="https://drupal.org/project/apachesolr"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;ApacheSolr module&lt;/a&gt; and any related required modules to the TN D6 makefile -- it's not clear if the 6.x-3.x branch or 6.x-1.x branch is the right choice at present.
&lt;/li&gt;&lt;li&gt;Build a new platform containing these modules, migrate a clone of STG to it.
&lt;/li&gt;&lt;li&gt;Enable the modules, configure them, disable core Search.
&lt;/li&gt;&lt;li&gt;Create a feature that wraps up config for Solr and required modules. Add to Git, add reference to feature to makefile
&lt;/li&gt;&lt;li&gt;Test, tweak, repeat 3 &amp;amp; 4 &amp;amp; 5 as needed.
&lt;/li&gt;&lt;li&gt;Migrate PROD to the new plaform, enabled feature, index site.
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
This could be parked until D7/8 migration, or not... Ed's call.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/671#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/519</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/519</guid>
        <title>#519: Fixing various URL in the Database</title>
        <pubDate>Fri, 15 Mar 2013 13:47:21 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This page:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="http://transitionnetwork.org/support/what-transition-initiative"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://transitionnetwork.org/support/what-transition-initiative&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Contains this HTML:
&lt;/p&gt;
&lt;pre class="wiki"&gt;&amp;lt;p&amp;gt;&amp;lt;img alt="TransitionSantaCruz" src="http://transitionsc.org/sites/www.transitionnetwork.org/files/pixture_reloaded_logo.png" align="right" height="69" width="150"&amp;gt;&amp;lt;/p&amp;gt;
&lt;/pre&gt;&lt;p&gt;
The image is a 404:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="http://transitionsc.org/sites/www.transitionnetwork.org/files/pixture_reloaded_logo.png"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://transitionsc.org/sites/www.transitionnetwork.org/files/pixture_reloaded_logo.png&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
The correct location for the image is:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="http://transitionsc.org/sites/default/files/pixture_reloaded_logo.png"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://transitionsc.org/sites/default/files/pixture_reloaded_logo.png&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Looking at the Internet Archive this was correct back in October 2012,
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="http://web.archive.org/web/20121022030350/http://www.transitionnetwork.org/support/what-transition-initiative"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://web.archive.org/web/20121022030350/http://www.transitionnetwork.org/support/what-transition-initiative&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Their munged HTML contains the correct URL:
&lt;/p&gt;
&lt;pre class="wiki"&gt;&amp;lt;p&amp;gt;&amp;lt;a href="/web/20121022030350/http://transitionsc.org/sites/default/files/pixture_reloaded_logo.png" class="colorbox initColorbox-processed cboxElement"&amp;gt;
&lt;/pre&gt;&lt;p&gt;
It appears to me that an edit must have been done on the database something like:
&lt;/p&gt;
&lt;pre class="wiki"&gt;s;/sites/default/files/;/sites/www.transitionnetwork.org/files/;
&lt;/pre&gt;&lt;p&gt;
There might well be other URLs to other Drupal sites that were changed when they shouldn't have been?
&lt;/p&gt;
&lt;p&gt;
I have had a quick look at the database dump and couldn't find any examples of this problem, but there are 113 lines to check:
&lt;/p&gt;
&lt;pre class="wiki"&gt;grep "sites/www.transitionnetwork.org/files" /var/backups/mysql/sqldump/transitionnetwor.sql | wc -l
113
&lt;/pre&gt;&lt;p&gt;
I did notice that there are a lot of URLs in the database like this:
&lt;/p&gt;
&lt;pre class="wiki"&gt;src=\"http://www.transitionnetwork.org/sites/www.transitionnetwork.org/files/uploaded/u5857/Map-TransitionNetworkOffice.jpg\"
&lt;/pre&gt;&lt;p&gt;
And
&lt;/p&gt;
&lt;pre class="wiki"&gt;src=\"https://www.transitionnetwork.org/sites/www.transitionnetwork.org/files/uploaded/u4/transition%20companion%20cover.jpg\"
&lt;/pre&gt;&lt;p&gt;
Both the above links would be better starting with &lt;tt&gt;/&lt;/tt&gt; or &lt;tt&gt;//www.transitionnetwork.org/&lt;/tt&gt; as this would avoid people getting HTTPS content when using HTTP and also getting HTTP content when using HTTPS.
&lt;/p&gt;
&lt;p&gt;
I think it would be worth putting the site into maintenance mode, doing a dump of the database, checking these 113 lines for issues like those above, correcting them all and then reinserting the data, however this would need to be done at a suitable time.
&lt;/p&gt;
&lt;p&gt;
I'd be happy to do this task. Ed, Jim, any thoughts about when would be a good time to do it?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/519#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/626</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/626</guid>
        <title>#626: Add redirect from an old CMS to a new URL</title>
        <pubDate>Wed, 20 Nov 2013 12:11:14 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Can Ed add a redirect from:
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/cms/haddenham"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/cms/haddenham&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
to another URL easily? Or does he need to ask Chris to do it?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/626#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/644</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/644</guid>
        <title>#644: AWstats Nginx config breaks aegir</title>
        <pubDate>Mon, 09 Dec 2013 16:46:05 GMT</pubDate>
        
        <dc:creator>jim</dc:creator>

        <description>&lt;p&gt;
Since the last update we've had a silent ngnix error that means &lt;a class="ext-link" href="http://tn.puffin.webarch.net"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://tn.puffin.webarch.net&lt;/a&gt; was not available.
&lt;/p&gt;
&lt;p&gt;
I restarted nginx and got:
&lt;/p&gt;
&lt;pre class="wiki"&gt;[  ok  ] Stopping Nginx Server...:
[ .... ] Starting Nginx Server...:nginx: [emerg] "log_format" directive is not allowed here in /etc/nginx/nginx.conf:28
&lt;/pre&gt;&lt;p&gt;
Which equates to the AWstats entry which is now commented out per:
&lt;/p&gt;
&lt;pre class="wiki"&gt;# log for awstats
#log_format apache '$remote_addr - $remote_user [$time_local] "$request" '
#                   '$status $body_bytes_sent "$http_referer" '
#                   '"$http_user_agent"';
#access_log         /var/log/nginx/awstats.log apache;
&lt;/pre&gt;&lt;p&gt;
I/we need access to aegir more than AWStats, so I've commented out the lines above and restarted nginx. Aegir is back and working well.
&lt;/p&gt;
&lt;p&gt;
This ticket is to find the correct log_format for modern nginx versions and reinstate AWstats -- assigning to Chris as a low priority thing.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/644#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/676</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/676</guid>
        <title>#676: Alternative to Skype for TTech Meetings</title>
        <pubDate>Tue, 14 Jan 2014 13:33:51 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Jim has pointed out that:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Skype costs us 15-30 minutes of grinding pain every time we do this!
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
So what are the alternatives and what are our requirements?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/676#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/716</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/716</guid>
        <title>#716: Heartbleed</title>
        <pubDate>Wed, 09 Apr 2014 08:53:58 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Following on from &lt;a class="new ticket" href="http://localhost:8080/trac/ticket/692#comment:18" title="maintenance: Debian Updates (new)"&gt;ticket:692#comment:18&lt;/a&gt; we should undertake the steps Drupal have taken: &lt;a class="ext-link" href="https://drupal.org/news/2014-04-08-security-update"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://drupal.org/news/2014-04-08-security-update&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/716#changelog</comments>
    </item>
 </channel>
</rss>