<?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;milestone=Maintenance&amp;group=resolution&amp;desc=1&amp;order=priority</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;milestone=Maintenance&amp;group=resolution&amp;desc=1&amp;order=priority</link>
    </image>
    <generator>Trac 0.12.5</generator>
    <item>
        <link>http://localhost:8080/trac/ticket/546</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/546</guid>
        <title>#546: Trac documentation</title>
        <pubDate>Wed, 08 May 2013 18:47:09 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Better documentation of things like how to set billing times etc
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/546#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/597</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/597</guid>
        <title>#597: Default owner for tickets</title>
        <pubDate>Tue, 17 Sep 2013 08:04:58 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Ben reported that the default owner for tickets is laura and that this should be changed.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/597#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/618</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/618</guid>
        <title>#618: Migrate Penguin and Parrot to the ZFS fileserver</title>
        <pubDate>Fri, 15 Nov 2013 09:37:36 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Since &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;wiki:PuffinServer&lt;/a&gt; has been running from the ZFS fileserver, see &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/593" title="maintenance: Migrating Puffin to a ZFS file server (closed: fixed)"&gt;ticket:593&lt;/a&gt;, it has been performing better -- we should also migrate &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PenguinServer"&gt;wiki:PenguinServer&lt;/a&gt; and &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;wiki:ParrotServer&lt;/a&gt; to the ZFS server prior to upgrading them to Debian Wheezy on &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/535" title="maintenance: Upgrade Puffin, Penguin and Parrot from Debian Squeeze to Wheezy (closed: fixed)"&gt;ticket:535&lt;/a&gt;.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/618#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/487</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/487</guid>
        <title>#487: robots.txt files for development sites</title>
        <pubDate>Tue, 29 Jan 2013 13:24:35 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
All the sites other than www.transitionnetwork.org on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;wiki:PuffinServer&lt;/a&gt; should have a robots.txt file to exclude them from being crawled and indexed to prevent the development versions of sites being included in search results.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/487#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/538</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/538</guid>
        <title>#538: intransitionmovie.com checks and updates</title>
        <pubDate>Tue, 30 Apr 2013 20:02:03 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The &lt;a class="ext-link" href="http://www.intransitionmovie.com/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.intransitionmovie.com/&lt;/a&gt; site has been migrated to &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;wiki:ParrotServer&lt;/a&gt;, the DNS might not have yet updated for everybody.
&lt;/p&gt;
&lt;p&gt;
Laura -- could you check that the site is working OK if you get a chance, especially the ecommerce elements?
&lt;/p&gt;
&lt;p&gt;
There are some outstanding updates, &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; is version 3.3.2 need updating to 3.5.1 and there are 12 plugins with updates available:
&lt;/p&gt;
&lt;pre class="wiki"&gt;18 installed plugins:
 UA affiliates
 UA affiliates-woocommerce-light
 UA akismet
  A backupwordpress
 UI bad-behavior
 UA bwp-minify
  A contact-form-7
 UA event-o-matic
  A transposh-translation-filter-for-wordpress
 UA usernoise
  A woocommerce
 UA woocommerce-export-csv
  A woocommerce-currency-converter
 UA woocommerce-dynamic-pricing
  A woocommerce-delivery-notes
 UA woocommerce-shipping-table-rate
 UA wp-customer-reviews
 UI wp-super-cache
Legend: A = Active, I = Inactive, U = Update Available
&lt;/pre&gt;&lt;p&gt;
I'm happy to do all these updates but I wouldn't know what exactly to check to see that the updates don't break anything -- would Laura be able to help with a quick check that updates haven't broken anything?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/538#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/542</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/542</guid>
        <title>#542: Parrot RAM</title>
        <pubDate>Wed, 01 May 2013 20:35:50 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
I'm concerned that &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;wiki:ParrotServer&lt;/a&gt; might not be able to cope with load spikes due to it only having 1GB of RAM, these are the Munin graphs we need to key an eye on:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://penguin.transitionnetwork.org/munin/transitionnetwork.org/parrot.transitionnetwork.org/swap.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;swap&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://penguin.transitionnetwork.org/munin/transitionnetwork.org/parrot.transitionnetwork.org/memory.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;memory usage&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://penguin.transitionnetwork.org/munin/transitionnetwork.org/parrot.transitionnetwork.org/multips_memory.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;apache2 and mysql memory usage&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
If the server runs out of RAM it will basically stop responding.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/542#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/543</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/543</guid>
        <title>#543: Puffin Load Spike</title>
        <pubDate>Fri, 03 May 2013 20:48:16 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Puffin just had a massive load spike up to 65 and then it calmed down and it's up in the 70's again:
&lt;/p&gt;
&lt;pre class="wiki"&gt;uptime
 21:46:43 up 91 days,  3:01,  4 users,  load average: 73.45, 30.76, 28.09
&lt;/pre&gt;&lt;p&gt;
I'm trying to find the cause, it's making the TN site unresponsive.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/543#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/577</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/577</guid>
        <title>#577: Transition Streets Wordpress Migration</title>
        <pubDate>Tue, 06 Aug 2013 21:28:25 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This is a ticket to document the migration of the Transition Totnes &lt;a class="ext-link" href="http://www.transitionstreets.org.uk/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.transitionstreets.org.uk/&lt;/a&gt; &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;wiki:WordPress&lt;/a&gt; site to &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;wiki:ParrotServer&lt;/a&gt;.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/577#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/581</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/581</guid>
        <title>#581: Remove 'add to newsletter' option for site editors/admins</title>
        <pubDate>Mon, 26 Aug 2013 13:24:17 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Please remove the option for site editors/admins to 'add this to the newsletter' (which would send it to the newsletter nodequeue). Please also for now make the newsletter nodequeue non-active.
&lt;/p&gt;
&lt;p&gt;
It's been confusing for staff members, and was for the simmplemail service really, so we're going to trial using a google doc for staff to add their stories to the newsletter instead.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/581#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/586</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/586</guid>
        <title>#586: New Relic Monitoring for BOA</title>
        <pubDate>Thu, 05 Sep 2013 08:35:17 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This is a ticket to document the consideration, and possible installation, of &lt;a class="ext-link" href="https://newrelic.com/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://newrelic.com/&lt;/a&gt; on the &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;PuffinServer&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/586#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/588</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/588</guid>
        <title>#588: RSS feed caching</title>
        <pubDate>Fri, 06 Sep 2013 09:43:57 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
At the meeting on 5th September &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/585" title="maintenance: TTech Meeting 5th September 2013 (closed: fixed)"&gt;ticket:585&lt;/a&gt; one thing we discussed was that:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
The biggest single source of bandwidth by URL is Rob's RSS feed, 34.5GB of data, 150k hits. This represents half the total site data transfer, the RSS files is 0.4MB but will hopefully be mostly served gzipped at 0.1MB.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
This ticket is to follow up on that -- are the RSS feeds served directly by Nginx?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/588#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/608</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/608</guid>
        <title>#608: User profile pictures are too big</title>
        <pubDate>Mon, 14 Oct 2013 08:37:38 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
The user profile pictures on the user profile nodes are too big.
&lt;/p&gt;
&lt;p&gt;
e.g.
&lt;a class="ext-link" href="https://transitionnetwork.org/people/tina-clarke"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://transitionnetwork.org/people/tina-clarke&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Please investigate and restrain them into a suitable maximum size
&lt;/p&gt;
&lt;p&gt;
NB: Ed is keeping a number of small UI-ish tickets back for Ben to do in a lump when we've built up enough so don't do anything yet.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/608#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/610</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/610</guid>
        <title>#610: Aegir database intensive (migrate, clone, restore) tasks hang for larger sites</title>
        <pubDate>Tue, 15 Oct 2013 10:18:59 GMT</pubDate>
        
        <dc:creator>jim</dc:creator>

        <description>&lt;p&gt;
Large sites (TN.org and variants) will simply not complete their migrate, clone or restore tasks in Aegir.
&lt;/p&gt;
&lt;p&gt;
However, smaller sites are fine, and all tasks work for them.
&lt;/p&gt;
&lt;p&gt;
The process largely completes -- codebase installs, database is cloned, symlinks for sites aliases and files created... BUT the process never completes in Aegir, so the final steps of switching a site's served location never occurs.
&lt;/p&gt;
&lt;p&gt;
Useful links/comments in this issue:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://tech.transitionnetwork.org/trac/ticket/610#comment:30"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Tests of Aegir commands&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://drupal.org/node/984256"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://drupal.org/node/984256&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://omega8.cc/aegir-task-fails-or-spins-forever-126"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;How to fix: Aegir task fails or spins forever&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/610#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/613</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/613</guid>
        <title>#613: Parrot mysql console errors</title>
        <pubDate>Mon, 04 Nov 2013 09:48:35 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
I connected to the &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;wiki:ParrotServer&lt;/a&gt; &lt;a class="wiki" href="http://localhost:8080/trac/wiki/XenShell"&gt;wiki:XenShell&lt;/a&gt; to check the bandwidth usage and there was the following output, we should try to track down the cause of this:
&lt;/p&gt;
&lt;pre class="wiki"&gt;parrot login: [41569.058444] hrtimer: interrupt took 59422559 ns
[442920.164115] INFO: task mysqld:3522 blocked for more than 120 seconds.
[442920.164133] "echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[442920.164142] mysqld        D ffff880003755c40     0  3522    711 0x00000000
[442920.164153]  ffff8800bfa68e20 0000000000000282 ffff8800565fb9e8 ffff8800565fb9e4
[442920.164165]  00000000000157c8 0000000000000000 000000000000f9e0 ffff8800565fbfd8
[442920.164175]  00000000000157c0 00000000000157c0 ffff88000180c6a0 ffff88000180c998
[442920.164185] Call Trace:
[442920.164200]  [&amp;lt;ffffffff8110fb96&amp;gt;] ? sync_buffer+0x0/0x40
[442920.164211]  [&amp;lt;ffffffff8130de82&amp;gt;] ? io_schedule+0x73/0xb7
[442920.164219]  [&amp;lt;ffffffff8110fbd1&amp;gt;] ? sync_buffer+0x3b/0x40
[442920.164228]  [&amp;lt;ffffffff8130f142&amp;gt;] ? _spin_unlock_irqrestore+0xd/0xe
[442920.164237]  [&amp;lt;ffffffff8130e292&amp;gt;] ? __wait_on_bit_lock+0x3f/0x84
[442920.164246]  [&amp;lt;ffffffff8110fb96&amp;gt;] ? sync_buffer+0x0/0x40
[442920.164253]  [&amp;lt;ffffffff8130e342&amp;gt;] ? out_of_line_wait_on_bit_lock+0x6b/0x77
[442920.164262]  [&amp;lt;ffffffff81066360&amp;gt;] ? wake_bit_function+0x0/0x23
[442920.164271]  [&amp;lt;ffffffff8110ffc3&amp;gt;] ? sync_dirty_buffer+0x29/0x93
[442920.164286]  [&amp;lt;ffffffffa001be04&amp;gt;] ? journal_dirty_data+0xd1/0x1b0 [jbd]
[442920.164301]  [&amp;lt;ffffffffa0032f4c&amp;gt;] ? ext3_journal_dirty_data+0xf/0x34 [ext3]
[442920.164312]  [&amp;lt;ffffffffa00313f5&amp;gt;] ? walk_page_buffers+0x65/0x8b [ext3]
[442920.164322]  [&amp;lt;ffffffffa0032f71&amp;gt;] ? journal_dirty_data_fn+0x0/0x13 [ext3]
[442920.164333]  [&amp;lt;ffffffffa0034a93&amp;gt;] ? ext3_ordered_write_end+0x73/0x10f [ext3]
[442920.164343]  [&amp;lt;ffffffff810b648a&amp;gt;] ? generic_file_buffered_write+0x18d/0x278
[442920.164352]  [&amp;lt;ffffffff810b6926&amp;gt;] ? __generic_file_aio_write+0x25f/0x293
[442920.164361]  [&amp;lt;ffffffff810b69b3&amp;gt;] ? generic_file_aio_write+0x59/0x9f
[442920.164369]  [&amp;lt;ffffffff810f0316&amp;gt;] ? do_sync_write+0xce/0x113
[442920.164377]  [&amp;lt;ffffffff81066332&amp;gt;] ? autoremove_wake_function+0x0/0x2e
[442920.164385]  [&amp;lt;ffffffff8130f6fa&amp;gt;] ? error_exit+0x2a/0x60
[442920.164394]  [&amp;lt;ffffffff8101251d&amp;gt;] ? retint_restore_args+0x5/0x6
[442920.164403]  [&amp;lt;ffffffff8102de30&amp;gt;] ? pvclock_clocksource_read+0x3a/0x8b
[442920.164411]  [&amp;lt;ffffffff810f0c68&amp;gt;] ? vfs_write+0xa9/0x102
[442920.164419]  [&amp;lt;ffffffff810f0d7d&amp;gt;] ? sys_write+0x45/0x6e
[442920.164427]  [&amp;lt;ffffffff81011b42&amp;gt;] ? system_call_fastpath+0x16/0x1b
[442920.164435] INFO: task mysqld:21061 blocked for more than 120 seconds.
[442920.164441] "echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[442920.164448] mysqld        D ffff8800018b0e20     0 21061    711 0x00000000
[442920.164457]  ffff8800018b0e20 0000000000000282 ffffffff8100c426 ffffffff8100e233
[442920.164469]  ffff880003755d10 0000000000000002 000000000000f9e0 ffff8800bdde3fd8
[442920.164480]  00000000000157c0 00000000000157c0 ffff8800bd9462e0 ffff8800bd9465d8
[442920.164492] Call Trace:
[442920.164498]  [&amp;lt;ffffffff8100c426&amp;gt;] ? pfn_to_mfn+0xe/0x22
[442920.164506]  [&amp;lt;ffffffff8100e233&amp;gt;] ? arbitrary_virt_to_machine+0x28/0x73
[442920.164515]  [&amp;lt;ffffffff8110fb96&amp;gt;] ? sync_buffer+0x0/0x40
[442920.164523]  [&amp;lt;ffffffff8106ce4a&amp;gt;] ? timekeeping_get_ns+0xe/0x2e
[442920.164531]  [&amp;lt;ffffffff8110fb96&amp;gt;] ? sync_buffer+0x0/0x40
[442920.164538]  [&amp;lt;ffffffff8130de82&amp;gt;] ? io_schedule+0x73/0xb7
[442920.164545]  [&amp;lt;ffffffff8110fbd1&amp;gt;] ? sync_buffer+0x3b/0x40
[442920.164554]  [&amp;lt;ffffffff8130f142&amp;gt;] ? _spin_unlock_irqrestore+0xd/0xe
[442920.164561]  [&amp;lt;ffffffff8130e292&amp;gt;] ? __wait_on_bit_lock+0x3f/0x84
[442920.164569]  [&amp;lt;ffffffff8110fb96&amp;gt;] ? sync_buffer+0x0/0x40
[442920.164576]  [&amp;lt;ffffffff8130e342&amp;gt;] ? out_of_line_wait_on_bit_lock+0x6b/0x77
[442920.164584]  [&amp;lt;ffffffff81066360&amp;gt;] ? wake_bit_function+0x0/0x23
[442920.164592]  [&amp;lt;ffffffff8110ffc3&amp;gt;] ? sync_dirty_buffer+0x29/0x93
[442920.164600]  [&amp;lt;ffffffffa001be04&amp;gt;] ? journal_dirty_data+0xd1/0x1b0 [jbd]
[442920.164611]  [&amp;lt;ffffffffa0032f4c&amp;gt;] ? ext3_journal_dirty_data+0xf/0x34 [ext3]
[442920.164622]  [&amp;lt;ffffffffa00313f5&amp;gt;] ? walk_page_buffers+0x65/0x8b [ext3]
[442920.164632]  [&amp;lt;ffffffffa0032f71&amp;gt;] ? journal_dirty_data_fn+0x0/0x13 [ext3]
[442920.164643]  [&amp;lt;ffffffffa0034a93&amp;gt;] ? ext3_ordered_write_end+0x73/0x10f [ext3]
[442920.164652]  [&amp;lt;ffffffff810b648a&amp;gt;] ? generic_file_buffered_write+0x18d/0x278
[442920.164661]  [&amp;lt;ffffffff810b6926&amp;gt;] ? __generic_file_aio_write+0x25f/0x293
[442920.164670]  [&amp;lt;ffffffff810b69b3&amp;gt;] ? generic_file_aio_write+0x59/0x9f
[442920.164677]  [&amp;lt;ffffffff810f0316&amp;gt;] ? do_sync_write+0xce/0x113
[442920.164685]  [&amp;lt;ffffffff81066332&amp;gt;] ? autoremove_wake_function+0x0/0x2e
[442920.164693]  [&amp;lt;ffffffff810f0c68&amp;gt;] ? vfs_write+0xa9/0x102
[442920.164700]  [&amp;lt;ffffffff810f0d18&amp;gt;] ? sys_pwrite64+0x57/0x77
[442920.164706]  [&amp;lt;ffffffff81011b42&amp;gt;] ? system_call_fastpath+0x16/0x1b
&lt;/pre&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/613#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/642</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/642</guid>
        <title>#642: Trac "databasee  is locked" errors in /var/log/messages</title>
        <pubDate>Sat, 07 Dec 2013 13:46:43 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
I have just noticed these errors in &lt;tt&gt;/var/log/messages&lt;/tt&gt; on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PenguinServer"&gt;wiki:PenguinServer&lt;/a&gt;:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Dec  1 23:09:00 penguin ﻿&amp;lt;11&amp;gt;Trac[chrome] ERROR: Error with navigation contributor TimingEstimationAndBillingPage: OperattionalError: database is locked
Dec  1 23:09:00 penguin ﻿&amp;lt;11&amp;gt;Trac[chrome] ERROR: Error with navigation contributor AdminModule: OperationalError: databasse is locked
Dec  1 23:09:00 penguin ﻿&amp;lt;11&amp;gt;Trac[chrome] ERROR: Error with navigation contributor SearchModule: OperationalError: databaase is locked
Dec  1 23:09:00 penguin ﻿&amp;lt;11&amp;gt;Trac[chrome] ERROR: Error with navigation contributor QueryModule: OperationalError: databasse is locked
Dec  1 23:09:00 penguin ﻿&amp;lt;11&amp;gt;Trac[chrome] ERROR: Error with navigation contributor ReportModule: OperationalError: databaase is locked
Dec  1 23:09:00 penguin ﻿&amp;lt;11&amp;gt;Trac[chrome] ERROR: Error with navigation contributor RoadmapModule: OperationalError: databbase is locked
Dec  1 23:09:00 penguin ﻿&amp;lt;11&amp;gt;Trac[chrome] ERROR: Error with navigation contributor TicketModule: OperationalError: databaase is locked
Dec  1 23:09:00 penguin ﻿&amp;lt;11&amp;gt;Trac[chrome] ERROR: Error with navigation contributor TimelineModule: OperationalError: dataabase is locked
Dec  1 23:09:00 penguin ﻿&amp;lt;11&amp;gt;Trac[chrome] ERROR: Error with navigation contributor BrowserModule: OperationalError: databbase is locked
Dec  1 23:09:00 penguin ﻿&amp;lt;11&amp;gt;Trac[chrome] ERROR: Error with navigation contributor WikiModule: OperationalError: databaseeis locked
&lt;/pre&gt;&lt;p&gt;
There are lots more of these, including some from this morning.
&lt;/p&gt;
&lt;p&gt;
Trac still seems to be working OK so I don't know how significant they are.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/642#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/663</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/663</guid>
        <title>#663: De-commission the PSE</title>
        <pubDate>Wed, 18 Dec 2013 17:44:43 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
We are wrapping up the PSE to simplify our web traffic, codebase and support requirements before we move to TNv3.
&lt;/p&gt;
&lt;p&gt;
Ed has informed all the PSE alpha triallists twice and asked them to remove their widgets. About half have. Others say they will. So we can remove the service any time from now on.
&lt;/p&gt;
&lt;p&gt;
Ed has UNpublished the following pages:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;/pse/create
&lt;/li&gt;&lt;li&gt;/pse/about
&lt;/li&gt;&lt;li&gt;/pse/faq
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Jim - time to de-commission the service in a suitable way. Wrap this puppy up and turn it off. Please outline what you are going to do on this ticket and then do it.
&lt;/p&gt;
&lt;p&gt;
Ed suggests this is work for January 2014.
&lt;/p&gt;
&lt;p&gt;
Sam, Chris, fyi and any other changes needed?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/663#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/668</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/668</guid>
        <title>#668: Wagn transition_mod</title>
        <pubDate>Sat, 11 Jan 2014 08:52:25 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Email from Ethan via Tom:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
I was doing some work on wagn mods today and I realized that I'd created a mod (as in "modification" or "module", whichever you like) for the transition site that probably never survived the move to the new server.
&lt;/p&gt;
&lt;p&gt;
Looking at &lt;a class="ext-link" href="https://patterns.transitionresearchnetwork.org/Building_Resilience"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://patterns.transitionresearchnetwork.org/Building_Resilience&lt;/a&gt; confirmed this for me.  The confidence shows up as the words "2 stars" rather than actual star images.  That's one thing the mod does.  The other has to do with reducing visual redundancy (recurring names) in pattern summaries.
&lt;/p&gt;
&lt;p&gt;
I've attached the mod file here.  Unless you've gotten creative with your configuration, you should be able to stick this file in local/mods and restart the server and have that fixed. Let me know if any of this doesn't make sense.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/668#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/670</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/670</guid>
        <title>#670: Roll back performance customisations and use stock BOA settings where possible</title>
        <pubDate>Sat, 11 Jan 2014 20:51:30 GMT</pubDate>
        
        <dc:creator>jim</dc:creator>

        <description>&lt;p&gt;
&lt;strong&gt;Issue&lt;/strong&gt;
Given so much has changed since the initial issues on the server, I now strongly recommend reverting all settings changes that do not add features back to stock BOA settings after the next BOA release.
&lt;/p&gt;
&lt;p&gt;
These would include all MySQL, PHP, FPM, Redis and other settings that have been for performance reasons, or to combat the situation where there was hardware/IO issues with the underlying server. I'm most interested in FPM and MySQL settings.
&lt;/p&gt;
&lt;p&gt;
The next version of BOA will include some improvements we need (&lt;a class="ext-link" href="https://tech.transitionnetwork.org/trac/ticket/629"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;see 629: Upgrades to BOA&lt;/a&gt; which should handle load on our server with a lot of CPU cores. With this in place we'll be able to revert more easily to stock settings.
&lt;/p&gt;
&lt;p&gt;
&lt;em&gt;Rationale&lt;/em&gt;
I'm not talking about rolling back changes that provide us with features or mission-critical capabilities, just the changes to the subsystems I list above for performance reasons.
&lt;/p&gt;
&lt;p&gt;
It's my belief that these enhancements no longer match the needs of the server since the changes to filesystem and underlying hardware fixes have been completed. They also represent an ongoing risk around updates, future planning -- plus it's possible they might mean Puffin's web services need more memory than it otherwise would, costing TN more than it should need to spend on hardware.
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;Proposed solution&lt;/strong&gt;
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;Await the next version of BOA, and setup the enhanced load settings per the documentation.
&lt;/li&gt;&lt;li&gt;Revert all other changes to conf files for MySQL, PHP, FPM, Redis that do not add a feature or are not mission-critical.
&lt;/li&gt;&lt;li&gt;Review &lt;tt&gt;/root/.barracuda.cnf&lt;/tt&gt; and turn off any overrides and customisations we don't now need as a result of 2).
&lt;/li&gt;&lt;li&gt;Run the BOA &lt;tt&gt;BOND.sh&lt;/tt&gt; script to do the tuning of the server appropriate to the memory requirements. This will tune for the current levels on first pass.
&lt;/li&gt;&lt;li&gt;Review Munin and site performance. If we need to make any tweaks then we can do a minimal set as required -- keeping an eye on memory usage.
&lt;/li&gt;&lt;li&gt;Once a few days have gone by I would hope that the overall memory use will be lower, OR with more cached data. At this point we can either re-run the barracuda installer with the &lt;tt&gt;_RESERVED_RAM&lt;/tt&gt; set to 1-4 Gb, or simply reduce the memory available to Puffin.
&lt;/li&gt;&lt;li&gt;Repeat from 4, using BOND.sh to optimise for the new memory footprint.
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
Clearly, it's possible no memory savings can be made, or just 1Gb or so is sensible. Either way, rolling back the changes made for a system that has changed immensely is worth attempting to compare current (tweaked) performance to the stock system. Since current settings are all documented and can be backed up, we should be able to test this with no risk and the ability to roll back as needed.
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;Next steps&lt;/strong&gt;
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Chris and Ed to give their thoughts.
&lt;/li&gt;&lt;li&gt;Ed to green-light before we proceed in too much detail or take any action.
&lt;/li&gt;&lt;li&gt;Chris and Jim to establish the changes and outcomes.
&lt;/li&gt;&lt;li&gt;Chris, Jim and whoever to do the new optimisation process.
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/670#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/673</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/673</guid>
        <title>#673: Install mosh - the mobile shell</title>
        <pubDate>Mon, 13 Jan 2014 11:27:40 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The mobile shell enables terminal connections to stay up when using really bad connections, for example on a train, see:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="http://mosh.mit.edu/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://mosh.mit.edu/&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/673#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/682</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/682</guid>
        <title>#682: Create Trac &amp; Wiki account for Paul</title>
        <pubDate>Wed, 22 Jan 2014 12:39:18 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi it looks like i@… will be joining us to pick up some of Jim's role as he moves on.
&lt;/p&gt;
&lt;p&gt;
Chris could you create a trac &amp;amp; Wiki account for him please?
&lt;/p&gt;
&lt;p&gt;
His email is; i@…
&lt;/p&gt;
&lt;p&gt;
Thanks
&lt;/p&gt;
&lt;p&gt;
Sam
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/682#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/683</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/683</guid>
        <title>#683: Create Aegir account for Paul</title>
        <pubDate>Wed, 22 Jan 2014 12:42:48 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Jim
&lt;/p&gt;
&lt;p&gt;
It looks like i@… will be joining us to pick up some of your work.
&lt;/p&gt;
&lt;p&gt;
Could you create an Aegir account for him please?
&lt;/p&gt;
&lt;p&gt;
I was also wondering about the Transition Network Github repo, do we need to do anything to hand that over?
&lt;/p&gt;
&lt;p&gt;
Thanks
&lt;/p&gt;
&lt;p&gt;
Sam
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/683#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/696</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/696</guid>
        <title>#696: Disk space error on parrot for TTT site</title>
        <pubDate>Mon, 03 Mar 2014 10:51:46 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Email from Laura:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Message appearing at top of ttt website when I just took a look-
&lt;/p&gt;
&lt;pre class="wiki"&gt;Warning: session_start():
open(/home/ttt/tmp/sess_mnme76d2k5s6vopk5u1it126p5, O_RDWR) failed: No
space left on device (28) in
/home/ttt/sites/default/wp-content/plugins/tt-resource-database/participants-database.php
on line 2534
&lt;/pre&gt;&lt;p&gt;
and something in the sidebar -
&lt;/p&gt;
&lt;pre class="wiki"&gt;Warning: call_user_func_array() expects parameter 1 to be a valid
callback, array must have exactly two members in
/home/ttt/sites/default/wp-includes/plugin.php on line 199
&lt;/pre&gt;&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/696#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/709</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/709</guid>
        <title>#709: Reconomy sites appears to be sending out spam</title>
        <pubDate>Fri, 28 Mar 2014 18:48:53 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This failed email has just been returned:
&lt;/p&gt;
&lt;pre class="wiki"&gt;From: Mail Delivery System &amp;lt;Mailer-Daemon@parrot.webarch.net&amp;gt;
Date: Fri, 28 Mar 2014 18:14:32 +0000
To: recon@parrot.webarch.net
Subject: Mail delivery failed: returning message to sender
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
  fionaward@transitionnetwork.org
    SMTP error from remote mail server after end of data:
    host mx1.spamfiltering.com [72.249.150.158]: 550 An address in this message (at sleepingteensex . com) is listed on
+sbl-multi.rbl.spamrl.com. Please organise removal and retry.
------ This is a copy of the message, including all the headers. ------
Return-path: &amp;lt;recon@parrot.webarch.net&amp;gt;
Received: from recon (uid=1006)
        by parrot.webarch.net with local (Exim 4.80)
        (envelope-from &amp;lt;recon@parrot.webarch.net&amp;gt;)
        id 1WTbIM-0001Sz-6R
        for fionaward@transitionnetwork.org; Fri, 28 Mar 2014 18:14:22 +0000
To: fionaward@transitionnetwork.org
Subject: roulette89
X-PHP-Originating-Script: 1006:class-phpmailer.php
Date: Fri, 28 Mar 2014 18:14:22 +0000
From: casino10 &amp;lt;fmzsb@www.reconomy.org&amp;gt;
Message-ID: &amp;lt;28cbb75557094e41d2f5e7e070dcd660@www.reconomy.org&amp;gt;
X-Priority: 3
X-Mailer: PHPMailer 5.2.4 (http://code.google.com/a/apache-extras.org/p/phpmailer/)
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8
From: casino10 &amp;lt;fmzsb@www.reconomy.org&amp;gt;
Subject: roulette89
Message Body:
интернет казино игровые автоматы рулетка зарубежный &amp;lt;a href= http://pobedim11.sleepingteensex.com/item280.html &amp;gt;можно ли играть в
+игровые автоматы в интернете на деньги&amp;lt;/a&amp;gt; игровые автоматы через интернет 3g еще &amp;lt;a href= http://pobedim11.sleepingteensex.com &amp;gt;Новый
+Игровой Автомат&amp;lt;/a&amp;gt; казино интернет казань.
--
This mail is sent via contact form on REconomy http://www.reconomyproject.org
&lt;/pre&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/709#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/710</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/710</guid>
        <title>#710: Incorrect email address for Sam on Transition Culture</title>
        <pubDate>Tue, 01 Apr 2014 12:01:47 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
I'm seeing quite a few emails like this:
&lt;/p&gt;
&lt;pre class="wiki"&gt;From: Mail Delivery System &amp;lt;Mailer-Daemon@parrot.webarch.net&amp;gt;
Date: Tue, 01 Apr 2014 08:04:28 +0100
To: tc@parrot.webarch.net
Subject: Mail delivery failed: returning message to sender
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:
  samrossiter@transitionentwork.org
    Unrouteable address
------ This is a copy of the message, including all the headers. ------
Return-path: &amp;lt;tc@parrot.webarch.net&amp;gt;
Received: from tc (uid=1011)
        by parrot.webarch.net with local (Exim 4.80)
        (envelope-from &amp;lt;tc@parrot.webarch.net&amp;gt;)
        id 1WUskG-0005Rv-Sa
        for samrossiter@transitionentwork.org; Tue, 01 Apr 2014 08:04:28 +0100
To: samrossiter@transitionentwork.org
Subject: [Wordfence Alert] Problems found on Transition Culture
X-PHP-Originating-Script: 1011:class-phpmailer.php
Date: Tue, 1 Apr 2014 07:04:28 +0000
From: WordPress &amp;lt;wordpress@transitionculture.org&amp;gt;
Message-ID: &amp;lt;11e64e1b3cdb24f69d0069ecdc224524@transitionculture.org&amp;gt;
X-Priority: 3
X-Mailer: PHPMailer 5.2.4 (http://code.google.com/a/apache-extras.org/p/phpmailer/)
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8
Wordfence found the following new issues on "Transition Culture".
NOTE: Upgrading to the paid version of Wordfence gives you two factor authentication (sign-in via cellphone)
and country blocking which are both effective methods to block attacks.
You can also schedule when your scans occur with Wordfence Premium.
Click here to sign-up for the Premium version of Wordfence now.
https://www.wordfence.com/wordfence-signup/
Alert generated at Tuesday 1st of April 2014 at 08:04:28 AM
Critical Problems:
* The Plugin "Spam Destroyer" needs an upgrade.
&lt;/pre&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/710#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/713</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/713</guid>
        <title>#713: Ticket clearing</title>
        <pubDate>Wed, 02 Apr 2014 09:30:31 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
There are 33 &lt;a class="ext-link" href="https://trac.transitionnetwork.org/trac/query?status=accepted&amp;amp;status=assigned&amp;amp;status=new&amp;amp;status=reopened&amp;amp;order=priority&amp;amp;col=id&amp;amp;col=summary&amp;amp;col=status&amp;amp;col=type&amp;amp;col=priority&amp;amp;col=milestone&amp;amp;col=component&amp;amp;report=18&amp;amp;type=maintenance"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Open Maintenance Tickets&lt;/a&gt; this ticket is to record the time taken to close as many of them as possible.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/713#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/744</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/744</guid>
        <title>#744: Add CSS Injector module to the D6 mix</title>
        <pubDate>Thu, 19 Jun 2014 10:50:03 GMT</pubDate>
        
        <dc:creator>annesley</dc:creator>

        <description>&lt;p&gt;
CSS Injector module allows admin dynamic adding of CSS in to a live production server without code updates. this is to respond quickly to client needs whilst implementing the requests in the correct place in the themes on the next promotion from dev.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/744#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/762</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/762</guid>
        <title>#762: cannot log in to Puffin</title>
        <pubDate>Sat, 19 Jul 2014 08:46:53 GMT</pubDate>
        
        <dc:creator>annesley</dc:creator>

        <description>&lt;p&gt;
hi, i think i've locked myself out of puffin again.
i successfully logged in and navigated to ~ and /.
but it wouldn't let me access /data/disk/tn/static/transition-network-d6-s012
it asked for more authentication and then stopped responding.
&lt;/p&gt;
&lt;p&gt;
thanks, a
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/762#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/776</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/776</guid>
        <title>#776: Piwik 2.0.5</title>
        <pubDate>Sat, 16 Aug 2014 07:55:49 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
New version of Piwik, not a security update so no urgent need to upgrade unless there is some new required feature:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="http://piwik.org/changelog/piwik-2-5-0/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://piwik.org/changelog/piwik-2-5-0/&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/776#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/781</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/781</guid>
        <title>#781: MediaWiki Security and Maintenance Releases: 1.22.10 and 1.23.3</title>
        <pubDate>Thu, 28 Aug 2014 06:42:16 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Announcement email:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://lists.wikimedia.org/pipermail/mediawiki-announce/2014-August/000159.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://lists.wikimedia.org/pipermail/mediawiki-announce/2014-August/000159.html&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Bugfixes only, not a security update so no urgent update required.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/781#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/786</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/786</guid>
        <title>#786: GitHub Transition: Annesley needs permission to create repositories</title>
        <pubDate>Mon, 15 Sep 2014 07:17:03 GMT</pubDate>
        
        <dc:creator>annesley</dc:creator>

        <description>&lt;p&gt;
is Paul the owner of Transition &lt;a class="missing wiki"&gt;GitHub?&lt;/a&gt;?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/786#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/810</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/810</guid>
        <title>#810: Piwik 2.9.1</title>
        <pubDate>Thu, 20 Nov 2014 14:58:20 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
From the &lt;a class="ext-link" href="http://piwik.org/changelog/piwik-2-9-1/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;changelog&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Piwik 2.9.1 is a new minor release of Piwik. In this release we have fixed a few minor issues reported in 2.9.0.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/810#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/813</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/813</guid>
        <title>#813: MediaWiki 1.23.7</title>
        <pubDate>Thu, 27 Nov 2014 14:38:47 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The &lt;a class="ext-link" href="https://lists.wikimedia.org/pipermail/mediawiki-announce/2014-November/000170.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;announcement email&lt;/a&gt;:
&lt;/p&gt;
&lt;p&gt;
I would like to announce the release of &lt;a class="wiki" href="http://localhost:8080/trac/wiki/MediaWiki"&gt;MediaWiki&lt;/a&gt; 1.23.7, 1.22.14 and 1.19.22. This is a regular security and maintenance release. Download links are given at the end of this email.
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;h2 id="Securityfixes"&gt;Security fixes&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;(bugs 66776, 71478) SECURITY:  User PleaseStand reported a way to inject code into API clients that used format=php to process pages that underwent flash policy mangling. This was fixed along with improving how the mangling was done for format=json, and allowing sites to disable the mangling using $wgMangleFlashPolicy.  &lt;a class="ext-link" href="https://phabricator.wikimedia.org/T68776"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://phabricator.wikimedia.org/T68776&lt;/a&gt; &lt;a class="ext-link" href="https://phabricator.wikimedia.org/T73478"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://phabricator.wikimedia.org/T73478&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;ul&gt;&lt;li&gt;(bug 70901) SECURITY: User Jackmcbarn reported that the ability to update the content model for a page could allow an unprivileged attacker to edit another user's common.js under certain circumstances. The user right "editcontentmodel" was added, and is needed to change a revision's content model.  &lt;a class="ext-link" href="https://phabricator.wikimedia.org/T72901"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://phabricator.wikimedia.org/T72901&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;ul&gt;&lt;li&gt;(bug 71111) SECURITY: User PleaseStand reported that on wikis that allow raw HTML, it is not safe to preview wikitext coming from an untrusted source such as a cross-site request. Thus add an edit token to the form, and when raw HTML is allowed, ensure the token is provided before showing the preview.  This check is not performed on wikis that both allow raw HTML and anonymous editing, since there are easier ways to exploit that scenario.  &lt;a class="ext-link" href="https://phabricator.wikimedia.org/T73111"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://phabricator.wikimedia.org/T73111&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;ul&gt;&lt;li&gt;(bug 72222) SECURITY: Do not show log action when the entry is revdeleted with DELETED_ACTION. NOTICE: this may be reverted in a future release pending a public RFC about the desired functionality. This issue was reported by user Bawolff.  &lt;a class="ext-link" href="https://phabricator.wikimedia.org/T74222"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://phabricator.wikimedia.org/T74222&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;h2 id="Bugfixes"&gt;Bugfixes&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;(bug 71621) Make allowing site-wide styles on restricted special pages a config option. &lt;a class="ext-link" href="https://phabricator.wikimedia.org/T73621"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://phabricator.wikimedia.org/T73621&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;ul&gt;&lt;li&gt;(bug 42723) Added updated version history from 1.19.2 to 1.22.13 &lt;a class="ext-link" href="https://phabricator.wikimedia.org/T44723"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://phabricator.wikimedia.org/T44723&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;ul&gt;&lt;li&gt;$wgMangleFlashPolicy was added to make &lt;a class="wiki" href="http://localhost:8080/trac/wiki/MediaWiki"&gt;MediaWiki&lt;/a&gt;'s mangling of anything that might be a flash policy directive configurable.
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Full release notes for 1.23.7:
&lt;a class="ext-link" href="https://www.mediawiki.org/wiki/Release_notes/1.23"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.mediawiki.org/wiki/Release_notes/1.23&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/813#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/823</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/823</guid>
        <title>#823: Pwiki 2014 annual report</title>
        <pubDate>Wed, 07 Jan 2015 12:19:55 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Ed would like a some PDF reports of Transition Network site usage for 2014 from Piwik.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/823#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/840</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/840</guid>
        <title>#840: Piwik 2.12.1</title>
        <pubDate>Tue, 31 Mar 2015 16:31:12 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
From the &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-2-12-1/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;changelog&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Piwik 2.12.1 is a new minor release of Piwik, a follow up to 2.12.0 major release.
&lt;/p&gt;
&lt;p&gt;
In this release we have focused on fixing a regression in the Visitor Log as well as other smaller fixes.
&lt;/p&gt;
&lt;p&gt;
11 tickets have been closed by 5 contributors!
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/840#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/850</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/850</guid>
        <title>#850: Piwik 2.13.1</title>
        <pubDate>Fri, 08 May 2015 10:25:43 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-2-13-1/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;changelog&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Piwik 2.13.1, a new minor release of Piwik, has been released!
&lt;/p&gt;
&lt;p&gt;
What’s new?
&lt;/p&gt;
&lt;p&gt;
We are releasing 2.13.1 shortly after 2.13.0 to address a few small bugs that were reported by the community. This release also includes a Tracking API performance improvements as well as other minor improvements listed below.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/850#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/866</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/866</guid>
        <title>#866: Piwik 2.14.1</title>
        <pubDate>Fri, 17 Jul 2015 08:41:34 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-2-14-1/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;changelog&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;h2 id="WhatsnewinPiwik2.14.1"&gt;What’s new in Piwik 2.14.1?&lt;/h2&gt;
&lt;p&gt;
In this release we have focused on fixing a few regressions reported in the last major release Piwik 2.14.0, as well as 27 other small improvements. As always we – the Piwik team – are very interested to hear your feedback!
&lt;/p&gt;
&lt;p&gt;
27 tickets have been closed by 6 contributors.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/866#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/869</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/869</guid>
        <title>#869: Piwik 2.14.3</title>
        <pubDate>Mon, 24 Aug 2015 12:00:58 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The &lt;a class="ext-link" href="https://piwik.org/changelog/piwik-2-14-3/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Piwik Changelog 2.14.3&lt;/a&gt; contains:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Piwik 2.14.3 is a new minor release of Piwik.
&lt;/p&gt;
&lt;p&gt;
What’s new?
&lt;/p&gt;
&lt;p&gt;
This release addresses a regression introduced in 2.14.2 that prevents users from installing Piwik in some cases.
&lt;/p&gt;
&lt;p&gt;
11 tickets have been closed by 5 contributors!
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/869#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/207</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/207</guid>
        <title>#207: Logwatch Issues</title>
        <pubDate>Fri, 17 Dec 2010 14:19:50 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This is a ticket to track items that show up in the logwatch emails to root and often just take a few mins of reading time and response.
&lt;/p&gt;
&lt;p&gt;
Any issues that look like they might take longer than a few mins should have their own tickets opened.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/207#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/208</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/208</guid>
        <title>#208: Dblog Issues</title>
        <pubDate>Fri, 17 Dec 2010 14:53:29 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;blockquote&gt;
&lt;p&gt;
"The dblog module monitors your website, capturing system events in a log to be reviewed by an authorized individual at a later time. The dblog log is simply a list of recorded events containing usage data, performance data, errors, warnings and operational information. It is vital to check the dblog report on a regular basis as it is often the only way to tell what is going on."
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/reports/dblog"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/reports/dblog&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
This is a ticket to be used to flag up issues that are not going to take up enough time that they justify their own ticket -- if an issue is raised in a comment on this ticket that does look like it's going to take some significant time then best start a new ticket for it.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/208#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/218</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/218</guid>
        <title>#218: Debian upgrades and updates</title>
        <pubDate>Thu, 06 Jan 2011 13:34:16 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This is a ticket to track debian upgrades to the &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;wiki:PuffinServer&lt;/a&gt;, &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PenguinServer"&gt;wiki:PenguinServer&lt;/a&gt; and &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;wiki:ParrotServer&lt;/a&gt; the time they take.
&lt;/p&gt;
&lt;p&gt;
See:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="http://lists.debian.org/debian-security-announce/recent"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Recent Debian security announcements&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="http://lists.askmonty.org/pipermail/announce/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;MariaDB Announce List archives&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
These updates are generally done using the &lt;a class="wiki" href="http://localhost:8080/trac/wiki/AptitudeUpdateScript"&gt;wiki:AptitudeUpdateScript&lt;/a&gt; and this records all the changes in the &lt;tt&gt;/root/Changelog&lt;/tt&gt; and then the contents of the Changelog are pasted into the ticket to document the upgrade.
&lt;/p&gt;
&lt;p&gt;
This ticket was was originally used for the &lt;del&gt;&lt;a class="wiki" href="http://localhost:8080/trac/wiki/DevelopmentServer"&gt;wiki:DevelopmentServer&lt;/a&gt;&lt;/del&gt; and the &lt;del&gt;&lt;a class="wiki" href="http://localhost:8080/trac/wiki/NewLiveServer"&gt;wiki:NewLiveServer&lt;/a&gt;&lt;/del&gt;.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/218#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/371</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/371</guid>
        <title>#371: Piwik Hosting</title>
        <pubDate>Mon, 05 Dec 2011 21:34:51 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Another option to consider for Piwik would be be to use a instance on another server, and there happens to be one here that could be used:
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://stats.webarch.net/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://stats.webarch.net/&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Could this be considered?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/371#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/382</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/382</guid>
        <title>#382: Measurement and tracking requirements for TN and PSE</title>
        <pubDate>Tue, 13 Dec 2011 04:57:12 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
to list the measurement and tracking requirements for TN and PSE so that we can assess piwik vs google and decide which way to go.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/382#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/470</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/470</guid>
        <title>#470: Penguin install and configuration</title>
        <pubDate>Sat, 15 Dec 2012 16:05:16 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
penguin.webarch.net is a new 2GB RAM virtual server which will replace &lt;a class="wiki" href="http://localhost:8080/trac/wiki/NewLiveServer"&gt;NewLiveServer&lt;/a&gt; and &lt;a class="wiki" href="http://localhost:8080/trac/wiki/DevelopmentServer"&gt;DevelopmentServer&lt;/a&gt; for running all non-Drupal sites and is due to go live in early 2013. Drupal sites from the old servers will be migrated to &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;PuffinServer&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
This ticket has been created for tracking time and tasks done during the install.
&lt;/p&gt;
&lt;p&gt;
See &lt;a class="ext-link" href="https://tech.transitionnetwork.org/trac/wiki/PenguinServer"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://tech.transitionnetwork.org/trac/wiki/PenguinServer&lt;/a&gt; and also the corresponding &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;PuffinServer&lt;/a&gt;.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/470#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/483</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/483</guid>
        <title>#483: Nginx 502 Bad Gateway Errors with BOA</title>
        <pubDate>Mon, 28 Jan 2013 11:23:45 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The Barracuda Octopus Aegir server on puffin.webarch.net is getting generating a lot of Nginx 502 Bad Gateway errors, see &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/466#comment:31" title="task: Puffin install and configuration (closed: fixed)"&gt;ticket:466#comment:31&lt;/a&gt; and &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/466#comment:38" title="task: Puffin install and configuration (closed: fixed)"&gt;ticket:466#comment:38&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
The Nginx logs contain 58 502 errors:
&lt;/p&gt;
&lt;pre class="wiki"&gt;cd /var/log/nginx
grep " 502 " * | wc -l
58
&lt;/pre&gt;&lt;p&gt;
I expect the cause of these is Nginx asking PHP-FPM for a page and not getting one, an answer might be to either speed up PHP-FPM response time or adjust the Nginx settings so that it waits longs for a response from PHP-FPM.
&lt;/p&gt;
&lt;p&gt;
There are several threads about this on &lt;a class="ext-link" href="http://groups.drupal.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://groups.drupal.org/&lt;/a&gt; but none of them have any useful suggestions (eg &lt;a class="ext-link" href="http://groups.drupal.org/node/87759"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;1&lt;/a&gt; &lt;a class="ext-link" href="http://groups.drupal.org/node/165334"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;2&lt;/a&gt; &lt;a class="ext-link" href="http://groups.drupal.org/node/198428"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;3&lt;/a&gt; &lt;a class="ext-link" href="http://groups.drupal.org/node/271588"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;4&lt;/a&gt;).
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/483#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/494</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/494</guid>
        <title>#494: Email account for TRAC</title>
        <pubDate>Thu, 21 Feb 2013 10:16:37 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Set up: 'trac@…'
Password: going to Chris separately
Secure SSL/TLS Settings
Username: trac@…
Password: Use the email account’s password.
Incoming Server: mail.xssl.net
IMAP: Port 993
POP3: Port 995
Outgoing Server: mail.xssl.net
SMTP: Port 465
Authentication is required for IMAP, POP3, and SMTP.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/494#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/495</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/495</guid>
        <title>#495: Replace Google Analytics with Piwki</title>
        <pubDate>Thu, 21 Feb 2013 10:20:25 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Unless we see any issue, turn GA off on 01/03/13.
Use Piwik instead.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/495#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/502</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/502</guid>
        <title>#502: patterns sub-domain for transitionresearchnetwork.org, was: Setting up specific pointer for URL</title>
        <pubDate>Wed, 27 Feb 2013 07:10:03 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;pre class="wiki"&gt;Can we set this URL:
www.transitionresearchnetwork.org/research-guidelines
to point to this location:
https://cldstr.com/docs/configure-dns
While this URL:
www.transitionresearchnetwork.org/
Still points to the current location.
~~~~
Ed Mitchell: Transition Network Web manager
web: http://transitionnetwork.org
project blog: http://transitionnetwork.org/blogs/ed-mitchell
mobile: +44 (0)7807 141 828
office hours: Mon, Tues, Wed, Thurs
company no. 6135675  charity no. 1128675
Subscribe to Transition news: http://tinyurl.com/transitionregister
~~~~
&lt;/pre&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/502#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/528</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/528</guid>
        <title>#528: patterns.transitionresearchnetwork.org DNS update</title>
        <pubDate>Tue, 26 Mar 2013 09:58:13 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Request from Ethan:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
We've moved the site back to the production server.  Would you be willing to set the CNAME for patterns.transitionresearchnetwork.org to patterns.transitionresearchnetwork.org.230.cldstr.com?
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
See also previous tickets &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/482" title="defect: transitionresearchnetwork.org domain name (closed: fixed)"&gt;ticket:482&lt;/a&gt; and &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/502" title="enhancement: patterns sub-domain for transitionresearchnetwork.org, was: Setting up ... (closed: fixed)"&gt;ticket:502&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/528#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/529</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/529</guid>
        <title>#529: New Barracuda BOA-2.0.7 Edition available</title>
        <pubDate>Fri, 05 Apr 2013 08:57:09 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;blockquote class="citation"&gt;
&lt;blockquote&gt;
&lt;p&gt;
There is new BOA-2.0.7 Edition of Barracuda and Octopus available.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;
Please review the changelog and upgrade as soon as possible
to receive all security updates and new features.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;
Changelog: &lt;a class="ext-link" href="http://bit.ly/newboa"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://bit.ly/newboa&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/529#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/530</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/530</guid>
        <title>#530: New Barracuda BOA-2.0.8 Edition available</title>
        <pubDate>Mon, 08 Apr 2013 07:44:51 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
If I had known this was about to come out I would have waited before doing the BOA-2.0.7 upgrade last night on &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/529" title="maintenance: New Barracuda BOA-2.0.7 Edition available (closed: fixed)"&gt;ticket:529&lt;/a&gt;
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
There is new BOA-2.0.8 Edition of Barracuda and Octopus available.
&lt;/p&gt;
&lt;p&gt;
Please review the changelog and upgrade as soon as possible to receive all security updates and new features.
&lt;/p&gt;
&lt;p&gt;
Changelog: &lt;a class="ext-link" href="http://bit.ly/newboa"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://bit.ly/newboa&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
Is mostly to fix a problem for people using Percona, &lt;a class="ext-link" href="https://drupal.org/node/1962690"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://drupal.org/node/1962690&lt;/a&gt; and as we are using MariaDB this isn't an issue for us.
&lt;/p&gt;
&lt;p&gt;
Other updates in this version:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;ul&gt;&lt;li&gt;Allow to use [a-z0-9] subdomains and not only [www] for IDN domain names.
&lt;/li&gt;&lt;li&gt;Change the interval between platforms builds from 5 to 3 seconds.
&lt;/li&gt;&lt;li&gt;Forced 1s Speed Booster TTL for vhosts behind local proxy is deprecated.
&lt;/li&gt;&lt;li&gt;Move old firewall logs to backups to avoid crazy load after upgrade.
&lt;/li&gt;&lt;li&gt;Nginx: Better exceptions handling in the Abuse Guard for js/shs modules.
&lt;/li&gt;&lt;li&gt;PHP: CLI is at 5.3 since BOA-2.0.4, so symlink old 5.2 binary path to 5.3
&lt;/li&gt;&lt;li&gt;Update _LENNY_TO_SQUEEZE major upgrade procedure.
&lt;/li&gt;&lt;li&gt;Update contrib with login_security-7.x-1.2
&lt;/li&gt;&lt;li&gt;Use static downloads for all distros in stable edition.
&lt;/li&gt;&lt;/ul&gt;&lt;/blockquote&gt;
&lt;p&gt;
I'll do this update tonight unless there are any objections, hopefully it should be quite quick.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/530#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/536</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/536</guid>
        <title>#536: Upgrade Mediawiki to 1.19.6</title>
        <pubDate>Mon, 29 Apr 2013 20:35:32 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
A new version of Mediawiki is due out tomorrow:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
This is a notice that on Tuesday, April 30th between 20:00-21:00 UTC
(1-2pm PDT) Wikimedia Foundation will release security updates for
current and supported branches of the &lt;a class="wiki" href="http://localhost:8080/trac/wiki/MediaWiki"&gt;MediaWiki&lt;/a&gt; software. Downloads
and patches will be available at that time, with the git repositories
updated later that afternoon.
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="http://lists.wikimedia.org/pipermail/mediawiki-announce/2013-April/000128.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://lists.wikimedia.org/pipermail/mediawiki-announce/2013-April/000128.html&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
The upgrade should simply be a matter of following the steps taken last time, see &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/532#comment:2" title="maintenance: Upgrade to Mediawiki 1.19.5 (closed: fixed)"&gt;ticket:532#comment:2&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/536#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/539</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/539</guid>
        <title>#539: REconomy site migration and updates</title>
        <pubDate>Wed, 01 May 2013 10:01:00 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This ticket is to keep track of the tasks undertaken and the time spent on the migration of the &lt;a class="ext-link" href="http://www.reconomy.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.reconomy.org/&lt;/a&gt; site to &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;wiki:ParrotServer&lt;/a&gt;.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/539#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/544</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/544</guid>
        <title>#544: CSF / LDF false positive blocks on Puffin</title>
        <pubDate>Sat, 04 May 2013 11:02:53 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Ticket to keep track of CSF /LDF issues on Puffin, see &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer#CSFLDF"&gt;wiki:PuffinServer#CSFLDF&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/544#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/550</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/550</guid>
        <title>#550: Transition Town Totnes migration</title>
        <pubDate>Sun, 19 May 2013 14:59:44 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
It has been agreed to migrate Transition Town Totnes, &lt;a class="ext-link" href="http://transitiontowntotnes.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://transitiontowntotnes.org/&lt;/a&gt; to &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;wiki:ParrotServer&lt;/a&gt; and this ticket has been created to record this process and the time spent on it and the documentation of the migration.
&lt;/p&gt;
&lt;p&gt;
There is also an issue regarding what, if anything, to do with the old Drupal site at &lt;a class="ext-link" href="http://archive.transitiontowntotnes.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://archive.transitiontowntotnes.org/&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/550#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/551</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/551</guid>
        <title>#551: Mediawiki 1.19.7 upgrade</title>
        <pubDate>Tue, 21 May 2013 08:25:51 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
From &lt;a class="ext-link" href="http://lists.wikimedia.org/pipermail/mediawiki-announce/2013-May/000130.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;MediaWiki-announce&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
This is a notice that on Tuesday, May 21st between 20:00-21:00 UTC
(1-2pm PDT) Wikimedia Foundation will release security updates for
current and supported branches of the MediaWiki software. Downloads
and patches will be available at that time, with the git repositories
updated later that afternoon. Although &lt;strong&gt;MediaWiki does not have the&lt;/strong&gt;
&lt;strong&gt;vulnerable feature enabled by default&lt;/strong&gt;, most wiki using common advanced
features will want to patch for this issue.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/551#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/552</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/552</guid>
        <title>#552: Puffin Downtime 23rd May 2013</title>
        <pubDate>Thu, 23 May 2013 20:54:15 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
There was a massive load spike on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;wiki:PuffinServer&lt;/a&gt; this afternoon, the load average peaked at over 60 and at exactly the same time there was also one on the virtual server serving &lt;a class="ext-link" href="http://webarch.net/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://webarch.net/&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
Pingdom reported:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;www.transitionnetwork.org down since 23/05/2013  12:11:57
&lt;/li&gt;&lt;li&gt;www.transitionnetwork.org is UP again at 23/05/2013  12:19:57, after 8m of downtime
&lt;/li&gt;&lt;li&gt;www.transitionnetwork.org is down since 23/05/2013  12:26:57
&lt;/li&gt;&lt;li&gt;www.transitionnetwork.org is UP again at 23/05/2013  12:58:57, after 32m of downtime
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
When I did managed to get back into the server php-fpm and nginx were not running and it took several attempt to get them to start up.
&lt;/p&gt;
&lt;p&gt;
Attached is the munin graps of the load from today, munin didn't record the start of the spike but it did start recording it as it came down.
&lt;/p&gt;
&lt;p&gt;
This ticket has been created to report the issue and also to record anything that might be found in the logs to explain what happened.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/552#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/554</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/554</guid>
        <title>#554: Site slow down and MySQL load increase</title>
        <pubDate>Tue, 28 May 2013 18:11:51 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Since the upgrade to &lt;a class="ext-link" href="http://blog.mariadb.org/mariadb-5-5-31-now-available/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;MariaDB 5.5.31&lt;/a&gt;, done on &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/218#comment:93" title="maintenance: Debian upgrades and updates (closed: fixed)"&gt;ticket:218#comment:93&lt;/a&gt; (and fixed on &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/548#comment:32" title="defect: All Admin functions broken on TN.org (closed: fixed)"&gt;ticket:548#comment:32&lt;/a&gt;) there appears to have been been a noticeable slowdown in the time for pages to be generated, measuring with &lt;a class="ext-link" href="http://tools.pingdom.com/fpt/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://tools.pingdom.com/fpt/&lt;/a&gt; the front page alone takes around 5 seconds to generate.
&lt;/p&gt;
&lt;p&gt;
There is a clear increase in the amount of MySQL/MariaDB activity measured by Munin, see the attached graphs, the upgrade was done around midday on 24th May 2013. There has also been a increase in traffic according to the firewall graphs. The memory usage of redis has also dropped right down and the database memory usage has significantly increased.
&lt;/p&gt;
&lt;p&gt;
It's not totally clear if the cause of this change in behaviour of the site is related to the MySQL/MariaDB upgrade or if there was a coincidental change in the traffic to the site at the same time. There is no noticeable change in the visitors recorded in the Piwik stats.
&lt;/p&gt;
&lt;p&gt;
According to pingdom the front page of the site is now "slower than 77% of all tested websites"  with a total load time of around 6 seconds, almost all of this is down to the wait of around 5 seconds for the index.php file. This can also be tested from parrot with Apache bench, sometimes cached pages are served up and these appear in an instance, if the front page is generated it takes around 5 seconds, see &lt;a class="wiki" href="http://localhost:8080/trac/wiki/LoadTimes#a2013-05-28"&gt;wiki:LoadTimes#a2013-05-28&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/554#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/555</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/555</guid>
        <title>#555: Load spikes causing the TN site to be stopped for 15 min at a time</title>
        <pubDate>Wed, 29 May 2013 09:53:52 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The BOA &lt;tt&gt;/var/xdrago/second.sh&lt;/tt&gt; script is run every minute via the root crontab and if it detects a certain load level it changes the nginx config to a "high load" config which results in bots being served 503 errors when they spider the site, see &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/563" title="maintenance: 503 Errors (closed: fixed)"&gt;ticket:563&lt;/a&gt;. When the load goes higher and hits another threshold the &lt;tt&gt;second.sh&lt;/tt&gt; script kills the webserver applications, nginx and php-fpm, and waits till the load has dropped before starting them up again. This was happening once or twice a day following the increase in traffic around the launch of &lt;a class="ext-link" href="https://www.transitionnetwork.org/power-just-doing-stuff"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;The Power of Just Doing Stuff&lt;/a&gt;. This has been addressed by multiplying the thresholds by 5 in &lt;tt&gt;second.sh&lt;/tt&gt;.
&lt;/p&gt;
&lt;h2 id="OriginalDescription"&gt;Original Description&lt;/h2&gt;
&lt;p&gt;
This morning at 10:19:24 I received the following alert from puffin:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Subject: lfd on puffin.webarch.net: High 5 minute load average alert - 6.59
Time:                    Wed May 29 10:17:02 2013 +0100
1 Min Load Avg:          23.39
5 Min Load Avg:          6.59
15 Min Load Avg:         2.57
Running/Total Processes: 44/326
&lt;/pre&gt;&lt;p&gt;
At 10:21:57 I got an alert regarding ssh:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Service: SSH
Host: puffin
Address: puffin.webarch.net
State: CRITICAL
Date/Time: Wed May 29 10:21:57 BST 2013
Additional Info:
CRITICAL - Socket timeout after 10 seconds
&lt;/pre&gt;&lt;p&gt;
Then at 10:26:47 ssh appeared to have recovered:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Service: SSH
Host: puffin
Address: puffin.webarch.net
State: OK
Date/Time: Wed May 29 10:26:47 BST 2013
Additional Info:
SSH OK - OpenSSH_5.5p1 Debian-6+squeeze3 (protocol 2.0)
&lt;/pre&gt;&lt;p&gt;
But then pingdom reported at 10:29:07:
&lt;/p&gt;
&lt;pre class="wiki"&gt;www.transitionnetwork.org is down since 29/05/2013  10:24:57.
&lt;/pre&gt;&lt;p&gt;
There was then a report regarding Nginx at 10:32:07:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Notification Type: PROBLEM
Service: HTTP
Host: puffin
Address: puffin.webarch.net
State: CRITICAL
Date/Time: Wed May 29 10:32:07 BST 2013
Additional Info:
Connection refused
&lt;/pre&gt;&lt;p&gt;
So at 10:33:47 I ssh'd in and found that php53-fpm and nginx were not running and it took several attempts to get them running again.
&lt;/p&gt;
&lt;p&gt;
The up email from pingdom reported:
&lt;/p&gt;
&lt;pre class="wiki"&gt;www.transitionnetwork.org is UP again at 29/05/2013  10:36:57, after 12m of downtime.
&lt;/pre&gt;&lt;p&gt;
I can't find anything in the logs to indicate what caused the load spike and php-fpm and nginx to stopp running.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/555#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/556</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/556</guid>
        <title>#556: Upgrade Piwik to version 1.12</title>
        <pubDate>Thu, 30 May 2013 21:40:48 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
A new version of Piwik came out today with some interesting looking features:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://piwik.org/blog/2013/05/piwik-1-12/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://piwik.org/blog/2013/05/piwik-1-12/&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://piwik.org/blog/2013/05/last-piwik-1-x-release-v1-12-new-features-api-improvements-screenshots/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://piwik.org/blog/2013/05/last-piwik-1-x-release-v1-12-new-features-api-improvements-screenshots/&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/556#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/560</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/560</guid>
        <title>#560: Install drupal-based project management system onto our servers</title>
        <pubDate>Tue, 11 Jun 2013 17:00:28 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Please can you install a suitable project management drupal-based tool onto the suitable server? I am thinking of Open Atrium. It's for staff and partners to use for management stuff (ie not a ticketing system or mediawiki).
&lt;/p&gt;
&lt;p&gt;
Open Atrium?
&lt;/p&gt;
&lt;p&gt;
Can you let me know how long it would take to install to a point where I can manage it and get a pilot project up and running?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/560#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/562</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/562</guid>
        <title>#562: Users being subscribed to widgets newsletter on registratoin</title>
        <pubDate>Mon, 17 Jun 2013 15:11:22 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Ed added new users to system via user--&amp;gt;add user. They are being automatically subscribed to the widget owners newsletter. Please investigate and stop this.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/562#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/563</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/563</guid>
        <title>#563: 503 Errors</title>
        <pubDate>Wed, 19 Jun 2013 10:59:54 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The BOA &lt;tt&gt;/var/xdrago/second.sh&lt;/tt&gt; script is run every minute via the root crontab and if it detects a certain load level it changes the nginx config to a "high load" config which results in bots being served 503 errors when they spider the site. When the load goes higher and hits another threshold the &lt;tt&gt;second.sh&lt;/tt&gt; script stops the site, see &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555&lt;/a&gt;.
&lt;/p&gt;
&lt;h2 id="OriginalDescription"&gt;Original Description&lt;/h2&gt;
&lt;p&gt;
The site is generating a lot of 503 errors, 83 since 6:30am today and there were around 750 yesterday.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/563#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/565</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/565</guid>
        <title>#565: Blogs breadcrumbs incorrect on listings views</title>
        <pubDate>Tue, 25 Jun 2013 13:21:56 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Blogs breadcrumbs are wrong at main all blogs view and one author's full list view:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/blog"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/blog&lt;/a&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/blogs/ed-mitchell"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/blogs/ed-mitchell&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Jim can you sort this in under 15 minutes (which is what you have left)
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/565#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/566</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/566</guid>
        <title>#566: Profile photo does not work</title>
        <pubDate>Wed, 26 Jun 2013 14:17:35 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Using this user account:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/users/patricia-benson"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/users/patricia-benson&lt;/a&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/people/patricia-benson"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/people/patricia-benson&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
I can't get the photo to sit correctly. I have already deleted her first user account as the first photo she put in was sideways - the system presented that the right size, but sideways. Then I couldn't get the system to forget the original photo so had to delete the account and start again.
Now I've tried adding  bigger, smaller pictures and they all come out far too big - the system is enlarging them up to wider than the space alloted.
&lt;/p&gt;
&lt;p&gt;
Very odd. Too tired and busy to do this now - will revisit in July after holiday.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/566#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/568</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/568</guid>
        <title>#568: TC blog: can't *not* send notifications</title>
        <pubDate>Mon, 08 Jul 2013 10:20:16 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
I can't see how to do a node edit and *not* send a notification - here seen on the Transition Culture blog:
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/node/32863/edit"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/node/32863/edit&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
please advise - there's been some kerfuffle about the TC blog move so swift resolution much appreciated
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/568#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/569</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/569</guid>
        <title>#569: 403s served to editors, admin very slow</title>
        <pubDate>Tue, 09 Jul 2013 07:52:32 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;ol&gt;&lt;li&gt;Rob is getting 403s when trying to submit his work. Report from 07:12am this morning (Tuesday)
&lt;/li&gt;&lt;/ol&gt;&lt;ol start="2"&gt;&lt;li&gt;Ed tried to add a blog post at node add:
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/node/add/blog"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/node/add/blog&lt;/a&gt;
It took nearly 15 seconds to get this published
&lt;a class="ext-link" href="https://www.transitionnetwork.org/blogs/ed-mitchell/2013-07/eds-test-blog-item-check-403"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/blogs/ed-mitchell/2013-07/eds-test-blog-item-check-403&lt;/a&gt;
&lt;/p&gt;
&lt;ol start="3"&gt;&lt;li&gt;Running admin functions takes ages.This request took well over 30 seconds:
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/content/node/overview"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/content/node/overview&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Please advise?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/569#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/571</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/571</guid>
        <title>#571: Force HTTP for anonymous, HTTPS for logged in users</title>
        <pubDate>Tue, 16 Jul 2013 11:59:54 GMT</pubDate>
        
        <dc:creator>jim</dc:creator>

        <description>&lt;p&gt;
To further reduce load and leverage the caching I've changed the Session 443 settings to force anon users to HTTP and logged in to HTTPS. The benefit of allowing a handful of users to choose is tiny compared the downsides of outages, 503s and higher load.
&lt;/p&gt;
&lt;p&gt;
The &lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/settings/session443"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;"User state" setting on the config page&lt;/a&gt; is now " Redirect authenticated users to HTTPS and redirect anonymous users to HTTP (with the exception of login/registration pages).", was "Redirect authenticated users to HTTPS and redirect anonymous users on login/registration pages to HTTPS. Anonymous users visiting other pages may use HTTP or HTTPS."
&lt;/p&gt;
&lt;p&gt;
I've also set user and site-wide contact forms, plus the mailchimp subs page force secure-only per the "Additional pages to make secure" setting.
&lt;/p&gt;
&lt;p&gt;
We can see if this makes a difference, and this ticket is to track comments and see if it results in any improvement in performance/stability.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/571#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/572</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/572</guid>
        <title>#572: Design changes for homepage and TC section</title>
        <pubDate>Wed, 17 Jul 2013 14:17:25 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Design changes for TN homepage and TC section done by Ben to be part of maintenance budget.
&lt;/p&gt;
&lt;p&gt;
list here:
&lt;a class="ext-link" href="https://docs.google.com/spreadsheet/ccc?key=0An7ZaZdq6UfJdDhxS0JxbXZLYnhLRkN4X3h5aVV3R1E#gid=0"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://docs.google.com/spreadsheet/ccc?key=0An7ZaZdq6UfJdDhxS0JxbXZLYnhLRkN4X3h5aVV3R1E#gid=0&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/572#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/573</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/573</guid>
        <title>#573: MariaDB 5.5.32 is available for Puffin</title>
        <pubDate>Thu, 18 Jul 2013 19:11:24 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
I could either update this via aptitude and it would be quick and have little down time or I could update it via BOA and it'll take 3 or 4 times as long and involved extra downtime.
&lt;/p&gt;
&lt;p&gt;
Jim -- which way would you like it done?
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
The MariaDB project is pleased to announce the immediate availability
of MariaDB 5.5.32.
&lt;/p&gt;
&lt;p&gt;
This is a bug-fix release. See the Release Notes and Changelog for
details.
&lt;/p&gt;
&lt;p&gt;
MariaDB 5.5.32 Stable (GA)
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Release Notes: &lt;a class="ext-link" href="https://kb.askmonty.org/en/mariadb-5532-release-notes"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://kb.askmonty.org/en/mariadb-5532-release-notes&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;Changelog: &lt;a class="ext-link" href="https://kb.askmonty.org/en/mariadb-5532-changelog"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://kb.askmonty.org/en/mariadb-5532-changelog&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
&lt;a class="ext-link" href="http://lists.askmonty.org/pipermail/announce/2013-July/000048.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://lists.askmonty.org/pipermail/announce/2013-July/000048.html&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/573#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/575</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/575</guid>
        <title>#575: User system is blocking *everyone* - needs fixing urgently</title>
        <pubDate>Wed, 31 Jul 2013 14:39:11 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Everyone who registers for the last two weeks is being blocked - check user list and see screengrab. Needs fixing promptly.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/575#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/579</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/579</guid>
        <title>#579: Special email alert for Rob Hopkins blog posts on TN.org</title>
        <pubDate>Mon, 12 Aug 2013 13:49:30 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;ol&gt;&lt;li&gt;Can we create a specific email alert for new blog posts from Rob Hopkins' blog (/blogs/rob-hopkins)?
&lt;/li&gt;&lt;li&gt;Can Ed do this?
&lt;/li&gt;&lt;li&gt;See below:
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
Proposed new alert:
&lt;del&gt;&lt;/del&gt;&lt;del&gt;&lt;/del&gt;&lt;del&gt;&lt;/del&gt;&lt;del&gt;~
&lt;/del&gt;&lt;/p&gt;
&lt;p&gt;
From: [Rob Hopkins at Transition Network &amp;lt;site@…&amp;gt;]
Subject: New blog post from Rob Hopkins' Transition Culture
To: [subscriber email]
Reply to: [&amp;lt;site@…&amp;gt;]
&lt;/p&gt;
&lt;p&gt;
Hello. I've written a new blog Transition Culture blog post
&lt;/p&gt;
&lt;p&gt;
You can read it and leave comments here:
[LINK]
&lt;/p&gt;
&lt;hr /&gt;
&lt;p&gt;
[BLOG POST TITLE]
[LINE BREAK - FULL CLEAR LINE]
[BLOG POST TEASER]
[LINE BREAK - FULL CLEAR LINE]
&lt;/p&gt;
&lt;hr /&gt;
&lt;p&gt;
Best regards,
Rob
&lt;/p&gt;
&lt;p&gt;
--
[TN EMAIL SUBSCRIPTION AUTO-BLURB]
This is an automatic message from Transition Network
To manage your subscriptions, browse to &lt;a class="ext-link" href="http://www.transitionnetwork.org/user/285/notifications"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.transitionnetwork.org/user/285/notifications&lt;/a&gt;
You can unsubscribe at &lt;a class="ext-link" href="http://www.transitionnetwork.org/notifications/unsubscribe/subscription/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.transitionnetwork.org/notifications/unsubscribe/subscription/&lt;/a&gt;...
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/579#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/580</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/580</guid>
        <title>#580: php5-fpm starting when puffin boots</title>
        <pubDate>Mon, 12 Aug 2013 16:03:06 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
When &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;wiki:PuffinServer&lt;/a&gt; is booted &lt;tt&gt;/etc/init.d/php5-fpm&lt;/tt&gt; is started and this causes errors with the site.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/580#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/583</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/583</guid>
        <title>#583: tmp files on parrot exceeded inode limit</title>
        <pubDate>Mon, 02 Sep 2013 12:28:46 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Users are attempting to purchase a DVD and the cart always zeros out even after attempts to update cart etc.
&lt;/p&gt;
&lt;p&gt;
Laura suggests that this may be a server issue and to start with Chris:
&lt;/p&gt;
&lt;p&gt;
The prob could v likely be on the hosting side, so be worth contacting Chris first (and mention can add to cart all okay when logged in, view cart and alter and get to billing page, so could be a session setting that's changed) -
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;Does the server have disk space left on /tmp. Session data is most likely written there. (sometimes this cart faff issue can happen because of that.)
&lt;/li&gt;&lt;/ol&gt;&lt;ol start="2"&gt;&lt;li&gt;Are the PHP Session settings correct/ have they changed recently? Chris can fix this if needing a tweakette in php.ini or other places in the underworld of those types of files.
&lt;/li&gt;&lt;/ol&gt;&lt;ol start="3"&gt;&lt;li&gt;DB could potentially need check/repair.
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
Another one is the shop element relies on cookies so if a user has set browser to not accept cookies may poss not work! (but think thats something not to think about here, as I tested as both logged in and logged out with cookies set to work on my browser, logged out got the 'cart empty' faff factor like other users will be getting.)
&lt;/p&gt;
&lt;p&gt;
If Chris can't spot the bug (does sound server side and sessions related from a quick test here, haven't looked at the server logs, but if get a mo later will see if I can), poss good to chat and I can think some more on it, but first thoughts alert me mostly to server side, sometimes a roll back to php 5.2 clicks things back into place (but shouldn't be needed).  Be good to see if there is a correlation with any server changes/tweaks happening around same timing that the cart stopped working.  Keep me in the loop if it is a server fix-y thing as always interested to hear results on bug fixing on sites.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/583#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/584</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/584</guid>
        <title>#584: News CTs and featured images: not handling as expected</title>
        <pubDate>Wed, 04 Sep 2013 08:33:12 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
The news CT has a featured image, but it doesn't seem to be handling it as expected (succesfully on the blogs). See this news item:
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/news/2013-09-03/new-economy-20-enterprises-report-released"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/news/2013-09-03/new-economy-20-enterprises-report-released&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
The featured image isn't visible anywhere - either:
&lt;/p&gt;
&lt;ol class="loweralpha"&gt;&lt;li&gt;in the news item itself
&lt;/li&gt;&lt;li&gt;in the /news view
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
Please investigate and resolve
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/584#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/585</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/585</guid>
        <title>#585: TTech Meeting 5th September 2013</title>
        <pubDate>Thu, 05 Sep 2013 07:47:16 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This ticket has been created for the TTech Skype meeting due to take place today.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/585#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/589</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/589</guid>
        <title>#589: Blocking spammers at a firewall level</title>
        <pubDate>Fri, 06 Sep 2013 09:48:59 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
At the meeting on 5th September &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/585" title="maintenance: TTech Meeting 5th September 2013 (closed: fixed)"&gt;ticket:585&lt;/a&gt; one thing we discussed was that for August 2013:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;blockquote&gt;
&lt;p&gt;
More data is transferred for /user/register than the front page, 5.1GB compared to 3.6GB.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;/blockquote&gt;
&lt;p&gt;
Most of this will be spam bots trying to register to post spam. Jim suggested that we could look at blocking some of these spam bots at a firewall level to save on resources. This ticket is to follow up on this suggestion.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/589#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/591</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/591</guid>
        <title>#591: Move MySQL temporary directory to tmpfs</title>
        <pubDate>Mon, 09 Sep 2013 12:47:41 GMT</pubDate>
        
        <dc:creator>jim</dc:creator>

        <description>&lt;p&gt;
Chris, please read: &lt;a class="ext-link" href="http://2bits.com/articles/reduce-your-servers-resource-usage-moving-mysql-temporary-directory-ram-disk.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://2bits.com/articles/reduce-your-servers-resource-usage-moving-mysql-temporary-directory-ram-disk.html&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
I think we could easily drop a little MySQL memory to give it some in-memory disk space to do the temporary table munching Drupal is causing it. I see there are already some mounted tmpfs partitions.
&lt;/p&gt;
&lt;p&gt;
Related to &lt;a class="assigned ticket" href="http://localhost:8080/trac/ticket/590" title="defect: Drupal performance improvements (assigned)"&gt;#590&lt;/a&gt; (proposal L: Review slow query log, explain queries, tweak as necessary/flag poorly behaving modules)
&lt;/p&gt;
&lt;p&gt;
What do you think? Worth doing?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/591#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/592</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/592</guid>
        <title>#592: Many panes on homepage are in italics</title>
        <pubDate>Wed, 11 Sep 2013 07:29:50 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
they shouldn't be, but they are:
ingredient of the day
latest tc post
featured training
why do transition
featured resrouce
featured project
social reporters
all automated listings at bottom
&lt;/p&gt;
&lt;p&gt;
please resolve - ben are you around to do this or is it more suitable to ask jim atm?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/592#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/593</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/593</guid>
        <title>#593: Migrating Puffin to a ZFS file server</title>
        <pubDate>Wed, 11 Sep 2013 15:52:47 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This ticket is for the migration of &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;PuffinServer&lt;/a&gt; to a ZFS file server, this will involve some downtime but should result in better IO and easier backups.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/593#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/595</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/595</guid>
        <title>#595: Upgrade Mediawiki to 1.19.8 from 1.19.7</title>
        <pubDate>Wed, 11 Sep 2013 22:18:05 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
From &lt;a class="ext-link" href="https://git.wikimedia.org/blob/mediawiki%2Fcore.git/REL1_19/RELEASE-NOTES-1.19"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://git.wikimedia.org/blob/mediawiki%2Fcore.git/REL1_19/RELEASE-NOTES-1.19&lt;/a&gt;
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;h2 id="MediaWiki1.19.8"&gt;MediaWiki 1.19.8&lt;/h2&gt;
&lt;p&gt;
This is a security and maintenance release of the MediaWiki 1.19 branch.
&lt;/p&gt;
&lt;h3 id="Changessince1.19.7"&gt;Changes since 1.19.7&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;SECURITY: Sanitize ResourceLoader exception messages
&lt;/li&gt;&lt;li&gt;SECURITY: Token-getting functions will fail when using jsonp callbacks.
&lt;/li&gt;&lt;li&gt;SECURITY: Fix extension detection with 2 .'s
&lt;/li&gt;&lt;li&gt;Allow a string other than '*' as condition for DatabaseBase::delete()
&lt;/li&gt;&lt;li&gt;Purge upstream caches when deleting file assets.
&lt;/li&gt;&lt;li&gt;jquery.tablesorter: Add missing dependency on jquery.mwExtension
&lt;/li&gt;&lt;/ul&gt;&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/595#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/600</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/600</guid>
        <title>#600: Numbers missing from Initiatives search page</title>
        <pubDate>Mon, 30 Sep 2013 11:46:20 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
When users do a search on /initiatives we are missing a number which pertains to the results of the report:
&lt;/p&gt;
&lt;p&gt;
It should say "XXX initiatives match your search criteria"
&lt;/p&gt;
&lt;p&gt;
The XXX bit is missing
&lt;/p&gt;
&lt;p&gt;
please check and resolve
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/600#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/601</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/601</guid>
        <title>#601: TTech Meeting 3rd October 2013</title>
        <pubDate>Thu, 03 Oct 2013 09:03:42 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This is a ticket for notes and times for the online meeting held on 3rd October 2013.
&lt;/p&gt;
&lt;p&gt;
The ticket for the last meeting is &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/585" title="maintenance: TTech Meeting 5th September 2013 (closed: fixed)"&gt;ticket:585&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/601#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/602</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/602</guid>
        <title>#602: RSS problems</title>
        <pubDate>Thu, 03 Oct 2013 09:14:43 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;ol&gt;&lt;li&gt;Blogs feed not working:
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/blogs/feed/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/blogs/feed/&lt;/a&gt;
&lt;/p&gt;
&lt;ol start="2"&gt;&lt;li&gt;Rob's blog not working:
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/blogs/feed/rob-hopkins"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/blogs/feed/rob-hopkins&lt;/a&gt;
&lt;/p&gt;
&lt;ol start="3"&gt;&lt;li&gt;Getting complaints from users who are getting multiple copies of each blog post. Can't check this as the feed is down, but I've got 2 or 3 complaints in my inbox.
&lt;/li&gt;&lt;/ol&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/602#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/609</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/609</guid>
        <title>#609: Videos not showing if added via video link</title>
        <pubDate>Tue, 15 Oct 2013 08:33:43 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
e.g. of project profile:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/projects/new-forest-transition-school-community-energy-saving-project"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/projects/new-forest-transition-school-community-energy-saving-project&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
none showing on video page:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/video"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/video&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/609#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/611</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/611</guid>
        <title>#611: Adding Trac Account for Alan</title>
        <pubDate>Thu, 17 Oct 2013 12:55:21 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Alan, the other sysadmin at Webarchitects is in a  better position than me to help with some of the more complex sysadmin issues so I hope it's OK that I have added an account for him here following the &lt;a class="wiki" href="http://localhost:8080/trac/wiki/TracUserAdmin"&gt;wiki:TracUserAdmin&lt;/a&gt; notes.
&lt;/p&gt;
&lt;p&gt;
He is looking at helping with these tickets:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/599" title="maintenance: Server time drift (closed: fixed)"&gt;ticket:599&lt;/a&gt; Server time drift
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555&lt;/a&gt; Load spikes causing the TN site to be stopped for 15 min at a time
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/593" title="maintenance: Migrating Puffin to a ZFS file server (closed: fixed)"&gt;ticket:593&lt;/a&gt; Migrating Puffin to a ZFS file server
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
I don't expect he will be recording much time, I hope that is OK, he already has sudo access to all the servers.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/611#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/612</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/612</guid>
        <title>#612: Upgrade to BOA-2.1.1 Stable Edition</title>
        <pubDate>Sun, 03 Nov 2013 11:11:24 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
I have been sent this email from &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;wiki:PuffinServer&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;blockquote&gt;
&lt;p&gt;
There is new BOA-2.1.0 Stable Edition available.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;
Please review the changelog and upgrade as soon as possible
to receive all security updates and new features.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;
Changelog: &lt;a class="ext-link" href="http://bit.ly/newboa"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://bit.ly/newboa&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;/blockquote&gt;
&lt;p&gt;
I could potentially do this upgrade tonight as it's a quite time for the server -- Jim, any reason not to apply this update tonight?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/612#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/614</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/614</guid>
        <title>#614: Subscription option for Social Reporters CT</title>
        <pubDate>Wed, 06 Nov 2013 16:49:49 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
We want a button on the Social Reporters section that enables users to easily subscribe to the Social Reporters' blog posts CT. Offers the option to all types of user:
&lt;/p&gt;
&lt;ol class="loweralpha"&gt;&lt;li&gt;Users may not be logged in
&lt;/li&gt;&lt;li&gt;Users may not be registered
&lt;/li&gt;&lt;/ol&gt;&lt;ol&gt;&lt;li&gt;This is a bit like the sub button on Transition Culture section
&lt;/li&gt;&lt;li&gt;I can't find it in TRAC but have this memory of enabling email-only subscriptions to not-registered-users from olden days - can you enlighten me about that? I'm not sure it's the answer - we probably want them to register so they can add comments - but this request has brought up that old function
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
..
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/614#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/615</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/615</guid>
        <title>#615: Move to GMap 6.x-2.x-dev as and get clusterer to work</title>
        <pubDate>Sun, 10 Nov 2013 18:14:51 GMT</pubDate>
        
        <dc:creator>jim</dc:creator>

        <description>&lt;p&gt;
This is largely done, but the only tasks left are:
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;Make a patch and add to our makefile so our custom markers appear ok.
&lt;/li&gt;&lt;li&gt;Get the clusterer to work per the comments &amp;amp; issues in &lt;a href="http://localhost:8080/trac/ticket/615#comment:1" title="Comment 1 for Ticket #615"&gt;comment:1&lt;/a&gt; below.
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
Per an email I got from Google:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
As you may be aware, &lt;a class="missing wiki"&gt;JavaScript?&lt;/a&gt; Maps API v2 was scheduled for shutdown on May 19, 2013. After listening to feedback from developers we decided to extend the deprecation timeline by six months, to November 19, 2013 to allow more time for migration to v3 of the API.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
On November 19, 2013 we will deploy a &lt;a class="missing wiki"&gt;JavaScript?&lt;/a&gt; wrapper that attempts to automagically turn remaining v2 maps into v3 maps. Though we expect this wrapper to work for most simple maps, we cannot guarantee that your maps will continue to function. We therefore highly recommend that you migrate to v3 before November 19. The good news is that Google Maps &lt;a class="missing wiki"&gt;JavaScript?&lt;/a&gt; API v3 is more robust and feature rich than v2, and we’ve written a guide to assist the migration.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
So this ticket is to do the update to the GMap module, testing and tweaking.
&lt;/p&gt;
&lt;p&gt;
Critical as we only have until 19 November for this...
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/615#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/617</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/617</guid>
        <title>#617: Help adding text to account creation email</title>
        <pubDate>Mon, 11 Nov 2013 17:16:37 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
I want to add a link to the email a user receives following their creation of an account.
&lt;/p&gt;
&lt;p&gt;
this one: Subject: Account details for [user] at Transition Network
&lt;/p&gt;
&lt;p&gt;
Can I do this myself? I've looked in subs, notifications, logintoboggan etc. and can't find the place
&lt;/p&gt;
&lt;p&gt;
is it do-able?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/617#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/621</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/621</guid>
        <title>#621: Check and speed up updates to homepage sections: TC and slideshow</title>
        <pubDate>Mon, 18 Nov 2013 09:22:59 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Two bits of the homepage are taking ages to update once Rob has made the changes and it's driving him spare. He's waiting up to 30 mins for them to update.
&lt;/p&gt;
&lt;p&gt;
Please speed up the times that it takes the system to update these two parts of the homepage to *instant* if possible:
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;Slideshow on homepage (AKA: &lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/build/views/edit/slideshows?destination=newhome#views-tab-panel_pane_1"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/build/views/edit/slideshows?destination=newhome#views-tab-panel_pane_1&lt;/a&gt;).
&lt;/li&gt;&lt;/ol&gt;&lt;ol start="2"&gt;&lt;li&gt;Latest Transition Culture Blog pane on Homepage (AKA &lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/build/views/edit/tc_latest_blog?destination=newhome#views-tab-block_1"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/build/views/edit/tc_latest_blog?destination=newhome#views-tab-block_1&lt;/a&gt;)
&lt;/li&gt;&lt;/ol&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/621#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/624</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/624</guid>
        <title>#624: Comment handling on pages: particularly Austerity one</title>
        <pubDate>Tue, 19 Nov 2013 11:16:02 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Rob is doing an austerity special over 8 days, with a different clip from an interview with NEF every day. I've set up a page here:
/austerity-basics
&lt;/p&gt;
&lt;p&gt;
Question:
&lt;/p&gt;
&lt;p&gt;
I know we can handle comments on pages, and I know that I don't get notifications of them. Can we arrange comment notifications for a page - asap - so that commenters get updates?
&lt;/p&gt;
&lt;p&gt;
If not, no problem. I heard about this plan *today* so am not expecting any massive tech leaps.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/624#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/628</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/628</guid>
        <title>#628: Change space notifications email from IJK.co.uk to TN.org</title>
        <pubDate>Thu, 21 Nov 2013 16:50:37 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
The space notifications are coming from "space.transitionnetwork.org" &amp;lt;jim@…&amp;gt;
&lt;/p&gt;
&lt;p&gt;
can you make them from
"space.transitionnetwork.org" and a suitable TN address?
&lt;/p&gt;
&lt;p&gt;
Do I need to set up a suitable TN address? Perhaps
&lt;/p&gt;
&lt;p&gt;
space@…?
&lt;/p&gt;
&lt;p&gt;
Or is there a standard drupal system one in place already?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/628#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/630</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/630</guid>
        <title>#630: Archiving Transition Town Totnes site</title>
        <pubDate>Mon, 25 Nov 2013 11:54:35 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Please estimate to archive TTT site as per conversation with Ed:
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;convert to html
&lt;/li&gt;&lt;li&gt;host on Penguin (incl. any likely issues for Penguin doing this)
&lt;/li&gt;&lt;li&gt;any ongoing maintenance
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
Then Ed will discuss with Frances at TTT as per agreement with Chris
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/630#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/631</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/631</guid>
        <title>#631: Move Transition Culture onto PARROT</title>
        <pubDate>Mon, 25 Nov 2013 11:57:44 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
We are about to move TC onto PARROT. List of likely actions here:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Ed speak to Simon (move the host, keep the developer if poss)
&lt;/li&gt;&lt;li&gt;Chris speak to Simon about TC issues - traffic, size etc.
&lt;/li&gt;&lt;li&gt;analyse TC traffic and DB size
&lt;/li&gt;&lt;li&gt;prepare PARROT
&lt;/li&gt;&lt;li&gt;move TC
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Chris thinks we'll need to up PARROT to
VPS2 + 2 GB RAM
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/631#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/632</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/632</guid>
        <title>#632: Add accounts for Sam</title>
        <pubDate>Mon, 25 Nov 2013 14:41:25 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Following &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/534" title="maintenance: Add accounts for Ben (closed: fixed)"&gt;ticket:534&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/632#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/633</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/633</guid>
        <title>#633: RHS blocks changes for homepage</title>
        <pubDate>Mon, 25 Nov 2013 15:27:15 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Re-arrange/add/edit the RHS blocks to appear the order below
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;Why/how etc. : NO change
&lt;/li&gt;&lt;li&gt;newsletter promo: NO change
&lt;/li&gt;&lt;li&gt;POJDS book button: much smaller - can you set book image to lhs and buy button to rhs within block? might need a special .png to have both in it
&lt;/li&gt;&lt;li&gt;Transition nearby button: NO change
&lt;/li&gt;&lt;li&gt;New iT2 film promo button: needs a graphic
&lt;/li&gt;&lt;li&gt;New TFP button: NEW: Trucie providing a graphic to fit in
&lt;/li&gt;&lt;li&gt;Training button: NEW: Ed asking for training graphic to fit in
&lt;/li&gt;&lt;li&gt;Social media promo button: NEW: needs some very modest SM logos to link to SM outposts FB and twitter
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
NB: Rob is only thinking of the homepage; Ed is not sure of the implications elsewhere on site... please advise on how/if this affects things elsewhere...
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/633#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/637</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/637</guid>
        <title>#637: What is the wordcount for the /news and /blogs/rob-hopkins teasers?</title>
        <pubDate>Thu, 28 Nov 2013 09:40:48 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
&lt;a class="ext-link" href="http://www.transitionnetwork.org/news"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.transitionnetwork.org/news&lt;/a&gt;
&lt;a class="ext-link" href="http://www.transitionnetwork.org/blogs/rob-hopkins"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.transitionnetwork.org/blogs/rob-hopkins&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
what is the teaser length - ie the first paragraph of a news or blog item that is published in the listings views?
&lt;/p&gt;
&lt;p&gt;
rob wants to know how many words he has for his introductions...
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/637#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/643</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/643</guid>
        <title>#643: Add paginator for /films view</title>
        <pubDate>Mon, 09 Dec 2013 11:40:08 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Please add pages links for this view:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/build/views/edit/Films?destination=films#views-tab-page_1"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/build/views/edit/Films?destination=films#views-tab-page_1&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
10 per page should do it
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/643#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/648</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/648</guid>
        <title>#648: Edit the contact form reply in January</title>
        <pubDate>Thu, 12 Dec 2013 10:49:39 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Ed has edited the contact form replies for webproject@… on the contact form for TN.org which will now reply to users saying this:
&lt;/p&gt;
&lt;p&gt;
"Thank you for getting in touch. Please note that the website support is part time; and between mid-December 2013 and mid-January 2014 we are handing over the website support work as Ed goes on Paternity leave and Sam comes onboard, so please be patient - your replies are likely to take more time than usual. "
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/build/contact"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/build/contact&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
SAM - when you are ready - probably mid-Jan - you will want to edit this back to something more suitable like:
&lt;/p&gt;
&lt;p&gt;
Thank you for getting in touch. Please note that the website support is part time, so while we will get back to you as soon as we can, that may be a few days
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/648#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/649</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/649</guid>
        <title>#649: Add commenting to /films/ content type in January</title>
        <pubDate>Thu, 12 Dec 2013 10:53:16 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
seen here:
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/content/node-type/films"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/content/node-type/films&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/films"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/films&lt;/a&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/films/occupy-love"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/films/occupy-love&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/649#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/650</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/650</guid>
        <title>#650: Helping TN strategy consultation with online publishing</title>
        <pubDate>Thu, 12 Dec 2013 11:00:08 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Sarah will be working on the TN strategy and this is about the content and comms tactics therein. The guiding principle is to use TN.org as the most suitable place for this material and conversations, and social media and direct mailshots for marketing and communicating it (because Sarah/TN cannot manage multiple conversations in multiple locations atm).
&lt;/p&gt;
&lt;p&gt;
This is work for Sam to do from January onwards
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;set up a landing page ".../TN-strategy-consultation" with its own RHS block with manual links to different documents and interviews
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
SAM this can be a normal page with anchor links etc.
&lt;/p&gt;
&lt;ol start="2"&gt;&lt;li&gt;Use of blogs
&lt;/li&gt;&lt;li&gt;Rob's for outreach - it's got the momentum - for updates/alerts/subscriptions
&lt;/li&gt;&lt;li&gt;Sarah's for continuity (and looking back at it) - using tag "fn-strategy-consultation"
&lt;/li&gt;&lt;/ol&gt;&lt;ol start="3"&gt;&lt;li&gt;other places for comms/engagement
&lt;/li&gt;&lt;li&gt;Forums not good; too open to trolls and spam; better in blog comments
&lt;/li&gt;&lt;li&gt;webinar? Possibly if suitable
&lt;/li&gt;&lt;li&gt;FB, twitter, other marketing channels - for marketing only
&lt;/li&gt;&lt;li&gt;online meeting with national hubs - quite possibly
&lt;/li&gt;&lt;/ol&gt;&lt;ol start="4"&gt;&lt;li&gt;Direct Mail shot to PPOCs
&lt;/li&gt;&lt;li&gt;Sarah Let Sam know if this is happening; Sam you'll need to do an export of PPOCs (&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/reports/initiatives/primary-contacts"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/reports/initiatives/primary-contacts&lt;/a&gt;), tidy and dump into mail chimp using the standard template
&lt;/li&gt;&lt;/ol&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/650#changelog</comments>
    </item>
 </channel>
</rss>