<?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=summary</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=summary</link>
    </image>
    <generator>Trac 0.12.5</generator>
    <item>
        <link>http://localhost:8080/trac/ticket/753</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/753</guid>
        <title>#753: wiki.transitionnetwork.org displaying error</title>
        <pubDate>Fri, 04 Jul 2014 08:23:52 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This is rather weird, the site was working yesterday, now at &lt;a class="ext-link" href="https://wiki.transitionnetwork.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://wiki.transitionnetwork.org/&lt;/a&gt; we have:
&lt;/p&gt;
&lt;pre class="wiki"&gt;bar(), etc etc) which throw parse errors in # PHP 4. Setup.php and ObjectCache.php have structures invalid in PHP 5.0 and # 5.1, respectively. if ( !function_exists( 'version_compare' ) || version_compare( phpversion(), '5.3.2' ) &amp;lt; 0 ) { // We need to use dirname( __FILE__ ) here cause __DIR__ is PHP5.3+ require dirname( __FILE__ ) . '/includes/PHPVersionError.php'; wfPHPVersionError( 'index.php' ); } require __DIR__ . '/includes/WebStart.php'; $mediaWiki = new MediaWiki(); $mediaWiki-&amp;gt;run();
&lt;/pre&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/753#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/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/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/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/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/780</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/780</guid>
        <title>#780: parrot</title>
        <pubDate>Wed, 27 Aug 2014 14:35:51 GMT</pubDate>
        
        <dc:creator>annesley</dc:creator>

        <description>&lt;p&gt;
can't access parrot again
also: it re-requests my password very quickly. what is the session timeout?
&lt;/p&gt;
&lt;p&gt;
also: i cannot include my files. seems that the website is located under the /home/annesley directory. is this some sort of strange setup because the PHP cannot see that area. and i cannot cd to the root through SFTP...
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/780#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/778</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/778</guid>
        <title>#778: need access to Parrot</title>
        <pubDate>Wed, 27 Aug 2014 12:16:39 GMT</pubDate>
        
        <dc:creator>annesley</dc:creator>

        <description>&lt;p&gt;
i need a publicly available &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; demo install to play with. should this be on Parrot? what (sub)domain can i use?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/778#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/698</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/698</guid>
        <title>#698: intransitionmovie.com returns 405 on submit</title>
        <pubDate>Thu, 06 Mar 2014 11:45:39 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
&lt;a class="ext-link" href="http://www.intransitionmovie.com/screenings/share-your-screening/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.intransitionmovie.com/screenings/share-your-screening/&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
vid Atcheson (david@…) sent a message using the contact form at
&lt;a class="ext-link" href="https://www.transitionnetwork.org/contact"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/contact&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
I couldn't find any contact info at &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;, but am
hoping you can help. When I visit
&lt;a class="ext-link" href="http://www.intransitionmovie.com/screenings/share-your-screening/index.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.intransitionmovie.com/screenings/share-your-screening/index.html&lt;/a&gt;
and put in my email address and hit Enter, I get:
&lt;/p&gt;
&lt;p&gt;
Hi I checked this and it returns a 405 error for me too.
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="http://www.intransitionmovie.com/screenings/share-your-screening/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.intransitionmovie.com/screenings/share-your-screening/&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
405 Not Allowed
nginx/1.4.4
&lt;/p&gt;
&lt;p&gt;
Hoping this can be fixed so we can let you know about our screening on April
8 at the Hawaii State Capitol auditorium.
&lt;/p&gt;
&lt;p&gt;
Aloha,
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;David Atcheson, Transition Oahu
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
I'll do some initial investigation
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/698#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/773</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/773</guid>
        <title>#773: download copy of current TN D6 website</title>
        <pubDate>Wed, 06 Aug 2014 09:58:14 GMT</pubDate>
        
        <dc:creator>annesley</dc:creator>

        <description>&lt;p&gt;
hi, am trying to get a copy of the current TN.org D6 database and filesystem down to my laptop to develop against. i had pulled from GIT, backed up from Backup&amp;amp;Migrate and got everything working but there are things missing.
&lt;/p&gt;
&lt;p&gt;
so i want to do a file copy. i started a tar operation but the tar size went over 1.3GB and i stopped it because it shouldn't be that big. as always BOA has restricted use of the "du" command so i can't really tell why the tar was so big. and i can't "df" to see if it's a problem
&lt;/p&gt;
&lt;p&gt;
should i let it continue? why is it so big?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/773#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/771</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/771</guid>
        <title>#771: cannot access puffin over sftp again</title>
        <pubDate>Tue, 05 Aug 2014 09:24:10 GMT</pubDate>
        
        <dc:creator>annesley</dc:creator>

        <description>&lt;p&gt;
not sure what happened this time. my connection to other servers is fine. i am using:
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="sftp://tn.ftp@puffin.transitionnetwork.org/static/transition-network-d6-32-s002-booker/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;sftp://tn.ftp@puffin.transitionnetwork.org/static/transition-network-d6-32-s002-booker/&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
the password was accepted first time and i successfully navigated to /static
&lt;/p&gt;
&lt;p&gt;
which worked until i tried to get to the transition-network-d6-32-s002-booker directory. now ssh fails also.
&lt;/p&gt;
&lt;p&gt;
when i ssh in i get plenty of warnings and potential lock outs when i try various things. like trying to access /static.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/771#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/811</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/811</guid>
        <title>#811: WordPress critical security release</title>
        <pubDate>Thu, 20 Nov 2014 20:25:07 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
From &lt;a class="ext-link" href="https://wordpress.org/news/2014/11/wordpress-4-0-1/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;the blog&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
&lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; 4.0.1 is now available. This is a critical security release for all previous versions and we strongly encourage you to update your sites immediately.
&lt;/p&gt;
&lt;p&gt;
Sites that support automatic background updates will be updated to &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; 4.0.1 within the next few hours. If you are still on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; 3.9.2, 3.8.4, or 3.7.4, you will be updated to 3.9.3, 3.8.5, or 3.7.5 to keep everything secure. (We don’t support older versions, so please update to 4.0.1 for the latest and greatest.)
&lt;/p&gt;
&lt;p&gt;
&lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; versions 3.9.2 and earlier are affected by a critical cross-site scripting vulnerability, which could enable anonymous users to compromise a site.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/811#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/594</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/594</guid>
        <title>#594: WordPress 3.6.1 Maintenance and Security Release</title>
        <pubDate>Wed, 11 Sep 2013 22:05:01 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The following is from &lt;a class="ext-link" href="http://wordpress.org/news/2013/09/wordpress-3-6-1/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://wordpress.org/news/2013/09/wordpress-3-6-1/&lt;/a&gt;
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
&lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; 3.6.1 is also a security release for all previous &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; versions and we strongly encourage you to update your sites immediately. It addresses three issues fixed by the &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; security team:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Block unsafe PHP unserialization that could occur in limited situations and setups, which can lead to remote code execution. Reported by Tom Van Goethem.
&lt;/li&gt;&lt;li&gt;Prevent a user with an Author role, using a specially crafted request, from being able to create a post “written by” another user. Reported by Anakorn Kyavatanakij.
&lt;/li&gt;&lt;li&gt;Fix insufficient input validation that could result in redirecting or leading a user to another website. Reported by Dave Cummo, a Northrup Grumman subcontractor for the U.S. Centers for Disease Control and Prevention.
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Additionally, we’ve adjusted security restrictions around file uploads to mitigate the potential for cross-site scripting.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/594#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/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/665</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/665</guid>
        <title>#665: Wagn "Problem Loading Page" error</title>
        <pubDate>Mon, 06 Jan 2014 14:02:00 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Bug report from Tom:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
I've encountered a problem when trying to set up new accounts: I get a 'Problem Loading Page' error when it tries to load &lt;a class="ext-link" href="http://localhost:3000/wagn/Invite_Success"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://localhost:3000/wagn/Invite_Success&lt;/a&gt;. This seems to be explained at &lt;a class="ext-link" href="http://wagn.org/Special_Urls_and_Ports"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://wagn.org/Special_Urls_and_Ports&lt;/a&gt; - which I am hoping falls under your area of responsibility as I'm not sure how to do it myself,! But let me know if not...
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/665#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/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/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/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/748</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/748</guid>
        <title>#748: Urgent: Fiona having problems sending email</title>
        <pubDate>Wed, 25 Jun 2014 12:42:27 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Chris, Fiona is having problems sending email. I have checked the quota in the web interface and she is not over her quota.
&lt;/p&gt;
&lt;p&gt;
She initially sent this:
&lt;/p&gt;
&lt;p&gt;
The message could not be sent because the server rejected the sender's email address. The sender's email address was 'fionaward@…'.
&lt;/p&gt;
&lt;hr /&gt;
&lt;p&gt;
Subject 'Re: filming'
Server Error: 550
Server Response: 550 Access denied - Invalid HELO name (See RFC2821 4.1.1.1)
Server: 'mail.transitionnetwork.org'
Windows Live Mail Error ID: 0x800CCC78
Protocol: SMTP
Port: 26
Secure(SSL): No
&lt;/p&gt;
&lt;hr /&gt;
&lt;p&gt;
Which looked to me like the email had been sent and rejected by the receiving server.
&lt;/p&gt;
&lt;p&gt;
So I sent this to Fiona:
&lt;/p&gt;
&lt;p&gt;
On 24 June 2014 16:11, Sam Rossiter &amp;lt;samintransition@…&amp;gt; wrote:
Hi Fiona I'll take a look now. It could have been rejected for a number of reasons. There's no keywords in the email that might trigger a spam rejection? Or have you Cc'd a large number of people?
&lt;/p&gt;
&lt;p&gt;
As a workaround until we get to the bottom of it is it something a collegue could forward? Or does it have to come from you?
&lt;/p&gt;
&lt;p&gt;
Thanks
&lt;/p&gt;
&lt;p&gt;
Sam
&lt;/p&gt;
&lt;hr /&gt;
&lt;p&gt;
Fiona replied:
&lt;/p&gt;
&lt;p&gt;
Hi Sam
I don;t think it's that email, as there are 13 that won't send frm my outbox even if I remove this email - same problem with the next one!
Thanks Fiona
&lt;/p&gt;
&lt;p&gt;
---
&lt;/p&gt;
&lt;p&gt;
Chris I'm not working until next Tuesday, so I was wondering if you could pick this up and liase with Fiona? fionawardttt [AT] googlemail.com
&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/748#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/729</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/729</guid>
        <title>#729: Upgrade to Piwik 2.2.2</title>
        <pubDate>Fri, 23 May 2014 08:21:12 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
2.2.2 came out on 8th May, not sure why I missed this at the time, the change log is here: &lt;a class="ext-link" href="http://piwik.org/changelog/piwik-2-2-2/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://piwik.org/changelog/piwik-2-2-2/&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
The last upgrade was 2.2.1 &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/726" title="maintenance: Upgrade to Piwik 2.2.1 (closed: fixed)"&gt;ticket:726&lt;/a&gt; and the upgrade notes are at &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PiwikServer#Updates"&gt;wiki:PiwikServer#Updates&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/729#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/726</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/726</guid>
        <title>#726: Upgrade to Piwik 2.2.1</title>
        <pubDate>Tue, 06 May 2014 11:14:05 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;blockquote class="citation"&gt;
&lt;p&gt;
Piwik 2.2.1 is a new minor release which brings more stability to the platform.
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="http://piwik.org/changelog/piwik-2-2-1/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://piwik.org/changelog/piwik-2-2-1/&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/726#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/720</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/720</guid>
        <title>#720: Upgrade to Piwik 2.2.0</title>
        <pubDate>Thu, 17 Apr 2014 07:51:50 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
From the Changelog, &lt;a class="ext-link" href="http://piwik.org/changelog/piwik-2-2-0/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://piwik.org/changelog/piwik-2-2-0/&lt;/a&gt;
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Piwik 2.2.0 is a major new release. This release is rated critical. Please update now.
&lt;/p&gt;
&lt;p&gt;
We highly recommend that you upgrade your server to Piwik 2.2.0 today to benefit from design, performance and security improvements in this release.
&lt;/p&gt;
&lt;h2 id="Piwik2.2helpsyoufocusonyourdata"&gt;Piwik 2.2 helps you focus on your data&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;All reports: display as much text as possible before the label becomes truncated (useful when you want to see more data at a glance without having to hover to view the full label)
&lt;/li&gt;&lt;li&gt;Make Datatables more readable and flatter – we have removed some borders.
&lt;/li&gt;&lt;li&gt;On the dashboard, the Data Tables and graph icons are now hidden by default and are now available by clicking on the widget footer.
&lt;/li&gt;&lt;/ul&gt;&lt;h2 id="Newfeatures"&gt;New features&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;Event Tracking: track your custom events with Piwik. An event is defined by a Category, an Action, an optional Name and an optional Value. Event Tracking is a powerful feature which can be used for many purposes! &lt;a class="ext-link" href="http://piwik.org/docs/event-tracking/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://piwik.org/docs/event-tracking/&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;Site Search reports are now available in Scheduled email reports and on Piwik Mobile
&lt;/li&gt;&lt;li&gt;New Websites Groups (available on request) functionality now allows you to group a cluster of websites in the All Websites Dashboard.
&lt;/li&gt;&lt;li&gt;Security fixes: we would like to warmly thank Security researchers Mateusz Goik and Vivek S. Jadhav for responsibly reporting two XSS security issues in Piwik which are now fixed in 2.2.0.
&lt;/li&gt;&lt;li&gt;API breaking change for Plugins developers
&lt;/li&gt;&lt;li&gt;Deprecated the function Schema::dropTables() and DbHelper::dropTables, for the new Db::dropTables()
&lt;/li&gt;&lt;li&gt;Removed the code that was deprecated in 2.1.0. Learn more &lt;a class="ext-link" href="http://piwik.org/blog/2014/02/piwik-2-1-changes-plugin-developers/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://piwik.org/blog/2014/02/piwik-2-1-changes-plugin-developers/&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/720#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/672</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/672</guid>
        <title>#672: Upgrade to Piwik 2.0.3</title>
        <pubDate>Mon, 13 Jan 2014 10:13:00 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-0-3/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Piwik changelog&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Piwik 2.0.3 is a bug-fix release. To ensure the highest quality and reliability for your Piwik 2.0 setup, we have fixed all known major bugs, as well as made some small improvements.
&lt;/p&gt;
&lt;p&gt;
...
&lt;/p&gt;
&lt;p&gt;
We highly recommend that you upgrade your server to Piwik 2.0.3 today to benefit from the latest improvements.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/672#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/532</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/532</guid>
        <title>#532: Upgrade to Mediawiki 1.19.5</title>
        <pubDate>Mon, 15 Apr 2013 13:40:34 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
New version out tonight:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
This is a notice that on Monday, April 15th 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. CVSS scores are between 4.3 and 7.1,
most users will want to update.
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="http://lists.wikimedia.org/pipermail/mediawiki-announce/2013-April/000126.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://lists.wikimedia.org/pipermail/mediawiki-announce/2013-April/000126.html&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/532#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/736</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/736</guid>
        <title>#736: Upgrade to MediaWiki 1.23.0</title>
        <pubDate>Thu, 05 Jun 2014 09:43:50 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/2014-June/000152.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;the announcements list&lt;/a&gt;:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
I am happy to announce the availability of the first stable release of the new &lt;a class="wiki" href="http://localhost:8080/trac/wiki/MediaWiki"&gt;MediaWiki&lt;/a&gt; 1.23 release series.
&lt;/p&gt;
&lt;p&gt;
&lt;a class="wiki" href="http://localhost:8080/trac/wiki/MediaWiki"&gt;MediaWiki&lt;/a&gt; 1.23 is a large release that contains many new features and bug fixes. This is a summary of the major changes of interest to users. You can consult the RELEASE-NOTES-1.23 file for the full list of changes in this version.
&lt;/p&gt;
&lt;p&gt;
This is a Long Term Support release (LTS) and will be supported until May 2017.
&lt;/p&gt;
&lt;p&gt;
Our thanks to everyone who helped to improve &lt;a class="wiki" href="http://localhost:8080/trac/wiki/MediaWiki"&gt;MediaWiki&lt;/a&gt; by testing the release candidates and submitting bug reports.
&lt;/p&gt;
&lt;h2 id="Whatsnew"&gt;What's new?&lt;/h2&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="wiki" href="http://localhost:8080/trac/wiki/MediaWiki"&gt;MediaWiki&lt;/a&gt; 1.23 includes all changes released in the smaller 1.23wmfX software deployments to Wikimedia sites.
&lt;/li&gt;&lt;/ul&gt;&lt;h3 id="Skinautodiscoverydeprecated"&gt;Skin autodiscovery deprecated&lt;/h3&gt;
&lt;p&gt;
Skin autodiscovery, the legacy skin installation mechanism used by &lt;a class="wiki" href="http://localhost:8080/trac/wiki/MediaWiki"&gt;MediaWiki&lt;/a&gt; since very early versions (around 2004), has been officially deprecated and will be removed in &lt;a class="wiki" href="http://localhost:8080/trac/wiki/MediaWiki"&gt;MediaWiki&lt;/a&gt; 1.25.
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="wiki" href="http://localhost:8080/trac/wiki/MediaWiki"&gt;MediaWiki&lt;/a&gt; 1.23 will emit warnings in production if a skin using the deprecated mechanism is found.
&lt;/li&gt;&lt;li&gt;See Manual:Skin autodiscovery for more information and a migration guide for site admins and skin developers.
&lt;/li&gt;&lt;/ul&gt;&lt;h3 id="Notifications"&gt;Notifications&lt;/h3&gt;
&lt;p&gt;
With 1.23, &lt;a class="wiki" href="http://localhost:8080/trac/wiki/MediaWiki"&gt;MediaWiki&lt;/a&gt; starts to behave more like a modern website as regards notifications, to keep the editors of your wiki engaged and always up to date about what interests them. This used to require several custom settings.
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;(bug 45020) Make preferences "Add pages I create and files I upload to my watchlist" and "pages and files I edit" true by default.
&lt;/li&gt;&lt;li&gt;(bug 45022) Make preference "Email me when a page or file on my watchlist is changed" true by default.
&lt;/li&gt;&lt;li&gt;(bug 49719) Watch user page and user talk page by default.
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
This will allow your new users to immediately start benefiting from the watchlist and email notification features, without needing to first read all the docs to find out that they're as useful as they are.
&lt;/p&gt;
&lt;h3 id="Mergedextensions"&gt;Merged extensions&lt;/h3&gt;
&lt;p&gt;
Merged into 1.23:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;ExpandTemplates (bug 28264).
&lt;/li&gt;&lt;li&gt;AssertEdit (bug 27841) - documented at API:Assert.
&lt;/li&gt;&lt;/ul&gt;&lt;h3 id="Interface"&gt;Interface&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;(bug 42026) Add option to only show page creations in Special:Contributions (and API).
&lt;/li&gt;&lt;li&gt;Add new special page to list duplicate files, Special:ListDuplicatedFiles.
&lt;/li&gt;&lt;li&gt;(bug 60333) Add new special page listing tracking categories (Special:TrackingCategories).
&lt;/li&gt;&lt;/ul&gt;&lt;h3 id="Editing"&gt;Editing&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;A new special page Special:Diff was added, allowing users to create internal links to revision comparison pages using syntax such as Special:Diff/12345, Special:Diff/12345/prev or Special:Diff/12345/98765.
&lt;/li&gt;&lt;/ul&gt;&lt;h3 id="Helppages"&gt;Help pages&lt;/h3&gt;
&lt;p&gt;
With 1.23, &lt;a class="wiki" href="http://localhost:8080/trac/wiki/MediaWiki"&gt;MediaWiki&lt;/a&gt; begins a process of consolidation of its help pages. Now, most are using the Translate extension and can be easily translated and updated in hundreds languages.
&lt;/p&gt;
&lt;p&gt;
In the coming months, we'll focus on making more of the central help pages translatable and on linking them from the relevant &lt;a class="wiki" href="http://localhost:8080/trac/wiki/MediaWiki"&gt;MediaWiki&lt;/a&gt; interfaces for better discoverability. Please help: add your own translations; update existing pages and cover missing &lt;a class="wiki" href="http://localhost:8080/trac/wiki/MediaWiki"&gt;MediaWiki&lt;/a&gt; topics.
&lt;/p&gt;
&lt;p&gt;
Traditionally, help pages have been scattered on countless wikis and poorly translated; most of those on mediawiki.org were migrated with the help of some Google Code-in students.
&lt;/p&gt;
&lt;h3 id="CSSrefreshforVector"&gt;CSS refresh for Vector&lt;/h3&gt;
&lt;ul&gt;&lt;li&gt;Various Vector CSS properties have been converted to LESS variables.
&lt;/li&gt;&lt;li&gt;The font size of &lt;tt&gt;#bodyContent&lt;/tt&gt;/&lt;tt&gt;.mw-body-content&lt;/tt&gt; has been increased to 0.875em.
&lt;/li&gt;&lt;li&gt;The line-height of &lt;tt&gt;#bodyContent&lt;/tt&gt;/&lt;tt&gt;.mw-body-content&lt;/tt&gt; has been increased to 1.6.
&lt;/li&gt;&lt;li&gt;The line-height of superscript (sup) and subscript (sub) are now set to 1.
&lt;/li&gt;&lt;li&gt;The default color for content text (but not the headers) is now #252525; (dark grey).
&lt;/li&gt;&lt;li&gt;All headers have updated sizes and margins.
&lt;/li&gt;&lt;li&gt;H1 and H2 headers now use a serif font.
&lt;/li&gt;&lt;li&gt;Body font is "sans-serif" as always.
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
For more information see Typography refresh.
&lt;/p&gt;
&lt;h3 id="Configuration"&gt;Configuration&lt;/h3&gt;
&lt;p&gt;
Add Config and GlobalConfig classes:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Allows configuration options to be fetched from context.
&lt;/li&gt;&lt;li&gt;Only one implementation, GlobalConfig, is provided, which simply returns $GLOBALS[$name]. There can be more classes in the future, possibly a database-based one. For convinience the "wg" prefix is automatically added.
&lt;/li&gt;&lt;li&gt;This adds the $wgConfigClass global variable which is used to determine which implementation of Config to use by default.
&lt;/li&gt;&lt;li&gt;The ContextSource getConfig and setConfig methods were introduced.
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Full release notes:
&lt;a class="ext-link" href="https://git.wikimedia.org/blob/mediawiki%2Fcore.git/1.23.0/RELEASE-NOTES-1.23"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://git.wikimedia.org/blob/mediawiki%2Fcore.git/1.23.0/RELEASE-NOTES-1.23&lt;/a&gt;
&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;hr /&gt;
&lt;p&gt;
Download:
&lt;a class="ext-link" href="http://download.wikimedia.org/mediawiki/1.23/mediawiki-1.23.0.tar.gz"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://download.wikimedia.org/mediawiki/1.23/mediawiki-1.23.0.tar.gz&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
GPG signatures:
&lt;a class="ext-link" href="http://download.wikimedia.org/mediawiki/1.23/mediawiki-1.23.0.tar.gz.sig"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://download.wikimedia.org/mediawiki/1.23/mediawiki-1.23.0.tar.gz.sig&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Public keys:
&lt;a class="ext-link" href="https://www.mediawiki.org/keys/keys.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.mediawiki.org/keys/keys.html&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
I'd suggest we upgrade to this version and then perhaps stick with it, only doing security updates, until we need to move to another version due to it no longer being supported or because we need some new functionality.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/736#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/745</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/745</guid>
        <title>#745: Upgrade to BOA-2.2.6 Stable Edition</title>
        <pubDate>Mon, 23 Jun 2014 09:32:31 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
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;p&gt;
There is new BOA-2.2.6 Stable Edition 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;
Reading through the change log there doesn't appear to be anything of note that directly effects us, the new php versions:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;PHP 5.4.28
&lt;/li&gt;&lt;li&gt;PHP 5.5.12
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Don't as we are still on &lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/reports/status/php"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;PHP Version 5.3.28&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
I think it would be worth doing this update one evening this week just to keep upto date with BOA.
&lt;/p&gt;
&lt;p&gt;
Previous updates: &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer#Upgradetickets"&gt;wiki:PuffinServer#Upgradetickets&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/745#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/725</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/725</guid>
        <title>#725: Upgrade to BOA-2.2.5</title>
        <pubDate>Fri, 02 May 2014 08:49:22 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
&lt;strong&gt;Note this ticket was opened to upgrade to BOA-2.2.4 but when the upgrade was done BOA-2.2.5 was out so BOA-2.2.4 was skipped&lt;/strong&gt;
&lt;/p&gt;
&lt;p&gt;
From the Changelog at &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;pre class="wiki"&gt;### Stable BOA-2.2.4 Release - Full Edition
### Date: Wed Apr 30 17:03:36 PDT 2014
### Includes Aegir 2.x-boa-custom version.
# Release Notes:
  This release includes several bug fixes along with five updated platforms,
  plus some hot-fixes applied to previous stable after its release. We have
  also added a fix for known problem is recent Drupal 7.27 [#2245331] hence
  the change from Drupal 7.27.1 to 7.27.2 in all D7 platforms.
# Important - Read This First! (for self-hosted BOA only)
  If you haven't run full barracuda+octopus upgrade to latest BOA Stable
  Edition yet, don't use any partial upgrade modes explained in docs/UPGRADE.txt
  Once new BOA Stable is released, you must run *full* upgrades with commands:
  $ barracuda up-stable
  $ octopus up-stable all both
  For silent, logged mode with e-mail message sent once the upgrade is
  complete, but no progress is displayed in the terminal window, you can run
  alternatively, starting with screen session to avoid incomplete upgrade
  if your SSH session will be closed for any reason before the upgrade
  will complete:
  $ screen
  $ barracuda up-stable log
  $ octopus up-stable all both log
  Note that the silent, non-interactive mode will automatically say Y/Yes
  to all prompts and is thus useful to run auto-upgrades scheduled in cron.
  If you have skipped some recent BOA releases, and you have new default config
  option: _PERMISSIONS_FIX=NO in your /root/.barracuda.cnf configuration file,
  plus, you are not sure if you follow best practices for managing permissions
  as recommended in our docs: https://omega8.cc/node/116 then we recommend
  that you change it to _PERMISSIONS_FIX=YES temporarily, or even permanently
  if your VPS is fast enough, and then run this powerful script as root:
  $ bash /var/xdrago/daily.sh
  Note that BOA 'legacy' mode is still at version 2.1.3
# Updated Octopus platforms:
  ### Drupal 7.27.2
  Commerce 1.25 ---------------- https://drupal.org/project/commerce_kickstart
  Commerce 2.14 ---------------- https://drupal.org/project/commerce_kickstart
  Commons 3.11 ----------------- https://drupal.org/project/commons
  Panopoly 1.5 ----------------- https://drupal.org/project/panopoly
  ### Pressflow 6.31.1
  Commons 2.17 ----------------- https://drupal.org/project/commons
  Note: Always read and follow upgrade procedure if explained in the distro
  release notes, like for Panopoly 1.5 at https://drupal.org/node/2255133
# New o_contrib modules:
  * print-6.x-1.19 (includes patch to auto-detect /usr/bin/wkhtmltopdf)
  * print-7.x-2.0  (includes patch to auto-detect /usr/bin/wkhtmltopdf)
# New features and enhancements in this release:
  * Support for session.gc_maxlifetime configurable via INI files.
  You can control session garbage collector (EOL) per site and per platform.
  The value (in seconds) of the session_gc_eol variable is used as
  session.gc_maxlifetime value and specifies the number of seconds after which
  data will be seen as 'garbage' and potentially cleaned up, resulting with
  $_SESSION variable discarded and affected authenticated users logged out.
  BOA default defined in the system level global.inc file is 86400 == 24h.
# Changes in this release:
  * Drush: Upgrade command line version 6 to mini-6-26-04-2014
  * Nginx: Use higher defaults for limit_conn to avoid error 503 (CloudFlare)
  * Nginx: Use more aggressive limits against spambots trying to rgstr accounts.
  * Redis: Integration module (the modern variant) upgrade to 7.x-2.x-o8-2.6-B
# System upgrades in this release:
  * Nginx 1.7.0
  * PHP 5.5.12
  * Redis 2.8.9
# Fixes in this release:
  * Add symlinks in the home directory if missing (every 5 minutes).
  * Add warning that Compass Tools install and upgrade may take a LONG time.
  * Always define _PHP_CN variable properly.
  * Do not delete symlinks to wrappers to avoid false LFD alarms.
  * Fix for 'Force backward compatible SERVER_SOFTWARE'.
  * Fix in websh for _IN_PATH logic to not break backend Drush tasks.
  * Fix the logic for wrappers update and symlinks.
  * Force MariaDB 5.5 re-install if installed version doesn't match latest.
  * Improve status messages to display when silent mode is used on upgrade.
  * Improve whitelisting in the websh wrapper.
  * Issue #2238805 - Command filtering - no word containing *drush* is allowed.
  * Issue #2241495 - wkhtmltopdf stopped working after upgrade.
  * Issue #2247997 - Update docs/REMOTE.txt with workaround for websh issue.
  * Issue #2250397 - Always follow (limited) redirects in cURL requests.
  * Issue #GH-304  - [rvm] use $_RUBY_VERSION as default.
  * Issue #GH-305  - Check disk usage before running install/upgrade.
  * Issue #GH-306  - Allow ruby 1.8 to remain installed.
  * Nginx: Allow to configure keywords for aggressive requests rate monitoring.
  * Nginx: Sync FastCGI timeouts with other Nginx and PHP-FPM defaults.
  * PHP: Add /opt/local/bin/php tmp symlink on barracuda/octopus upgrade.
  * PHP: Allow to set custom _PHP_FPM_TIMEOUT but not lower than 60 (in seconds)
  * PHP: Always respect _PHP_FPM_WORKERS variable if set to numeric value &amp;gt; 0
  * PHP: Better defaults for realpath_cache_ttl and realpath_cache_size.
  * PHP: Fix for CVE-2014-0185 privilege escalation in FPM (doesn't affect BOA)
  * PHP: pm.max_children was not properly updated on FPM version self-switch.
  * PHP: Sync incorrect default_socket_timeout with max_execution_time (180s).
  * PHP: Use 30s for pm.process_idle_timeout - it prevents too high RAM usage.
  * PHP: Variable _PROCESS_MAX_FPM is not used on the Satellite Instance level.
  * Postfix: Force re-install if broken permisions detected on upgrade.
  * Prevent duplicate cron invocations with more strict delays.
  * Shell: Proper fix for wildcard in the path (cd command only)
  * Standardize install and upgrade for Chive, SQL Buddy and CGP.
  * Sync Redis timeout with default FPM timeout (180s).
  * Sync SQL connect_timeout with default mysql.connect_timeout in PHP (60s).
  * Update the logic for multi-version PHP support in BOND.
  * Update the logic for multi-version PHP support in docs/REMOTE.txt
&lt;/pre&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/725#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/721</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/721</guid>
        <title>#721: Upgrade to BOA-2.2.3 Stable Edition</title>
        <pubDate>Sat, 19 Apr 2014 05:58:00 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
&lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;wiki:PuffinServer&lt;/a&gt; has sent this email:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
There is new BOA-2.2.3 Stable Edition 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;
The Changelog contains:
&lt;/p&gt;
&lt;pre class="wiki"&gt;
### Stable BOA-2.2.3 Release - Full Edition
### Date: Fri Apr 18 12:57:40 PDT 2014
### Includes Aegir 2.x-boa-custom version.
# Release Notes:
  This release includes several bug fixes and security upgrades both for the
  system services and Drupal core, along with three updated platforms and new
  features, including support for MariaDB 10.0 and Ubuntu 14.04 LTS Trusty.
# Important - Read This First! (for self-hosted BOA only)
  If you haven't run full barracuda+octopus upgrade to latest BOA Stable
  Edition yet, don't use any partial upgrade modes explained in docs/UPGRADE.txt
  Once new BOA Stable is released, you must run *full* upgrades with commands:
  $ barracuda up-stable
  $ octopus up-stable all both
  For silent, logged mode with e-mail message sent once the upgrade is
  complete, but no progress is displayed in the terminal window, you can run
  alternatively, starting with screen session to avoid incomplete upgrade
  if your SSH session will be closed for any reason before the upgrade
  will complete:
  $ screen
  $ barracuda up-stable log
  $ octopus up-stable all both log
  Note that the silent, non-interactive mode will automatically say Y/Yes
  to all prompts and is thus useful to run auto-upgrades scheduled in cron.
# Updated Octopus platforms:
  ### Drupal 7.27.1
  Guardr 1.3 ------------------- https://drupal.org/project/guardr
  Open Atrium 2.17 ------------- https://drupal.org/project/openatrium
  Recruiter 1.2 ---------------- https://drupal.org/project/recruiter
# New features and enhancements in this release:
  * Add docs/FAQ.txt
  * Add support for MariaDB 10.0 or 5.5 install via _DB_SERIES variable.
  * Add support for Ubuntu 14.04 LTS Trusty.
  * Improve auto-healing for multi-version PHP-FPM setup.
  * Improve docs/UPGRADE.txt
  * Improve health check for protected vhosts during live SSH-auth update.
# Changes in this release:
  * Issue #GH-299 - Force disable LESS developer mode on production sites.
  * Move custom scripts to /opt/local/bin/
  * Normalize localhost entry in /etc/hosts to avoid FQDN mapped to 127.0.0.1
  * PHP: Do not use separate FPM pool for cron if _PHP_FPM_DENY is empty.
# System upgrades in this release:
  * MariaDB 5.5.37
# Fixes in this release:
  * Add 'exit 0' line if missing.
  * Add /opt/local/bin to PATH by default.
  * Add symlinks for wrappers only temporarily.
  * Better gem uninstall options.
  * Compass: Multiple fixes for various expected gems versions install/upgrades.
  * Do not override lshell env_path in websh wrapper.
  * Do not use monitored bin path for custom scripts to avoid LFD false alarms.
  * Extra db GRANT for 127.0.0.1 not added when migrating site.
  * Improve auto-healing to create required directories in /var/run/ if missing.
  * Issue #2230269 - New Jetty 9 version overrides JETTY_PORT=8099 with 8080.
  * Issue #2235991 - Drush make needs better exceptions in websh wrapper.
  * Issue #2236475 - Clarify what the Legacy mode really means.
  * Issue #2238965 - Add missing path to switch_to_bash().
  * Issue #2241013 - Git commands should be whitelisted in websh wrapper.
  * Issue #2241495 - wkhtmltopdf stopped working after upgrade.
  * Issue #GH-301 - Update the list of restricted keywords for Octopus username.
  * Make sure that permissions on Chive Manager dir/files are correct.
  * Note: _SSL_FROM_SOURCES=YES is ignored and not needed on Wheezy and Precise.
  * Remove the line with header TABLE_NAME (sqlmagic).
  * Reset PATH to avoid RVM overrides after Compass Tools install/upgrade.
  * Shell: Allow to run 'drush cache-clear drush' in any directory.
  * The _PHP_MODERN_ONLY variable is no longer used.
  * Ubuntu 14.04 LTS Trusty requires MariaDB 10.0
  * Use hostname -b instead of deprecated hostname -v.
&lt;/pre&gt;&lt;p&gt;
Note that we are already running the latest MariaDB, see &lt;a class="new ticket" href="http://localhost:8080/trac/ticket/692#comment:31" title="maintenance: Debian Updates (new)"&gt;ticket:692#comment:31&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
See also the last BOA upgrade ticket, BOA-2.2.2 &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/707" title="maintenance: Upgrade to BOA-2.2.2 (closed: fixed)"&gt;ticket:707&lt;/a&gt; and also &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/670" title="maintenance: Roll back performance customisations and use stock BOA settings where ... (closed: fixed)"&gt;ticket:670&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/721#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/707</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/707</guid>
        <title>#707: Upgrade to BOA-2.2.2</title>
        <pubDate>Wed, 26 Mar 2014 19:25:52 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
I have created a new ticket for this as I have found having one ticket (see &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/629" title="maintenance: Upgrade to BOA-2.1.3 Stable Edition (closed: wontfix)"&gt;ticket:629&lt;/a&gt;) for all BOA upgrades makes it really hard to review past upgrades.
&lt;/p&gt;
&lt;p&gt;
Upgrades from BOA-2.0.7 to BOA-2.1.1 did have their own tickets, see &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer#Upgradetickets"&gt;wiki:PuffinServer#Upgradetickets&lt;/a&gt; and unless there is a convincing reason not to have one ticket per upgrade I'd rather do it like this.
&lt;/p&gt;
&lt;p&gt;
Jim has pointed out on the Ttech list that:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
the v2.2.0 changelog is up as of a few days ago:
&lt;a class="ext-link" href="http://drupalcode.org/project/barracuda.git/blob/HEAD:/CHANGELOG.txt"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupalcode.org/project/barracuda.git/blob/HEAD:/CHANGELOG.txt&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
The Changelog starts:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;ul&gt;&lt;li&gt;Stable BOA-2.2.0 Release - Full Edition
&lt;/li&gt;&lt;li&gt;Date: TBD
&lt;/li&gt;&lt;li&gt;Includes Aegir 2.x-boa-custom version.
&lt;/li&gt;&lt;/ul&gt;&lt;ul&gt;&lt;li&gt;Release Notes:
&lt;/li&gt;&lt;/ul&gt;&lt;blockquote&gt;
&lt;p&gt;
There are many important changes and improvements in this release you should be aware of *before* running your BOA system upgrade.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;
Even if you are on a hosted BOA system with upgrades managed for you, it is very important to read at least this extensive release notes.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;
And if you are more curious, read also the big changelog further below, which covers only a small number of over 530 commits since BOA-2.1.3
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;/blockquote&gt;
&lt;p&gt;
I have yet to read the rest of the Changelog.
&lt;/p&gt;
&lt;p&gt;
There is also a task to copy the proposed changes to the BOA configuration in &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/629" title="maintenance: Upgrade to BOA-2.1.3 Stable Edition (closed: wontfix)"&gt;ticket:629&lt;/a&gt; over to this ticket.
&lt;/p&gt;
&lt;p&gt;
Should people other than chris and ed be CC's for this ticket?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/707#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/691</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/691</guid>
        <title>#691: Upgrade Wagn hosting for patterns site</title>
        <pubDate>Fri, 21 Feb 2014 16:53:43 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The &lt;a class="ext-link" href="http://patterns.transitionresearchnetwork.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://patterns.transitionresearchnetwork.org/&lt;/a&gt; site is running using a development set up and the webrick server falls over every now and then, so the plan is to upgrade to a production style setup.
&lt;/p&gt;
&lt;p&gt;
References:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/635" title="maintenance: Transition Research Patterns WEBrick monitoring (closed: wontfix)"&gt;ticket:635&lt;/a&gt; webrick server problems
&lt;/li&gt;&lt;li&gt;&lt;a class="wiki" href="http://localhost:8080/trac/wiki/TransitionResearchWagn"&gt;wiki:TransitionResearchWagn&lt;/a&gt; documentation
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/561" title="maintenance: Move Transition Research patterns Wagn website onto Penguin (closed: fixed)"&gt;ticket:561&lt;/a&gt; the last install
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="http://wagn.org/installation"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://wagn.org/installation&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/691#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/535</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/535</guid>
        <title>#535: Upgrade Puffin, Penguin and Parrot from Debian Squeeze to Wheezy</title>
        <pubDate>Fri, 26 Apr 2013 18:49:16 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Debian 7 is &lt;a class="ext-link" href="http://bits.debian.org/2013/04/release-date.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;due out on 5th May 2013&lt;/a&gt; and &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; will need upgrading.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/535#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/732</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/732</guid>
        <title>#732: Upgrade Piwik to 2.3.0</title>
        <pubDate>Tue, 27 May 2014 09:21:24 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;blockquote class="citation"&gt;
&lt;p&gt;
Piwik 2.3.0 is a new major release of Piwik!
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="http://piwik.org/changelog/piwik-2-3-0/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://piwik.org/changelog/piwik-2-3-0/&lt;/a&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/732#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/664</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/664</guid>
        <title>#664: Upgrade Piwik to 2.0.2</title>
        <pubDate>Tue, 24 Dec 2013 14:35:06 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This is a bugfix version which fixes 3 issues, see &lt;a class="ext-link" href="http://piwik.org/changelog/piwik-2-0-1/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://piwik.org/changelog/piwik-2-0-1/&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Upgrade notes are here, &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PiwikServer#Updates"&gt;wiki:PiwikServer#Updates&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/664#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/706</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/706</guid>
        <title>#706: Upgrade Mediawiki to 1.22.5 and install the new VisualEditor</title>
        <pubDate>Wed, 26 Mar 2014 15:46:03 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/2014-March/000144.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 Thursday, March 27th between 17:00-18:00 UTC (Thursday, March 27th, 9:00-10:00am PST) we will release security and maintenance 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.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/706#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/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/620</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/620</guid>
        <title>#620: Upgrade MediaWiki to 1.19.9</title>
        <pubDate>Fri, 15 Nov 2013 14:57:58 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
See the announcement email:
&lt;/p&gt;
&lt;pre class="wiki"&gt;I would like to announce the release of MediaWiki 1.21.3, 1.20.8 and
1.19.9. These releases fix 2 security related bugs that could affect users
of MediaWiki. Download links are given at the end of this email.
* Kevin Israel (Wikipedia user PleaseStand) identified and reported two
vectors for injecting Javascript in CSS that bypassed MediaWiki's blacklist
(CVE-2013-4567, CVE-2013-4568).
&amp;lt;https://bugzilla.wikimedia.org/show_bug.cgi?id=55332&amp;gt;
* Internal review while debugging a site issue discovered that MediaWiki
and the CentralNotice extension were incorrectly setting cache headers when
a user was autocreated, causing the user's session cookies to be cached,
and returned to other users (CVE-2013-4572).
&amp;lt;https://bugzilla.wikimedia.org/show_bug.cgi?id=53032&amp;gt;
Additionally, the following extensions have been updated to fix security
issues:
* CleanChanges: MediaWiki steward Teles reported that revision-deleted IP's
are not correctly hidden when this extension is used (CVE-2013-4569).
&amp;lt;https://bugzilla.wikimedia.org/show_bug.cgi?id=54294&amp;gt;
* ZeroRatedMobileAccess: Tomasz Chlebowski reported an XSS vulnerability
(CVE-2013-4573).
&amp;lt;https://bugzilla.wikimedia.org/show_bug.cgi?id=55991&amp;gt;
* CentralAuth: MediaWiki developer Platonides reported a login CSRF in
CentralAuth (CVE-2012-5394).
&amp;lt;https://bugzilla.wikimedia.org/show_bug.cgi?id=40747&amp;gt;
Full release notes for 1.21.3:
&amp;lt;https://www.mediawiki.org/wiki/Release_notes/1.21&amp;gt;
Full release notes for 1.20.8:
&amp;lt;https://www.mediawiki.org/wiki/Release_notes/1.20&amp;gt;
Full release notes for 1.19.9:
&amp;lt;https://www.mediawiki.org/wiki/Release_notes/1.19&amp;gt;
For information about how to upgrade, see
&amp;lt;https://www.mediawiki.org/wiki/Manual:Upgrading&amp;gt;
&lt;/pre&gt;&lt;p&gt;
The steps followed for the last upgrade can be followed again, see &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/595" title="maintenance: Upgrade Mediawiki to 1.19.8 from 1.19.7 (closed: fixed)"&gt;ticket:595&lt;/a&gt; and see also the documentation at &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PenguinServer#wiki.transitionnetwork.org"&gt;wiki:PenguinServer#wiki.transitionnetwork.org&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/620#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/699</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/699</guid>
        <title>#699: Update Core &amp; Plugins on transitionculture.org</title>
        <pubDate>Mon, 10 Mar 2014 11:46:33 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
This site needs an update.
&lt;/p&gt;
&lt;p&gt;
I'll do a database backup then update it.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/699#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/567</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/567</guid>
        <title>#567: Update BOA for new Redis 2.6.14</title>
        <pubDate>Tue, 02 Jul 2013 11:10:27 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
A suggestion from Jim:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
BOA now includes Redis
2.6.14 &amp;lt;&lt;a class="ext-link" href="https://raw.github.com/antirez/redis/2.6/00-RELEASENOTES"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://raw.github.com/antirez/redis/2.6/00-RELEASENOTES&lt;/a&gt;&amp;gt; if
you do a 'barracda up-stable system'... What interests me about this is
these lines from the changelog:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
UPGRADE URGENCY: HIGH because of the following two issues:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Lua scripting + Replication + AOF in slaves problem (see Issue #1164).
&lt;/li&gt;&lt;li&gt;AOF + expires possible race condition (see Issue #1079).
&lt;/li&gt;&lt;/ul&gt;&lt;/blockquote&gt;
&lt;p&gt;
It's a long shot, but that could maybe be part of the issue we've seen
recently.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
I'm not sure if this is best done now or later tonight when the site is less busy?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/567#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/900</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/900</guid>
        <title>#900: Unusal High Load on Puffin</title>
        <pubDate>Sun, 31 Jan 2016 12:24:40 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
For the first time since the BOA cron jobs were commented out we have had some very high loads on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;PuffinServer&lt;/a&gt;, this is shown in the &lt;a class="ext-link" href="https://penguin.transitionnetwork.org/munin/transitionnetwork.org/puffin.transitionnetwork.org/index.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Munin graphs&lt;/a&gt;, I'll post some specific ones in comments to this ticket.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/900#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/845</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/845</guid>
        <title>#845: Unneeded FTP server on PuffinServer</title>
        <pubDate>Mon, 13 Apr 2015 11:03:12 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The BOA stack installs and runs a FTP server, which we don't need as we use SSH/SFTP and it therefore causes a unneeded load, see &lt;a class="new ticket" href="http://localhost:8080/trac/ticket/692#comment:177" title="maintenance: Debian Updates (new)"&gt;ticket:692#comment:177&lt;/a&gt; for an example.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/845#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/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/842</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/842</guid>
        <title>#842: Trac fetchmail</title>
        <pubDate>Thu, 02 Apr 2015 12:54:11 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
There is a new SSL/TLS certificate at mail.webarch.net so these steps need following: &lt;a class="wiki" href="http://localhost:8080/trac/wiki/TransitionTrac#Fetchmail"&gt;wiki:TransitionTrac#Fetchmail&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/842#changelog</comments>
    </item><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/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/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/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/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/654</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/654</guid>
        <title>#654: TIs appearing in 'TIs by list' view without a number</title>
        <pubDate>Thu, 12 Dec 2013 12:43:12 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Some TIs are appearing in the 'Initiatives by number' view - but don't have numbers:
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/initiatives/by-number"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/initiatives/by-number&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
for Sam to invesitage and solve or put to techs in January
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/654#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/826</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/826</guid>
        <title>#826: Switching MX records from United to Google</title>
        <pubDate>Thu, 15 Jan 2015 17:15:41 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
TN are switching the MX records from United to Google on Friday 23/1/15.
&lt;/p&gt;
&lt;p&gt;
Will this affect the website/Web Architects in any way that we need to plan for in advance? Scripts, web forms etc? Anything you can think of?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/826#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/724</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/724</guid>
        <title>#724: Subscription emails from Rob's blog not arriving.</title>
        <pubDate>Tue, 29 Apr 2014 09:21:12 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
A user has got in touch to let us know he is not getting Rob's updates by email. He's still subscribed.
&lt;/p&gt;
&lt;p&gt;
I just checked my mail and the last one I received was on the 11/4. I'll have a look and see if I can work it out.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/724#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/839</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/839</guid>
        <title>#839: Stable BOA-2.4.1 Release</title>
        <pubDate>Tue, 24 Mar 2015 10:44:41 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
BOA appears to have stopped sending email to notify that new versions are available, I just manually checked the &lt;a class="ext-link" href="https://github.com/omega8cc/boa/blob/master/CHANGELOG.txt"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Changelog&lt;/a&gt; and discovered that BOA-2.4.1 came out on 8th March 2015:
&lt;/p&gt;
&lt;pre class="wiki"&gt;### Stable BOA-2.4.1 Release - Full Edition
### Date: Sun Mar  8 14:56:51 PDT 2015
### Milestone URL: https://github.com/omega8cc/boa/milestones/2.4.1
### Latest hotfix added on: Wed Mar 11 11:58:52 PDT 2015
  @=&amp;gt; Includes Aegir Hostmaster 2.x-head with improvements
  @=&amp;gt; Includes Aegir Provision 3.x-head with improvements
  @=&amp;gt; Includes Drush 7.0.0-alpha9 customized for BOA
# Release Notes:
  This new BOA release includes one new and 12 updated Aegir platforms,
  8 new features and enhancements, 15 new software versions, 10 other changes,
  plus over 38 bug fixes, with most notable features and changes listed below:
  @=&amp;gt; Add duobackboa with /root/.duobackboa.cnf file to run duplicate backups
  @=&amp;gt; Add SSL with TLS/SNI on server with one IP, multiple certificates support
  @=&amp;gt; Add support for Octopus batch migration - see docs/MIGRATE.txt for details
  @=&amp;gt; Allow to use _PHP_GEOS=YES with all PHP versions
# New Octopus platforms:
  OpenAid 2.0 ------------------ https://drupal.org/project/openaid
# Updated Octopus platforms:
  Commerce 1.33 ---------------- https://drupal.org/project/commerce_kickstart
  Commerce 2.21 ---------------- https://drupal.org/project/commerce_kickstart
  Commons 2.22 ----------------- https://drupal.org/project/commons
  Commons 3.22 ----------------- https://drupal.org/project/commons
  Drupal 8.0.0-b7 -------------- https://drupal.org/drupal-8.0
  Guardr 2.8 ------------------- https://drupal.org/project/guardr
  OpenAtrium 2.32 -------------- https://drupal.org/project/openatrium
  OpenChurch 2.1-b5 ------------ https://drupal.org/project/openchurch
  OpenOutreach 1.16 ------------ https://drupal.org/project/openoutreach
  OpenScholar 3.20.0 ----------- http://theopenscholar.org
  Panopoly 1.18 ---------------- https://drupal.org/project/panopoly
  Recruiter 1.5 ---------------- https://drupal.org/project/recruiter
# New features and enhancements:
  * Add compatibility with latest VS beng kernel
  * Add duobackboa with /root/.duobackboa.cnf file to run duplicate backups
  * Add support for multivalued fields in SOLR 4 - pull request #626
  * Add support for mysqladmin proc logging
  * Add support for Octopus batch migration - see docs/MIGRATE.txt for details
  * Add support for scout/mysql monitoring
  * CSF: Add popular ports 222 and 2222 to TCP_OUT by default
  * SSL with TLS/SNI on server with one IP, multiple certificates - fixes #465
# Changes:
  * Allow to run automated SQL conversion only weekly
  * Allow to use _PHP_GEOS=YES with all PHP versions
  * Do not send extra nocache cookie on GET requests
  * Drush mini-7-07-03-2015
  * Make barracuda wrapper available on initial install to avoid confusion
  * Nginx: Update for crawlers exceptions list
  * Redis Integration Module: Update to version mod-05-03-2015
  * Remove dependency on legacy Drush 4
  * Use latest Apache Solr Search 6.x-3.x config
  * Use latest Apache Solr Search 7.x-1.x config
# System upgrades:
  * Apache Solr 4.9.1
  * cURL 7.41.0 (if installed from sources)
  * Git 2.3.0 (if installed from sources)
  * Jetty 9.2.7.v20150116
  * MariaDB 10.0.17
  * MariaDB 5.5.42
  * MariaDB Galera Cluster 10.0.17
  * Nginx 1.7.10
  * OpenSSL 1.0.2 (if installed from sources)
  * PHP 5.4.38
  * PHP 5.5.22
  * PHP 5.6.6
  * PHP: ionCube loader 4.7.4
  * Pure-FTPd 1.0.37
  * Ruby 2.2.1
  * Use duplicity 0.7.01 and boto 2.36.0 - fixes #630
  * Vnstat 1.13
# Fixes:
  * [provision] False "load on system too heavy" messages - fixes #619
  * [provision] Issue #2350695 - Profile is registered twice, also as a module
  * [provision] Nginx: Remove webform keyword from regex locations - fixes #599
  * Add also manage_ltd_users to the list - fixes #616
  * Avoid installing New Relic with no valid license key provided - fixes #608
  * Do not add no longer used symlink
  * Do not create conflicting plain HTTP proxy for single IP mode - fixes #465
  * Do not delete backboa while duplicity is running
  * Do not replace any contrib in latest OA - fixes #2420131
  * Do not run D7 core hotfix on already fixed instances
  * Fix for legacy systems autoupdate logic
  * Fix for missing chattr -i on web user update
  * Fix for missing datestamp
  * Fix for too dangerous pdnsd auto-config logic
  * Fix pdnsd restarts procedures - fixes #610
  * Fix permissions for pdnsd if needed
  * Fix variable in autoupboa - pull request #629
  * Force php.ini update
  * Hotfix for cluster instances
  * Hotfix for OpenSSL/cURL versions out of sync
  * How to enable permanent redirect to HTTPS with single IP - #465
  * Issue #2425963 - Broken slider in Commerce Kickstart 2.21
  * Make sure that @hostmaster alias works after migration
  * Provide a patch for older civicrm versions to make them Drush 7 compatible
  * Randomize backups schedule to avoid issues with AWS limits
  * Reload nginx service automatically - #465
  * Remove conflicting pdnsd restarts to avoid race conditions - fixes #610
  * Remove deprecated sysctl options
  * Remove post-install leftovers if needed
  * Single PHP-version installation fails - fixes #598
  * Typo - fixes #539
  * Unable to connect to SOLR on latest head - fixes #623
  * Update installers as expected, also with _SKYNET_MODE=OFF - fixes #644
  * Update meta-installers for new stable
  * Update the upgrade procedure how-to - fixes ##616
  * Use civicrm-4.5.6 compatible with Drush 7
  * Use correct AWS Endpoint when us-east-1 Region is specified
  * Use correct open_basedir for lshell user - fixes #603
  * Use separate loops for symlinks and ghost cleanup
  * Workaround for EntityMalformedException in Open Outreach - fixes #229
  * Workaround for missing interface/lo.pdnsd on legacy systems
  * Workaround for SA-CONTRIB-2015-063 - Webform - Cross Site Scripting
&lt;/pre&gt;&lt;p&gt;
I'll run the upgrade one evening this week.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/839#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/827</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/827</guid>
        <title>#827: Stable BOA-2.4.0 Release</title>
        <pubDate>Mon, 19 Jan 2015 20:11:09 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
No release date yet, but lots of detail in the Changelog:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://github.com/omega8cc/boa/blob/master/CHANGELOG.txt"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://github.com/omega8cc/boa/blob/master/CHANGELOG.txt&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
2.4.0 issues:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://github.com/omega8cc/boa/milestones/2.4.0"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://github.com/omega8cc/boa/milestones/2.4.0&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/827#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/844</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/844</guid>
        <title>#844: Stable BOA 2.4.2 Release</title>
        <pubDate>Fri, 10 Apr 2015 10:34:56 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Looks like all the tickets for BOA 2.4.2 have been closed and it is due to be released today:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://github.com/omega8cc/boa/milestones"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://github.com/omega8cc/boa/milestones&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
The Changelog has not yet been updated:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://github.com/omega8cc/boa/blob/master/CHANGELOG.txt"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://github.com/omega8cc/boa/blob/master/CHANGELOG.txt&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
For some unknown reason BOA no longer sends emails when a new version is out so the Changelog will need checking manually.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/844#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/677</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/677</guid>
        <title>#677: Spike in MyISAM (search) database activity, Redis unable to cache such requests</title>
        <pubDate>Wed, 15 Jan 2014 10:49:33 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Since Sunday there has been a marked increase in MySQL activity and also a drop in Redis memory use, I suspect these things are related.
&lt;/p&gt;
&lt;p&gt;
I'll post some Munin graphs below to illustrate this.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/677#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/656</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/656</guid>
        <title>#656: Spam being sent out via Transition Culture</title>
        <pubDate>Sat, 14 Dec 2013 14:48:21 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
I'm getting several of thee day day:
&lt;/p&gt;
&lt;pre class="wiki"&gt;From: Mail Delivery System &amp;lt;Mailer-Daemon@parrot.webarch.net&amp;gt;
Date: Sat, 14 Dec 2013 13:21:02 +0000
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:
  inxzkysnf@gmail.com
    SMTP error from remote mail server after RCPT TO:&amp;lt;inxzkysnf@gmail.com&amp;gt;:
    host gmail-smtp-in.l.google.com [173.194.78.26]:
    550-5.1.1 The email account that you tried to reach does not exist. Please try
    550-5.1.1 double-checking the recipient's email address for typos or
    550-5.1.1 unnecessary spaces. Learn more at
    550 5.1.1 http://support.google.com/mail/bin/answer.py?answer=6596 l11si2175565wjw.16 - gsmtp
------ 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 1Vrp9L-0002BF-Kf
        for inxzkysnf@gmail.com; Sat, 14 Dec 2013 13:20:56 +0000
To: inxzkysnf@gmail.com
Subject: Thanks for your message
X-PHP-Originating-Script: 1011:lib_nonajax.php
From: robjhopkins@gmail.com
Reply-To: robjhopkins@gmail.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----MIME_BOUNDRY_main_message"
Message-Id: &amp;lt;E1Vrp9L-0002BF-Kf@parrot.webarch.net&amp;gt;
Date: Sat, 14 Dec 2013 13:20:55 +0000
This is a multi-part message in MIME format.
------MIME_BOUNDRY_main_message
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: quoted-printable
Dear timberland france,
Thank you for your message on the Transition Culture website - I will get back to you as soon as possible.
------MIME_BOUNDRY_main_message
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
&amp;lt;!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"&amp;gt;
&amp;lt;HTML&amp;gt;&amp;lt;BODY&amp;gt;
&amp;lt;div style=3D"font:normal 1em arial; margin-top:10px"&amp;gt;&amp;lt;p&amp;gt;&amp;lt;strong&amp;gt;Dear timberland france,&amp;lt;/strong&amp;gt;&amp;lt;/p&amp;gt;
&amp;lt;p&amp;gt;Thank you for your message on the Transition Culture website - I will get back to you as soon as possible.
&amp;lt;div style=3D"width:80%; background:#f4faff ; color:#aaa; font-size:11px; padding:10px; margin-top:20px"&amp;gt;&amp;lt;strong&amp;gt;This is an automatic
+confirmation message. 14 December, 2013.&amp;lt;/strong&amp;gt;&amp;lt;/div&amp;gt;&amp;lt;/div&amp;gt;&amp;lt;/BODY&amp;gt;&amp;lt;/HTML&amp;gt;
&lt;/pre&gt;&lt;p&gt;
It appears to be spam sent fro the Transition Culture &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; site to a Gnmail user who doesn't exist.
&lt;/p&gt;
&lt;p&gt;
It appears, from the email headers that this form is being used for the spamming &lt;tt&gt;/home/tc/sites/default/wp-content/plugins/contactforms/lib_nonajax.php&lt;/tt&gt;.
&lt;/p&gt;
&lt;p&gt;
This needs some more investigation.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/656#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/828</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/828</guid>
        <title>#828: Site down due to massive load spike 2015-01-29</title>
        <pubDate>Thu, 29 Jan 2015 17:09:07 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Seems to be recovering now, this ticket is to try to find the cause.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/828#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/576</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/576</guid>
        <title>#576: Site down</title>
        <pubDate>Thu, 01 Aug 2013 09:42:44 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Been down for 15 minutes by now I reckon
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/576#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/755</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/755</guid>
        <title>#755: Site administrator's file upload capacity: not responding to changes</title>
        <pubDate>Tue, 08 Jul 2014 09:21:16 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Rob Hopkins reached the limit for file uploads and could not upload any more images (not good for him as he writes posts with lots of pictures daily).
&lt;/p&gt;
&lt;p&gt;
Sam raised the limit. This change in the limit does not seem to have affected Rob's situation - he still can't upload any images.
&lt;/p&gt;
&lt;p&gt;
Looking at these settings:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/settings/uploads"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/settings/uploads&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Rob should be able to upload more - he is a site editor and admin - but he can't.
&lt;/p&gt;
&lt;p&gt;
Please investigate
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/755#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/687</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/687</guid>
        <title>#687: Set up cert expiry date checking for all SSL certs</title>
        <pubDate>Mon, 03 Feb 2014 13:35:01 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Last month the &lt;tt&gt;*.transitionnetwork.org&lt;/tt&gt; cert expired before it was replaced with a new one and users therefore got warnings for around half a day, see &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/685" title="task: SSL certificate about to expire? (closed: fixed)"&gt;ticket:685&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
A script to check the expiry dates was set up on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;wiki:PuffinServer&lt;/a&gt; on &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/685#comment:9" title="task: SSL certificate about to expire? (closed: fixed)"&gt;ticket:685#comment:9&lt;/a&gt; and this ticket is to document setting this up for &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;.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/687#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/557</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/557</guid>
        <title>#557: Set up a re-direct</title>
        <pubDate>Tue, 04 Jun 2013 15:21:18 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Please can you set up two re-direct/pointers
&lt;/p&gt;
&lt;p&gt;
from: "power.transitionnetwork.org"
to: "&lt;a class="ext-link" href="http://www.transitionnetwork.org/power-just-doing-stuff"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.transitionnetwork.org/power-just-doing-stuff&lt;/a&gt;"
&lt;/p&gt;
&lt;p&gt;
AND
&lt;/p&gt;
&lt;p&gt;
from: "&lt;a class="ext-link" href="http://www.thepowerofjustdoingstuff.org"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.thepowerofjustdoingstuff.org&lt;/a&gt;" (we own in gandi)
to: "&lt;a class="ext-link" href="http://www.transitionnetwork.org/power-just-doing-stuff"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.transitionnetwork.org/power-just-doing-stuff&lt;/a&gt;"
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/557#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/739</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/739</guid>
        <title>#739: Set up DEV and other drupal accounts for Annesley</title>
        <pubDate>Wed, 11 Jun 2014 14:38:42 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
is this you chris? or a sam job? or paul?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/739#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/599</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/599</guid>
        <title>#599: Server time drift</title>
        <pubDate>Sun, 29 Sep 2013 21:57:59 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The servers are not keeping good time at the moment.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/599#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/815</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/815</guid>
        <title>#815: Security updates need to be applied for a couple of contributed modules:</title>
        <pubDate>Tue, 16 Dec 2014 13:45:16 GMT</pubDate>
        
        <dc:creator>paul</dc:creator>

        <description>&lt;p&gt;
DBTNG
Hierarchical Select
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/815#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/920</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/920</guid>
        <title>#920: SSL weirdness?</title>
        <pubDate>Thu, 14 Jul 2016 20:20:19 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Chris
&lt;/p&gt;
&lt;p&gt;
So Paul put the site into maintenance mode, took a database dump and then tried to re-enable live mode using the drush command.
&lt;/p&gt;
&lt;p&gt;
It seems it came out of maintenance mode OK, but we're now getting this certificate error.
&lt;/p&gt;
&lt;p&gt;
I have changed the Zone file on Gandi in the meantime, but this doesn't seem to be propagating.
&lt;/p&gt;
&lt;p&gt;
Any ideas?
&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/920#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/685</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/685</guid>
        <title>#685: SSL certificate about to expire?</title>
        <pubDate>Thu, 23 Jan 2014 12:31:06 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Chris this dropped into my inbox this morning.
&lt;/p&gt;
&lt;p&gt;
Can you tell from the following if it's a certificate we still use? Does it need to be renewed?
&lt;/p&gt;
&lt;p&gt;
Thanks
&lt;/p&gt;
&lt;p&gt;
Sam
&lt;/p&gt;
&lt;p&gt;
---
&lt;/p&gt;
&lt;p&gt;
Hello,
&lt;/p&gt;
&lt;p&gt;
This mail is to inform you that your certificate SSL Standard (*.transitionnetwork.org) expires today, on 2014-01-24 00:59.
&lt;/p&gt;
&lt;p&gt;
Warning: for Pro and Business certificates, web browsers have increased security. It can now take up to several weeks, and so we strongly recommend that you perform the operation as soon as possible.
&lt;/p&gt;
&lt;p&gt;
If you would like to keep your certificate, we recommend renewing it today. For this you must launch the renewal process from the following page: &lt;a class="ext-link" href="https://www.gandi.net/admin/ssl/renew/26873"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.gandi.net/admin/ssl/renew/26873&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
If you do not want to keep your certificate, then no further action is necessary on your part. It will be automatically revoked by our services and rendered useless.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/685#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/795</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/795</guid>
        <title>#795: SHA1 Deprecation: Regenerate all certs using SHA256</title>
        <pubDate>Fri, 10 Oct 2014 20:37:49 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
SHA1 SSL certs and chains are now &lt;a class="ext-link" href="https://www.ssllabs.com/ssltest/analyze.html?d=patterns.transitionresearchnetwork.org"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;flagged at SSLLabs&lt;/a&gt;, see &lt;a class="ext-link" href="https://community.qualys.com/blogs/securitylabs/2014/09/09/sha1-deprecation-what-you-need-to-know"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;SHA1 Deprecation: What You Need to Know&lt;/a&gt;, however Gandi doesn't yet support SHA256, see &lt;a class="ext-link" href="https://shaaaaaaaaaaaaa.com/check/patterns.transitionresearchnetwork.org"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;SHAAAAAAAAAAAAA&lt;/a&gt; which links to &lt;a class="ext-link" href="https://twitter.com/gandibar/status/509116131173748736"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;this tweet&lt;/a&gt;, when they do support SHA256 all the keys, certs and chains will need updating.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/795#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/785</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/785</guid>
        <title>#785: SA-CONTRIB-2014-086 - Custom BreadCrumbs - Cross Site Scripting (XSS)</title>
        <pubDate>Thu, 11 Sep 2014 15:54:35 GMT</pubDate>
        
        <dc:creator>paul</dc:creator>

        <description>&lt;p&gt;
@Ed Would you check my choice of component; I was looking for maintenance?  Should I assign this to me as I create the ticket?
&lt;/p&gt;
&lt;p&gt;
View online: &lt;a class="ext-link" href="https://www.drupal.org/node/2336263"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/node/2336263&lt;/a&gt;
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Advisory ID: DRUPAL-SA-CONTRIB-2014-086
&lt;/li&gt;&lt;li&gt;Project: Custom Breadcrumbs &lt;a class="missing changeset" title="No default repository defined"&gt;[1]&lt;/a&gt; (third-party module)
&lt;/li&gt;&lt;li&gt;Version: 6.x, 7.x
&lt;/li&gt;&lt;li&gt;Date: 2014-September-10
&lt;/li&gt;&lt;li&gt;Security risk: 16/25 ( Critical)
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
AC:None/A:User/CI:Some/II:Some/E:Theoretical/TD:All &lt;a class="missing changeset" title="No default repository defined"&gt;[2]&lt;/a&gt;
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Vulnerability: Cross Site Scripting
&lt;/li&gt;&lt;/ul&gt;&lt;hr /&gt;
&lt;hr /&gt;
&lt;p&gt;
Custom Breadcrumbs allows administrators to set up parametrized breadcrumb
trails for different content types, views, panels, taxonomy vocabularies and
terms, paths, and a simple API that allows contributed modules to enable
custom breadcrumbs for module pages and theme templates.
&lt;/p&gt;
&lt;p&gt;
User input is not properly sanitized in all use cases, opening a Cross Site
Scripting (XSS) vulnerability.
&lt;/p&gt;
&lt;p&gt;
The vulnerability is only present when the custom breadcrumb is configured
with the special identifier so that some of the breadcrumb items are
not links. Typical example is that the last breadcrumb element is showing the
current page title but is not a link. The XSS vulnerability is not triggered
if all items of the breadcrumb are links and special identifier is not
used.
&lt;/p&gt;
&lt;hr /&gt;
&lt;hr /&gt;
&lt;ul&gt;&lt;li&gt;/A CVE identifier &lt;a class="missing changeset" title="No default repository defined"&gt;[3]&lt;/a&gt; will be requested, and added upon issuance, in
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
accordance
with Drupal Security Team processes./
&lt;/p&gt;
&lt;hr /&gt;
&lt;hr /&gt;
&lt;ul&gt;&lt;li&gt;Custom Breadcrumbs 6.x-1.x versions prior to 6.x-1.6
&lt;/li&gt;&lt;li&gt;Custom Breadcrumbs 6.x-2.x versions are NOT affected
&lt;/li&gt;&lt;li&gt;Custom Breadcrumbs 7.x-2.x versions prior to 7.x-2.0-beta1
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Drupal core is not affected. If you do not use the contributed Custom
Breadcrumbs &lt;a class="missing changeset" title="No default repository defined"&gt;[4]&lt;/a&gt; module,
there is nothing you need to do.
&lt;/p&gt;
&lt;hr /&gt;
&lt;hr /&gt;
&lt;p&gt;
Install the latest version:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;If you use the Custom Breadcrumbs module version 1.x for Drupal 6.x,
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
upgrade to Custom Breadcrumbs 6.x-1.6 &lt;a class="missing changeset" title="No default repository defined"&gt;[5]&lt;/a&gt;.
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;If you use the Custom Breadcrumbs module version 2.x for Drupal 7.x,
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
upgrade to Custom Breadcrumbs 7.x-2.0-beta1 &lt;a class="missing changeset" title="No default repository defined"&gt;[6]&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
Also see the Custom Breadcrumbs &lt;a class="missing changeset" title="No default repository defined"&gt;[7]&lt;/a&gt; project page.
&lt;/p&gt;
&lt;hr /&gt;
&lt;hr /&gt;
&lt;ul&gt;&lt;li&gt;Markus Sipilä &lt;a class="missing changeset" title="No default repository defined"&gt;[8]&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;hr /&gt;
&lt;hr /&gt;
&lt;ul&gt;&lt;li&gt;Markus Sipilä &lt;a class="missing changeset" title="No default repository defined"&gt;[9]&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;Colan Schwartz &lt;a class="missing changeset" title="No default repository defined"&gt;[10]&lt;/a&gt; the module maintainer
&lt;/li&gt;&lt;/ul&gt;&lt;hr /&gt;
&lt;hr /&gt;
&lt;ul&gt;&lt;li&gt;Greg Knaddison &lt;a class="missing changeset" title="No default repository defined"&gt;[11]&lt;/a&gt; of the Drupal Security Team
&lt;/li&gt;&lt;/ul&gt;&lt;hr /&gt;
&lt;hr /&gt;
&lt;p&gt;
The Drupal security team can be reached at security at drupal.org or via the
contact form at &lt;a class="ext-link" href="https://www.drupal.org/contact"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/contact&lt;/a&gt; &lt;a class="missing changeset" title="No default repository defined"&gt;[12]&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
Learn more about the Drupal Security team and their policies &lt;a class="missing changeset" title="No default repository defined"&gt;[13]&lt;/a&gt;,
writing secure code for Drupal &lt;a class="missing changeset" title="No default repository defined"&gt;[14]&lt;/a&gt;, and
securing your site &lt;a class="missing changeset" title="No default repository defined"&gt;[15]&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[1]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/project/custom_breadcrumbs"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/project/custom_breadcrumbs&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[2]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/security-team/risk-levels"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/security-team/risk-levels&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[3]&lt;/a&gt; &lt;a class="ext-link" href="http://cve.mitre.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://cve.mitre.org/&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[4]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/project/custom_breadcrumbs"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/project/custom_breadcrumbs&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[5]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/node/2335705"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/node/2335705&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[6]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/node/2335721"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/node/2335721&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[7]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/project/custom_breadcrumbs"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/project/custom_breadcrumbs&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[8]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/user/109674"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/109674&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[9]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/user/109674"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/109674&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[10]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/user/58704"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/58704&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[11]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/user/36762"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/36762&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[12]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/contact"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/contact&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[13]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/security-team"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/security-team&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[14]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/writing-secure-code"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/writing-secure-code&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[15]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/security/secure-configuration"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/security/secure-configuration&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;span class="underline"&gt;&lt;/span&gt;&lt;span class="underline"&gt;&lt;/span&gt;&lt;span class="underline"&gt;&lt;/span&gt;&lt;span class="underline"&gt;&lt;/span&gt;&lt;span class="underline"&gt;&lt;/span&gt;&lt;span class="underline"&gt;&lt;/span&gt;&lt;span class="underline"&gt;&lt;/span&gt;&lt;span class="underline"&gt;&lt;/span&gt;&lt;span class="underline"&gt;&lt;/span&gt;&lt;span class="underline"&gt;&lt;/span&gt;&lt;span class="underline"&gt;&lt;/span&gt;&lt;span class="underline"&gt;_
Security-news mailing list
Security-news@…
Unsubscribe at &lt;a class="ext-link" href="https://lists.drupal.org/mailman/listinfo/security-news"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://lists.drupal.org/mailman/listinfo/security-news&lt;/a&gt;
&lt;/span&gt;&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/785#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/831</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/831</guid>
        <title>#831: Rob is having Image upload issues</title>
        <pubDate>Tue, 17 Feb 2015 11:37:09 GMT</pubDate>
        
        <dc:creator>ade</dc:creator>

        <description>&lt;p&gt;
Hi Paul,
Rob in Totnes is creating a blog post and is getting an error whilst trying to upload an image. Initially I thought it could have been a harddrive full issue, but we can see that we have drive room.
Sam and I have had a quick look to see if anything obvious, but we are now stumbling a bit. We can replicate the issue by trying to upload an image to a blog post, but cannot see where to find an event log to see if any logs are being generated that may aid in a diagnosis. Could you have a look and let us know your thoughts please? Rob is currently waiting to post a blog so is quite urgent.
&lt;/p&gt;
&lt;p&gt;
Many thanks
Ade
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/831#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/651</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/651</guid>
        <title>#651: Report for tools content type</title>
        <pubDate>Thu, 12 Dec 2013 11:33:22 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
For January:
set up a report for tools content type:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;downloadable in .xls
&lt;/li&gt;&lt;li&gt;tool title
&lt;/li&gt;&lt;li&gt;URL (must be a hyperlink generated in .csv)
&lt;/li&gt;&lt;li&gt;node reference
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
No tools report exists yet - but lots of others here:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/reports"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/reports&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/651#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/652</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/652</guid>
        <title>#652: Report for resource content type</title>
        <pubDate>Thu, 12 Dec 2013 11:34:49 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
For January:
set up a report for tools content type:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;downloadable in .xls
&lt;/li&gt;&lt;li&gt;resource title
&lt;/li&gt;&lt;li&gt;URL (must be a hyperlink generated in .csv)
&lt;/li&gt;&lt;li&gt;node reference
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
you will be able to work from this report:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/reports/resources"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/reports/resources&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/652#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/653</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/653</guid>
        <title>#653: Report for ingredients content type</title>
        <pubDate>Thu, 12 Dec 2013 11:36:53 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
For January:
set up a report for ingredients content type:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;downloadable in .xls
&lt;/li&gt;&lt;li&gt;ingredient title
&lt;/li&gt;&lt;li&gt;URL (must be a hyperlink generated in .csv)
&lt;/li&gt;&lt;li&gt;node reference
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
No ingredients report exists yet - but lots of others here:
​&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/reports"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/reports&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/653#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/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/545</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/545</guid>
        <title>#545: Registration page: 502</title>
        <pubDate>Wed, 08 May 2013 08:38:13 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
&lt;a class="ext-link" href="http://www.transitionnetwork.org/user/register"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.transitionnetwork.org/user/register&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
found a bunch of these yesterday - this one is still showing a 502...
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/545#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/730</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/730</guid>
        <title>#730: Redis Munin stats for puffin</title>
        <pubDate>Fri, 23 May 2014 08:38:33 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The Redis stats for &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;wiki:PuffinServer&lt;/a&gt; are not being generated:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://penguin.transitionnetwork.org/munin/transitionnetwork.org/puffin.transitionnetwork.org/index.html#redis"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://penguin.transitionnetwork.org/munin/transitionnetwork.org/puffin.transitionnetwork.org/index.html#redis&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/730#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/878</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/878</guid>
        <title>#878: Reconomy.org add subdomains</title>
        <pubDate>Thu, 15 Oct 2015 11:35:03 GMT</pubDate>
        
        <dc:creator>ade</dc:creator>

        <description>&lt;pre class="wiki"&gt;Hi Chris,
I thought I had added this as a ticket, but does not seem to have come
through.
I have had a request to add the following to the reconomy.org website.
I notice that i do not have permission to do this myself via gandi.net so
could you please add for me.
many thanks
Ade
We're going to need to point the REfund API to a particular subdomain
of the reconomy.org domain in the next few weeks. This will also apply
to the frontend. Is there anyone I can email about this?
Here are the proposed subdomains:
funds.reconomy.org
api.funds.reconomy.org
Both subdomains should point to this IP: 178.62.93.215
--
Ade Stuart
Web Manager - Transition network
07595 331877
The Transition Network is a registered charity
address: 43 Fore St, Totnes, Devon, TQ9 5HN, UK
website: www.transitionnetwork.org
TN company no: 6135675 TN charity no: 1128675
&lt;/pre&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/878#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/728</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/728</guid>
        <title>#728: Re-patch location module</title>
        <pubDate>Tue, 20 May 2014 12:53:16 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Bugger just realised that I didn't finish the pull request into the main branch: &lt;a class="ext-link" href="https://trac.transitionnetwork.org/trac/ticket/681"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://trac.transitionnetwork.org/trac/ticket/681&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
So the location module patch is not on the live site.
&lt;/p&gt;
&lt;p&gt;
I have now done the patch correctly I think: &lt;a class="ext-link" href="https://github.com/transitionnetwork/transitionnetwork.org-d6.profile/pull/2"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://github.com/transitionnetwork/transitionnetwork.org-d6.profile/pull/2&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Shall I additionally add the patch to the live site using Drush as I did before?
&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/728#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/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/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/718</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/718</guid>
        <title>#718: REconomy site showing adverts randomly</title>
        <pubDate>Thu, 10 Apr 2014 08:19:34 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Load &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; and the first time you get it, and other times at random and you get spam.
&lt;/p&gt;
&lt;p&gt;
URGENT check please - on REconomy and all WP sites...
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/718#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/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/674</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/674</guid>
        <title>#674: Puffin locked up</title>
        <pubDate>Tue, 14 Jan 2014 09:59:40 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This is on the console, no response via web or ssh :
&lt;/p&gt;
&lt;pre class="wiki"&gt;[4478428.894563]  [&amp;lt;ffffffff810f3634&amp;gt;] ? sys_readlinkat+0x25/0x8d
[4478428.894571]  [&amp;lt;ffffffff81011b42&amp;gt;] ? system_call_fastpath+0x16/0x1b
[4478428.894581] INFO: task cron:46009 blocked for more than 120 seconds.
[4478428.894587] "echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[4478428.894595] cron          D ffff8801fb270e20     0 46009   8829 0x00000080
[4478428.894606]  ffff8801fb270e20 0000000000000286 0000000000000001 00000001810423b0
[4478428.894617]  ffff88000bcf87c0 000000000000000b 000000000000f9e0 ffff8800cbb9dfd8
[4478428.894628]  00000000000157c0 00000000000157c0 ffff8801fa458000 ffff8801fa4582f8
[4478428.894640] Call Trace:
[4478428.894648]  [&amp;lt;ffffffff811976a6&amp;gt;] ? vsnprintf+0x40a/0x449
[4478428.894656]  [&amp;lt;ffffffff8130e5c3&amp;gt;] ? __mutex_lock_common+0x122/0x192
[4478428.894666]  [&amp;lt;ffffffff8130e6eb&amp;gt;] ? mutex_lock+0x1a/0x31
[4478428.894673]  [&amp;lt;ffffffff810f7eac&amp;gt;] ? do_lookup+0x80/0x15d
[4478428.894681]  [&amp;lt;ffffffff810f892c&amp;gt;] ? __link_path_walk+0x5a5/0x6f5
[4478428.894689]  [&amp;lt;ffffffff810f826a&amp;gt;] ? do_follow_link+0x1fa/0x317
[4478428.894697]  [&amp;lt;ffffffff810f86e0&amp;gt;] ? __link_path_walk+0x359/0x6f5
[4478428.894705]  [&amp;lt;ffffffff810f8caa&amp;gt;] ? path_walk+0x66/0xc9
[4478428.894713]  [&amp;lt;ffffffff810fa114&amp;gt;] ? do_path_lookup+0x20/0x77
[4478428.894721]  [&amp;lt;ffffffff810fa2a0&amp;gt;] ? do_filp_open+0xe5/0x94b
[4478428.894729]  [&amp;lt;ffffffff81012cdb&amp;gt;] ? xen_hypervisor_callback+0x1b/0x20
[4478428.894738]  [&amp;lt;ffffffff8130dda8&amp;gt;] ? thread_return+0x79/0xe0
[4478428.894746]  [&amp;lt;ffffffff811901fb&amp;gt;] ? _atomic_dec_and_lock+0x33/0x50
[4478428.894755]  [&amp;lt;ffffffff81103705&amp;gt;] ? alloc_fd+0x67/0x10c
[4478428.894763]  [&amp;lt;ffffffff810eeacf&amp;gt;] ? do_sys_open+0x55/0xfc
[4478428.894770]  [&amp;lt;ffffffff81011b42&amp;gt;] ? system_call_fastpath+0x16/0x1b
[4478669.197427] INFO: task vnstatd:1920 blocked for more than 120 seconds.
[4478669.197448] "echo 0 &amp;gt; /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[4478669.197458] vnstatd       D 0000000000000000     0  1920      1 0x00000000
[4478669.197469]  ffff8801ff18bf90 0000000000000282 ffff8801fa651e10 ffff880000009680
[4478669.197482]  0000000000000000 000000000000000a 000000000000f9e0 ffff8801fa651fd8
[4478669.197494]  00000000000157c0 00000000000157c0 ffff8801fe335bd0 ffff8801fe335ec8
[4478669.197505] Call Trace:
[4478669.197520]  [&amp;lt;ffffffff8130f6fa&amp;gt;] ? error_exit+0x2a/0x60
[4478669.197531]  [&amp;lt;ffffffff8101251d&amp;gt;] ? retint_restore_args+0x5/0x6
[4478669.197542]  [&amp;lt;ffffffff8130e5c3&amp;gt;] ? __mutex_lock_common+0x122/0x192
[4478669.197551]  [&amp;lt;ffffffff8130e6eb&amp;gt;] ? mutex_lock+0x1a/0x31
[4478669.197561]  [&amp;lt;ffffffff810f7eac&amp;gt;] ? do_lookup+0x80/0x15d
[4478669.197569]  [&amp;lt;ffffffff810f86aa&amp;gt;] ? __link_path_walk+0x323/0x6f5
[4478669.197577]  [&amp;lt;ffffffff810f8caa&amp;gt;] ? path_walk+0x66/0xc9
[4478669.197585]  [&amp;lt;ffffffff810fa114&amp;gt;] ? do_path_lookup+0x20/0x77
[4478669.197593]  [&amp;lt;ffffffff810fa2a0&amp;gt;] ? do_filp_open+0xe5/0x94b
[4478669.197602]  [&amp;lt;ffffffff8130f054&amp;gt;] ? _spin_lock_irqsave+0x15/0x34
[4478669.197612]  [&amp;lt;ffffffff81068fa6&amp;gt;] ? hrtimer_try_to_cancel+0x3a/0x43
[4478669.197622]  [&amp;lt;ffffffff8102de30&amp;gt;] ? pvclock_clocksource_read+0x3a/0x8b
[4478669.197631]  [&amp;lt;ffffffff81103705&amp;gt;] ? alloc_fd+0x67/0x10c
[4478669.197641]  [&amp;lt;ffffffff810eeacf&amp;gt;] ? do_sys_open+0x55/0xfc
[4478669.197649]  [&amp;lt;ffffffff81011b42&amp;gt;] ? system_call_fastpath+0x16/0x1b
&lt;/pre&gt;&lt;p&gt;
Rebooting...
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/674#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/862</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/862</guid>
        <title>#862: Puffin locked</title>
        <pubDate>Sat, 27 Jun 2015 15:31:27 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
&lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;PuffinServer&lt;/a&gt; is not responding, I got a Munin email alert, on the Xen console:
&lt;/p&gt;
&lt;pre class="wiki"&gt;[2008077.910371] BUG: soft lockup - CPU#1 stuck for 61s! [munin-node [::f:25444]
[2008077.910371] Modules linked in: joydev sg st sd_mod crc_t10dif sr_mod scsi_mod ide_gd_mod ide_cd_mod ide_core cdrom xt_recent xt_tcpudp xt_connlimit nf_nat_ftp ipt_REDIRECT xt_conntrack iptable_mangle nf_conntrack_ftp ipt_REJECT ipt_LOG xt_limit xt_multiport iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables snd_pcm snd_timer snd soundcore snd_page_alloc evdev pcspkr ext4 crc16 jbd2 mbcache dm_mod xen_netfront xen_blkfront
[2008077.910371] CPU 1:
[2008077.910371] Modules linked in: joydev sg st sd_mod crc_t10dif sr_mod scsi_mod ide_gd_mod ide_cd_mod ide_core cdrom xt_recent xt_tcpudp xt_connlimit nf_nat_ftp ipt_REDIRECT xt_conntrack iptable_mangle nf_conntrack_ftp ipt_REJECT ipt_LOG xt_limit xt_multiport iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables snd_pcm snd_timer snd soundcore snd_page_alloc evdev pcspkr ext4 crc16 jbd2 mbcache dm_mod xen_netfront xen_blkfront
[2008077.910371] Pid: 25444, comm: munin-node [::f Not tainted 2.6.32-5-xen-amd64 #1
[2008077.910371] RIP: e030:[&amp;lt;ffffffff8100922a&amp;gt;]  [&amp;lt;ffffffff8100922a&amp;gt;] hypercall_page+0x22a/0x1001
[2008077.910371] RSP: e02b:ffff8800988f7ba8  EFLAGS: 00000246
[2008077.910371] RAX: 0000000000040000 RBX: ffffea0006c2eb88 RCX: ffffffff8100922a
[2008077.910371] RDX: 00000000ffffff00 RSI: 0000000000000000 RDI: 0000000000000000
[2008077.910371] RBP: 0000000000000002 R08: 0000000000000002 R09: ffff8801ffc1dd00
[2008077.910371] R10: 0000000000000002 R11: 0000000000000246 R12: ffff88000000ad00
[2008077.910371] R13: ffff880000008000 R14: 0000000000000200 R15: 000000000000000e
[2008077.910371] FS:  00007fefd0bde700(0000) GS:ffff88000bb20000(0000) knlGS:0000000000000000
[2008077.910371] CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
[2008077.910371] CR2: 00007fefce124380 CR3: 0000000001001000 CR4: 0000000000000660
[2008077.910371] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[2008077.910371] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[2008077.910371] Call Trace:
[2008077.910371]  [&amp;lt;ffffffff810baa62&amp;gt;] ? free_hot_cold_page+0x1a2/0x1af
[2008077.910371]  [&amp;lt;ffffffff8100e635&amp;gt;] ? xen_force_evtchn_callback+0x9/0xa
[2008077.910371]  [&amp;lt;ffffffff8100ecf2&amp;gt;] ? check_events+0x12/0x20
[2008077.910371]  [&amp;lt;ffffffff8100ecdf&amp;gt;] ? xen_restore_fl_direct_end+0x0/0x1
[2008077.910371]  [&amp;lt;ffffffff8130f142&amp;gt;] ? _spin_unlock_irqrestore+0xd/0xe
[2008077.910371]  [&amp;lt;ffffffff810bd9ca&amp;gt;] ? release_pages+0x16a/0x18d
[2008077.910371]  [&amp;lt;ffffffff8100c1a7&amp;gt;] ? xen_mc_flush+0x159/0x185
[2008077.910371]  [&amp;lt;ffffffff810da555&amp;gt;] ? free_pages_and_swap_cache+0x57/0x73
[2008077.910371]  [&amp;lt;ffffffff810cd5bf&amp;gt;] ? unmap_vmas+0x6cb/0x959
[2008077.910371]  [&amp;lt;ffffffff8100922a&amp;gt;] ? hypercall_page+0x22a/0x1001
[2008077.910371]  [&amp;lt;ffffffff8100922a&amp;gt;] ? hypercall_page+0x22a/0x1001
[2008077.910371]  [&amp;lt;ffffffff810d1bca&amp;gt;] ? exit_mmap+0xc4/0x148
[2008077.910371]  [&amp;lt;ffffffff8104cd95&amp;gt;] ? mmput+0x3c/0xdf
[2008077.910371]  [&amp;lt;ffffffff81050a2e&amp;gt;] ? exit_mm+0x102/0x10d
[2008077.910371]  [&amp;lt;ffffffff81052453&amp;gt;] ? do_exit+0x1f8/0x6c9
[2008077.910371]  [&amp;lt;ffffffff8105299a&amp;gt;] ? do_group_exit+0x76/0x9d
[2008077.910371]  [&amp;lt;ffffffff810529d3&amp;gt;] ? sys_exit_group+0x12/0x16
[2008077.910371]  [&amp;lt;ffffffff81011b42&amp;gt;] ? system_call_fastpath+0x16/0x1b
[2008381.335662] Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:16:3e:19:68:02:00:12:1e:13:6c:db:08:00 SRC=122.172.30.208 DST=81.95.52.103 LEN=60 TOS=0x08 PREC=0x20 TTL=55 ID=30880 DF PROTO=TCP SPT=60400 DPT=23 WINDOW=5808 RES=0x00 SYN URGP=0
[2008384.465057] Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:16:3e:19:68:02:00:12:1e:13:6c:db:08:00 SRC=122.172.30.208 DST=81.95.52.103 LEN=60 TOS=0x08 PREC=0x20 TTL=55 ID=30881 DF PROTO=TCP SPT=60400 DPT=23 WINDOW=5808 RES=0x00 SYN URGP=0
[2008390.255448] Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:16:3e:19:68:02:00:12:1e:13:6c:db:08:00 SRC=122.172.30.208 DST=81.95.52.103 LEN=60 TOS=0x08 PREC=0x20 TTL=55 ID=30882 DF PROTO=TCP SPT=60400 DPT=23 WINDOW=5808 RES=0x00 SYN URGP=0
&lt;/pre&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/862#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/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>
 </channel>
</rss>