<?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?milestone=Maintenance&amp;group=status&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?milestone=Maintenance&amp;group=status&amp;order=summary</link>
    </image>
    <generator>Trac 0.12.5</generator>
    <item>
        <link>http://localhost:8080/trac/ticket/645</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/645</guid>
        <title>#645: APC Tuning on Parrot and Penguin</title>
        <pubDate>Tue, 10 Dec 2013 10:52:31 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
As part of the upgrade from Squeeze to Wheezy, see &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/535" title="maintenance: Upgrade Puffin, Penguin and Parrot from Debian Squeeze to Wheezy (closed: fixed)"&gt;ticket:535&lt;/a&gt;, Munin graphs for APC were added:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://penguin.transitionnetwork.org/munin/transitionnetwork.org/parrot.transitionnetwork.org/index.html#php-apc"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://penguin.transitionnetwork.org/munin/transitionnetwork.org/parrot.transitionnetwork.org/index.html#php-apc&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://penguin.transitionnetwork.org/munin/transitionnetwork.org/penguin.transitionnetwork.org/index.html#php-apc"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://penguin.transitionnetwork.org/munin/transitionnetwork.org/penguin.transitionnetwork.org/index.html#php-apc&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
There is also more APC info here:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://parrot.transitionnetwork.org/apc.php"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://parrot.transitionnetwork.org/apc.php&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="ext-link" href="https://penguin.transitionnetwork.org/info/apc.php"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://penguin.transitionnetwork.org/info/apc.php&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
The documentation for the variables which can be set in &lt;tt&gt;/etc/php5/mods-available/apc.ini&lt;/tt&gt; can be found here:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="http://php.net/manual/en/apc.configuration.php"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://php.net/manual/en/apc.configuration.php&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
This monitoring is generating quite a high volume of warnings about fragmentation and purges and this ticket has been created to try to sort this issue out.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/645#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/655</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/655</guid>
        <title>#655: Add social media icons with counters to blogs listings views</title>
        <pubDate>Thu, 12 Dec 2013 13:03:11 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Investigate with Rob how to add Social media icons with counters into the /blogs listings views and individual node views.
&lt;/p&gt;
&lt;p&gt;
I suggest starting with just Rob's blogs (/rob-hopkins), separate context for 'Transition Culture section' and then roll it out over other blogs and maybe news content type once the /rob-hopkins has been trialled
&lt;/p&gt;
&lt;p&gt;
Sam to talk with Rob
&lt;/p&gt;
&lt;p&gt;
Also cc-ing Ben as design - theme guy
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/655#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/676</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/676</guid>
        <title>#676: Alternative to Skype for TTech Meetings</title>
        <pubDate>Tue, 14 Jan 2014 13:33:51 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Jim has pointed out that:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Skype costs us 15-30 minutes of grinding pain every time we do this!
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
So what are the alternatives and what are our requirements?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/676#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/898</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/898</guid>
        <title>#898: Fwd: Access to Drupal</title>
        <pubDate>Tue, 26 Jan 2016 17:35:05 GMT</pubDate>
        
        <dc:creator>ade</dc:creator>

        <description>&lt;pre class="wiki"&gt;Hi Chris,
The web team at the development agency are requesting access to the
webserver so that they can look at the sites make up.
(Please see below)
Would you please set up an account so that they can get root read access?
I guess this would be done via FTP, but your thoughts greatly appreciated.
best regards
Ade
---------- Forwarded message ----------
From: Ainslie Beattie &amp;lt;ainsliebeattie@transitionnetwork.org&amp;gt;
Date: 26 January 2016 at 17:25
Subject: Fwd: Access to Drupal
To: Sam Rossiter &amp;lt;samrossiter@transitionnetwork.org&amp;gt;, Ade Stuart &amp;lt;
adestuart@transitionnetwork.org&amp;gt;, Yvonne Struthers &amp;lt;yvonne@thisisyoke.com&amp;gt;
Hey both, can you please action this urgently so that Yoke can have access.
Cheers
---------- Forwarded message ----------
From: "Yvonne Struthers" &amp;lt;yvonne@thisisyoke.com&amp;gt;
Date: 26 Jan 2016 10:58
Subject: Access to Drupal
To: &amp;lt;ainsliebeattie@transitionnetwork.org&amp;gt;
Cc:
Hi Ainslie,
Just a quick email as I'm out seeing a client today,but just to say,it
looks like you have only given us access to the database. What we need
please is admin access to the Drupal site and to the code base so that we
can get a sense of how it's all set up.
Thanks in advance!
Yvonne
Sent from my iPhone
--
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/898#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/814</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/814</guid>
        <title>#814: Higher that usual loads on PuffinServer since early September</title>
        <pubDate>Wed, 03 Dec 2014 17:12:35 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The following &lt;a class="ext-link" href="https://penguin.transitionnetwork.org/munin/transitionnetwork.org/puffin.transitionnetwork.org/load.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;load graph&lt;/a&gt; from &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;PuffinServer&lt;/a&gt; shows that the load increased substantially in early September 2014, does anyone know why?
&lt;/p&gt;
&lt;p&gt;
&lt;a style="padding:0; border:none" href="http://localhost:8080/trac/attachment/ticket/814/puffin-load-2014-11-03.png"&gt;&lt;img src="http://localhost:8080/trac/raw-attachment/ticket/814/puffin-load-2014-11-03.png" /&gt;&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
When I found &lt;a class="ext-link" href="http://www.vdmi.nl/blog/i-went-drupal-733-and-all-i-got-was-slow-site"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;I went to Drupal 7.33 and all I got was a slow site&lt;/a&gt; I thought that perhaps a Drupal 7 site on the server could be the cause but 7.33 came out on &lt;a class="ext-link" href="https://www.drupal.org/drupal-7.33-release-notes"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;7th November 2014&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
Anyone have any ideas?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/814#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/881</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/881</guid>
        <title>#881: Site on ParrotServer with a memory leak?</title>
        <pubDate>Fri, 23 Oct 2015 11:19:04 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
It appears a site, or application, on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;ParrotServer&lt;/a&gt; might have a memory leak.
&lt;/p&gt;
&lt;p&gt;
&lt;a style="padding:0; border:none" href="http://localhost:8080/trac/attachment/ticket/881/parrot-memory-pinpoint-1411038915-1445598915.png"&gt;&lt;img src="http://localhost:8080/trac/raw-attachment/ticket/881/parrot-memory-pinpoint-1411038915-1445598915.png" /&gt;&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/881#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/758</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/758</guid>
        <title>#758: * Advisory ID: DRUPAL-SA-CORE-2014-003</title>
        <pubDate>Wed, 16 Jul 2014 21:55:29 GMT</pubDate>
        
        <dc:creator>paul</dc:creator>

        <description>&lt;p&gt;
View online: &lt;a class="ext-link" href="https://www.drupal.org/SA-CORE-2014-003"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/SA-CORE-2014-003&lt;/a&gt;
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Advisory ID: DRUPAL-SA-CORE-2014-003
&lt;/li&gt;&lt;li&gt;Project: Drupal core &lt;a class="missing changeset" title="No default repository defined"&gt;[1]&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;Version: 6.x, 7.x
&lt;/li&gt;&lt;li&gt;Date: 2014-July-16
&lt;/li&gt;&lt;li&gt;Security risk: Critical &lt;a class="missing changeset" title="No default repository defined"&gt;[2]&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;Exploitable from: Remote
&lt;/li&gt;&lt;li&gt;Vulnerability: Multiple vulnerabilities
&lt;/li&gt;&lt;/ul&gt;&lt;hr /&gt;
&lt;hr /&gt;
&lt;p&gt;
Multiple vulnerabilities were fixed in the supported Drupal core versions 6
and 7.
&lt;/p&gt;
&lt;p&gt;
.... Denial of service with malicious HTTP Host header (Base system - Drupal
6 and 7 - Critical)
&lt;/p&gt;
&lt;p&gt;
Drupal core's multisite feature dynamically determines which configuration
file to use based on the HTTP Host header.
&lt;/p&gt;
&lt;p&gt;
The HTTP Host header validation does not sufficiently check
maliciously-crafted header values, thereby exposing a denial of service
vulnerability.
&lt;/p&gt;
&lt;p&gt;
.... Access bypass (File module - Drupal 7 - Critical)
&lt;/p&gt;
&lt;p&gt;
The File module included in Drupal 7 core allows attaching files to pieces of
content. The module doesn't sufficiently check permission to view the
attached file when attaching a file that was previously uploaded. This could
allow attackers to gain access to private files.
&lt;/p&gt;
&lt;p&gt;
This vulnerability is mitigated by the fact that the attacker must have
permission to create or edit content with a file field.
&lt;/p&gt;
&lt;p&gt;
Note: The Drupal 6 &lt;a class="missing wiki"&gt;FileField?&lt;/a&gt; &lt;a class="missing changeset" title="No default repository defined"&gt;[3]&lt;/a&gt; module is affected by a similar issue (see
SA-CONTRIB-2014-071 - &lt;a class="missing wiki"&gt;FileField?&lt;/a&gt; - Access bypass &lt;a class="missing changeset" title="No default repository defined"&gt;[4]&lt;/a&gt;) and requires an update
to the current security release of Drupal 6 core in order for the fix
released there to work correctly. However, Drupal 6 core itself is not
directly affected.
&lt;/p&gt;
&lt;p&gt;
.... Cross-site scripting (Form API option groups - Drupal 6 and 7 -
Moderately critical)
&lt;/p&gt;
&lt;p&gt;
A cross-site scripting vulnerability was found due to Drupal's form API
failing to sanitize option group labels in select elements. This
vulnerability affects Drupal 6 core directly, and likely affects Drupal 7
forms provided by contributed or custom modules.
&lt;/p&gt;
&lt;p&gt;
This vulnerability is mitigated by the fact that it requires the "administer
taxonomy" permission to exploit in Drupal 6 core, and there is no known
exploit within Drupal 7 core itself.
&lt;/p&gt;
&lt;p&gt;
.... Cross-site scripting (Ajax system - Drupal 7 - Moderately critical)
&lt;/p&gt;
&lt;p&gt;
A reflected cross-site scripting vulnerability was found in certain forms
containing a combination of an Ajax-enabled textfield (for example, an
autocomplete field) and a file field.
&lt;/p&gt;
&lt;p&gt;
This vulnerability is mitigated by the fact that an attacker can only trigger
the attack in a limited set of circumstances, usually requiring custom or
contributed modules.
&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;[5]&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;Drupal core 6.x versions prior to 6.32.
&lt;/li&gt;&lt;li&gt;Drupal core 7.x versions prior to 7.29.
&lt;/li&gt;&lt;/ul&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 Drupal 6.x, upgrade to Drupal core 6.32. &lt;a class="missing changeset" title="No default repository defined"&gt;[6]&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;If you use Drupal 7.x, upgrade to Drupal core 7.29. &lt;a class="missing changeset" title="No default repository defined"&gt;[7]&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Also see the Drupal core &lt;a class="missing changeset" title="No default repository defined"&gt;[8]&lt;/a&gt; project page.
&lt;/p&gt;
&lt;hr /&gt;
&lt;hr /&gt;
&lt;ul&gt;&lt;li&gt;The denial of service vulnerability using malicious HTTP Host headers was
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
reported by Régis Leroy &lt;a class="missing changeset" title="No default repository defined"&gt;[9]&lt;/a&gt;.
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;The access bypass vulnerability in the File module was reported by Ivan
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Ch
&lt;a class="missing changeset" title="No default repository defined"&gt;[10]&lt;/a&gt;.
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;The cross-site scripting vulnerability with Form API option groups was
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
reported by Károly Négyesi &lt;a class="missing changeset" title="No default repository defined"&gt;[11]&lt;/a&gt;.
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;The cross-site scripting vulnerability in the Ajax system was reported by
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
mani22test &lt;a class="missing changeset" title="No default repository defined"&gt;[12]&lt;/a&gt;.
&lt;/p&gt;
&lt;hr /&gt;
&lt;hr /&gt;
&lt;ul&gt;&lt;li&gt;The denial of service vulnerability using malicious HTTP Host headers was
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
fixed by Régis Leroy &lt;a class="missing changeset" title="No default repository defined"&gt;[13]&lt;/a&gt;, and by Klaus Purer &lt;a class="missing changeset" title="No default repository defined"&gt;[14]&lt;/a&gt; of the Drupal
Security
Team.
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;The access bypass vulnerability in the File module was fixed by Nate Haug
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[15]&lt;/a&gt; and Ivan Ch &lt;a class="missing changeset" title="No default repository defined"&gt;[16]&lt;/a&gt;, and by Drupal Security Team members David
Rothstein
&lt;a class="missing changeset" title="No default repository defined"&gt;[17]&lt;/a&gt;, Heine Deelstra &lt;a class="missing changeset" title="No default repository defined"&gt;[18]&lt;/a&gt; and David Snopek &lt;a class="missing changeset" title="No default repository defined"&gt;[19]&lt;/a&gt;.
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;The cross-site scripting vulnerability with Form API option groups was
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
fixed by Greg Knaddison &lt;a class="missing changeset" title="No default repository defined"&gt;[20]&lt;/a&gt; of the Drupal Security Team.
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;The cross-site scripting vulnerability in the Ajax system was fixed by
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Neil Drumm &lt;a class="missing changeset" title="No default repository defined"&gt;[21]&lt;/a&gt; of the Drupal Security Team.
&lt;/p&gt;
&lt;hr /&gt;
&lt;hr /&gt;
&lt;ul&gt;&lt;li&gt;The Drupal Security Team &lt;a class="missing changeset" title="No default repository defined"&gt;[22]&lt;/a&gt;
&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="http://drupal.org/contact"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/contact&lt;/a&gt; &lt;a class="missing changeset" title="No default repository defined"&gt;[23]&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;[24]&lt;/a&gt;, writing
secure code for Drupal &lt;a class="missing changeset" title="No default repository defined"&gt;[25]&lt;/a&gt;, and securing your site &lt;a class="missing changeset" title="No default repository defined"&gt;[26]&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
Follow the Drupal Security Team on Twitter at
&lt;a class="ext-link" href="https://twitter.com/drupalsecurity"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://twitter.com/drupalsecurity&lt;/a&gt; &lt;a class="missing changeset" title="No default repository defined"&gt;[27]&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="http://drupal.org/project/drupal"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/project/drupal&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[2]&lt;/a&gt; &lt;a class="ext-link" href="http://drupal.org/security-team/risk-levels"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://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="https://www.drupal.org/project/filefield"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/project/filefield&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/node/2304561"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/node/2304561&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[5]&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;[6]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/drupal-6.32-release-notes"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/drupal-6.32-release-notes&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/drupal-7.29-release-notes"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/drupal-7.29-release-notes&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[8]&lt;/a&gt; &lt;a class="ext-link" href="http://drupal.org/project/drupal"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/project/drupal&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/1367862"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/1367862&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/556138"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/556138&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/u/chx"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/u/chx&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/user/2844779"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/2844779&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/user/1367862"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/1367862&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/user/262198"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/262198&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/user/35821"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/35821&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[16]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/user/556138"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/556138&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[17]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/user/124982"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/124982&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[18]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/user/17943"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/17943&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[19]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/user/266527"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/266527&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[20]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/u/greggles"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/u/greggles&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[21]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/u/drumm"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/u/drumm&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[22]&lt;/a&gt; &lt;a class="ext-link" href="http://drupal.org/security-team"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/security-team&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[23]&lt;/a&gt; &lt;a class="ext-link" href="http://drupal.org/contact"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/contact&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[24]&lt;/a&gt; &lt;a class="ext-link" href="http://drupal.org/security-team"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/security-team&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[25]&lt;/a&gt; &lt;a class="ext-link" href="http://drupal.org/writing-secure-code"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/writing-secure-code&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[26]&lt;/a&gt; &lt;a class="ext-link" href="http://drupal.org/security/secure-configuration"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/security/secure-configuration&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[27]&lt;/a&gt; &lt;a class="ext-link" href="https://twitter.com/drupalsecurity"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://twitter.com/drupalsecurity&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/758#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/596</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/596</guid>
        <title>#596: Captions issue</title>
        <pubDate>Mon, 16 Sep 2013 16:58:04 GMT</pubDate>
        
        <dc:creator>benj</dc:creator>

        <description>&lt;p&gt;
basically captions are appearing on body inline images and featured images on STG but not PROD and I can't see where the difference is...
&lt;/p&gt;
&lt;p&gt;
The following code addition to the bottom of template.php should be (but isn't) adding the caption class to images such as the one at the top of this page:
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/blogs/ed-mitchell/2013-06/test-blog-test-caption-and-featured-image"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/blogs/ed-mitchell/2013-06/test-blog-test-caption-and-featured-image&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Any reason you can think of why not? Or do you know of another easy way of adding the class caption to featured image fields? (I guess the module &lt;a class="ext-link" href="https://drupal.org/project/semantic_cck"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://drupal.org/project/semantic_cck&lt;/a&gt; - but maybe overkill...)
&lt;/p&gt;
&lt;p&gt;
/&lt;strong&gt;
&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Adds caption css class to featured images
*/
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
function transition2_imagecache_formatter_featured_image_default($element) {
&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;
&lt;em&gt; Inside a view $element may contain NULL data. In that case, just return.
if (empty($element&lt;a class="wiki" href="http://localhost:8080/trac/wiki/WikiStart#item"&gt;#item&lt;/a&gt;&lt;a class="missing wiki"&gt;fid?&lt;/a&gt;)) {
&lt;/em&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;
return &lt;em&gt;;
&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
}
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;
&lt;em&gt; Extract the preset name from the formatter name.
$presetname = substr($element&lt;a class="wiki" href="http://localhost:8080/trac/wiki/WikiStart#formatter"&gt;#formatter&lt;/a&gt;, 0, strrpos($element&lt;a class="wiki" href="http://localhost:8080/trac/wiki/WikiStart#formatter"&gt;#formatter&lt;/a&gt;, '_'));
$style = 'linked';
$style = 'default';
&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;
$item = $element&lt;a class="wiki" href="http://localhost:8080/trac/wiki/WikiStart#item"&gt;#item&lt;/a&gt;;
$item&lt;a class="missing wiki"&gt;data?&lt;/a&gt;&lt;a class="missing wiki"&gt;alt?&lt;/a&gt; = isset($item&lt;a class="missing wiki"&gt;data?&lt;/a&gt;&lt;a class="missing wiki"&gt;alt?&lt;/a&gt;) ? $item&lt;a class="missing wiki"&gt;data?&lt;/a&gt;&lt;a class="missing wiki"&gt;alt?&lt;/a&gt; : &lt;em&gt;;
$item&lt;a class="missing wiki"&gt;data?&lt;/a&gt;&lt;a class="missing wiki"&gt;title?&lt;/a&gt; = isset($item&lt;a class="missing wiki"&gt;data?&lt;/a&gt;&lt;a class="missing wiki"&gt;title?&lt;/a&gt;) ? $item&lt;a class="missing wiki"&gt;data?&lt;/a&gt;&lt;a class="missing wiki"&gt;title?&lt;/a&gt; : NULL;
&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;
$class = "imagecache imagecache-$presetname imagecache-$style imagecache-{$element&lt;a class="wiki" href="http://localhost:8080/trac/wiki/WikiStart#formatter"&gt;#formatter&lt;/a&gt;} caption";
return theme('imagecache', $presetname, $item&lt;a class="missing wiki"&gt;filepath?&lt;/a&gt;, $item&lt;a class="missing wiki"&gt;data?&lt;/a&gt;&lt;a class="missing wiki"&gt;alt?&lt;/a&gt;, $item&lt;a class="missing wiki"&gt;data?&lt;/a&gt;&lt;a class="missing wiki"&gt;title?&lt;/a&gt;, array('class' =&amp;gt; $class));
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
}
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/596#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/727</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/727</guid>
        <title>#727: Change background on block from orange to white</title>
        <pubDate>Fri, 16 May 2014 10:02:17 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Ben
&lt;/p&gt;
&lt;p&gt;
Rob wants a list of the themes presented in a block.
&lt;/p&gt;
&lt;p&gt;
I did the block: &lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/build/block/configure/block/97"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/build/block/configure/block/97&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
But it appears with an orange background. The block is visible towards the bottom of the page (for logged in admins) here: &lt;a class="ext-link" href="https://www.transitionnetwork.org/blogs/rob-hopkins"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/blogs/rob-hopkins&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
If I put the block on other pages it appears with a white background.
&lt;/p&gt;
&lt;p&gt;
I tried to hack it with some inline CSS but failed.
&lt;/p&gt;
&lt;p&gt;
Could you take a look?
&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/727#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/636</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/636</guid>
        <title>#636: Changes to Space.transitionnetwork.org homepage to facilitate user registration</title>
        <pubDate>Wed, 27 Nov 2013 17:30:19 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Space currently does not give users who aren't already registered a way in. Anon users can see some of the spaces but when they try to apply for membership, they hit a login page, which they can't complete as they are not registered.
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;RTFM for OA as to OA best practice - this is billable time. Then leave notes about it in wiki for later developers.
&lt;/li&gt;&lt;/ol&gt;&lt;ol start="2"&gt;&lt;li&gt;The homepage needs editing to sort this out. Here are some first changes:
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
2.1. Remove the 'Need the pros' pane (RHS)
2.2 Remove the 'Just getting started' pane (LHS)
2.3 Add a 'Request membership' pane which is basically a user registration form. Make registration 'approval only' for now, approval to be by a site admin (webproject@…)
&lt;/p&gt;
&lt;p&gt;
The /spaces listings view shows the spaces that are publicly viewable, and there is a 'request group membership' button for each of them.
&lt;/p&gt;
&lt;ol start="3"&gt;&lt;li&gt;Can you make this into a registration form as well?
&lt;/li&gt;&lt;/ol&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/636#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/541</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/541</guid>
        <title>#541: Documentation of the WordPress sites</title>
        <pubDate>Wed, 01 May 2013 20:25:57 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
These pages have been created for the documentation of the &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;wiki:WordPress&lt;/a&gt; sites running on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PenguinServer"&gt;wiki:PenguinServer&lt;/a&gt;:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="wiki" href="http://localhost:8080/trac/wiki/InTransitionWordPress"&gt;wiki:InTransitionWordPress&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="wiki" href="http://localhost:8080/trac/wiki/ReconomyWordPress"&gt;wiki:ReconomyWordPress&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="wiki" href="http://localhost:8080/trac/wiki/EarthInheritorsWordPress"&gt;wiki:EarthInheritorsWordPress&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
So far they only have a listing on the plugins for each site.
&lt;/p&gt;
&lt;p&gt;
Ideally they would document all the plugins, the theme and the steps that need to be taken to upgrade each site and also any other things that need documenting.
&lt;/p&gt;
&lt;p&gt;
Laura is this something you might be able to help with? I'm happy doing some work on it but you know your way around these sites far better than anyone else.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/541#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/590</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/590</guid>
        <title>#590: Drupal performance improvements</title>
        <pubDate>Fri, 06 Sep 2013 10:27:27 GMT</pubDate>
        
        <dc:creator>jim</dc:creator>

        <description>&lt;p&gt;
This ticket is to track the work and changes done within the Drupal sphere in relation to performance enhancements done since &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/585" title="maintenance: TTech Meeting 5th September 2013 (closed: fixed)"&gt;#585&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
More information is needed and will come when &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/586" title="maintenance: New Relic Monitoring for BOA (closed: fixed)"&gt;ticket:586&lt;/a&gt; New Relic Monitoring for BOA is completed.
&lt;/p&gt;
&lt;p&gt;
I also note that many of these cleanup operations will also help make the move to D7 smoother and better.
&lt;/p&gt;
&lt;h1 id="Summaryofactionsandstatus"&gt;Summary of actions and status&lt;/h1&gt;
&lt;h2 id="TODO"&gt;TODO&lt;/h2&gt;
&lt;p&gt;
&lt;strong&gt;O) Stop making so many URL aliases for non-relevant pages, clean up url_alias table&lt;/strong&gt; -- 1/4-1/2 hour, medium reward, only risk is that some already broken links might break... Per chat with Ed, only these will be removed (plus releated tweaks to Pathauto settings):
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;3,579 entries where src = node/%/feed
&lt;/li&gt;&lt;li&gt;1,856 entries where src = user/%/contact
&lt;/li&gt;&lt;li&gt;= 5,435 or ~11% of entries in url_alias
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
&lt;strong&gt;L) Review slow query log, explain queries, tweak as necessary/flag poorly behaving modules.&lt;/strong&gt; 2-4 hours, high reward, low risk... Keep looking at the slow query log and adjust Drupal or find patches as necessary. ALSO related &lt;a class="ext-link" href="http://2bits.com/articles/reduce-your-servers-resource-usage-moving-mysql-temporary-directory-ram-disk.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Reduce your server's resource usage by moving MySQL temporary directory to tmpfs&lt;/a&gt;... Have opened ticket for this: &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/591" title="maintenance: Move MySQL temporary directory to tmpfs (closed: fixed)"&gt;#591&lt;/a&gt; for Chris.
&lt;/p&gt;
&lt;h3 id="Done"&gt;Done&lt;/h3&gt;
&lt;p&gt;
&lt;strong&gt;A) Remove spam taxonomy entries&lt;/strong&gt; &lt;del&gt;1/2 hour, Low risk, low reward -- See item 8 below. A simple delete from taxo term table where length &amp;gt; 50 is worth doing IMHO, and nothing I saw that would be clobbered is not spam.&lt;/del&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;B) Try a Taxonomy Cleanup&lt;/strong&gt;:  &lt;del&gt;3 hours, Medium risk, medium reward -- style module to try to merge terms with the same names and clean up the link tables back to nodes. Further, we can remove any taxonomies or relations to certain CTs that don't really add value.&lt;/del&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;D) Review Views caching&lt;/strong&gt; &lt;del&gt;1 hour, low risk, high reward -- Utilise Views Content Cache this was done a while back but I think -- done (task 12) in comment 21.&lt;/del&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;F) Force blocks caches to cached appropriately (and be rendered/included only as needed)&lt;/strong&gt; &lt;del&gt;1-2 hours, medium reward, low risk -- BOA packages the &lt;a class="ext-link" href="https://drupal.org/project/blockcache_alter"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Block Cache Alter&lt;/a&gt;, which makes sure Drupal only renders blocks when needed. Potential small but nice boost quickly in whole site. -- per comment 22, block caching is disabled by other modules so this will have to go on hold for now.&lt;/del&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;H) Remove &lt;a class="missing wiki"&gt;CustomError?&lt;/a&gt; module all together&lt;/strong&gt; &lt;del&gt;1/2 hour, low risk, low reward -- We should take out the PHP code from the 403 section of &lt;a class="missing wiki"&gt;CustomError?&lt;/a&gt; and put it into a simple page entry. See comment 6 below as this has happened for 404s (which need no PHP). We can then remove the &lt;a class="missing wiki"&gt;CustomError?&lt;/a&gt; module all together, saving lots of sessions. I would go ahead and do this but since the 403 page has various displays depending on user type, I wanted to raise it here as it *may* have side effects. Or not...&lt;/del&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;I) Re-enable block caching.&lt;/strong&gt; &lt;del&gt;2-6 hours, high risk, high reward -- Per comment 24, a module (probably Content Access) is stopping Drupal caching blocks, which for some of them means a fair amount of pointless overhead. We need to somehow get around this and get blocks cached if possible. R&amp;amp;D mainly, perhaps with some hacking/patching - but I'd stop short of doing this if so.&lt;/del&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;K) Add &amp;amp; enable Views Lite Pager on big views.&lt;/strong&gt; &lt;del&gt;1 hour, low risk, low reward -- Using this module stops a heavy count query on views with pagers -- recommended for large sites.&lt;/del&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;M) Take control of Cron, and maximise time pages are cached for.&lt;/strong&gt; &lt;del&gt;.25h, high reward, low risk -- Cron is wiping the page cache, so we need to install &lt;a class="ext-link" href="https://drupal.org/project/elysia_cron"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://drupal.org/project/elysia_cron&lt;/a&gt; so we can clear the page less often, and run other things when we want and the site is quieter. Now need per minute resolution set to get the best, see comment 33 and 34 for more...&lt;/del&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;N) Replace Admin Menu 1.x with 3.x&lt;/strong&gt; -- will happen when &lt;a class="assigned ticket" href="http://localhost:8080/trac/ticket/590" title="defect: Drupal performance improvements (assigned)"&gt;#590&lt;/a&gt; occurs, marking complete here -- &lt;del&gt;5 mins, high reward, low risk -- done when &lt;a class="assigned ticket" href="http://localhost:8080/trac/ticket/582" title="maintenance: TN.org platform and sites (assigned)"&gt;#582&lt;/a&gt; happens, could be the cause of some load spikes as it occasionally goes made and does 2000-5000 queries~~
&lt;/del&gt;&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/590#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/701</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/701</guid>
        <title>#701: Emails &amp; Telephone calls</title>
        <pubDate>Tue, 18 Mar 2014 09:38:24 GMT</pubDate>
        
        <dc:creator>paul</dc:creator>

        <description></description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/701#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/711</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/711</guid>
        <title>#711: Emails &amp; Telephone calls</title>
        <pubDate>Tue, 01 Apr 2014 13:47:56 GMT</pubDate>
        
        <dc:creator>paul</dc:creator>

        <description></description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/711#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/587</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/587</guid>
        <title>#587: Puffin MySQL Tuning</title>
        <pubDate>Thu, 05 Sep 2013 12:54:47 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
This ticket is to track the tuning we do to MySQL on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;PuffinServer&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
See also previous comments on this issue:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:12" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:12&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:15" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:15&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:16" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:16&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:17" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:17&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:20" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:20&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:29" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:29&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#SettingsChanged" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#SettingsChanged&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:39" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:39&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:56" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:56&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:57" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:57&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:60" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:60&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:65" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:65&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:66" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:66&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:67" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:67&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:68" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:68&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:82" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:82&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555#comment:85" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555#comment:85&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/587#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/638</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/638</guid>
        <title>#638: Question about notifications option for content creators</title>
        <pubDate>Thu, 28 Nov 2013 12:32:57 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Content creators (news, Rob's blog, social reporters) struggle with the notifications. the problem is that they forget to click the option to 'do not send notifications for this update' and then notifications are sent out. It is easy for us to think this is easy for them, but when you are bashing stuff out in a hurry, it's easy to forget this fiddly bit.
&lt;/p&gt;
&lt;p&gt;
CAN WE set drupal to NOT send notifications out as standard for some of the content types?
&lt;/p&gt;
&lt;p&gt;
And change it so that the content creators (news, Rob's blog, social reporters) choose to SEND notifications out instead (of NOT sending them)
?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/638#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/737</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/737</guid>
        <title>#737: SPF / Emails rejected from the website contact form</title>
        <pubDate>Thu, 05 Jun 2014 15:46:13 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
We had a user report that they could not send a message via our contact form:
&lt;/p&gt;
&lt;p&gt;
"Yesterday I sent a message to you via the contact form on the website. But obviously something went wrong: for I got a failure notice saying my message could not be delivered. Therefore I'm sending it directly via email (see below) hoping that you're receiving my message this way."
&lt;/p&gt;
&lt;p&gt;
&amp;lt;info@…&amp;gt;: host mx1.spamfiltering.com[72.249.150.158] said:
&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;
550 81.95.XX.XX is not allowed to send mail from gmx.de. Please see
&lt;a class="ext-link" href="http://www.openspf.net/Why?scope=mfrom;identity=userXX@gmx.de;ip=81.95.XX.XX"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.openspf.net/Why?scope=mfrom;identity=userXX@gmx.de;ip=81.95.XX.XX&lt;/a&gt;
(in reply to end of DATA command)
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
(User details edited as this is publicly archived)
&lt;/p&gt;
&lt;p&gt;
I'm not sure I quite understand what's going on here. Chris indicated in email that this would affect other users whose email provider has set this kind of SPF record.
&lt;/p&gt;
&lt;p&gt;
Can we make an educated guess as to what proportion of email providers set this kind of SPF?
&lt;/p&gt;
&lt;p&gt;
How many messages do we never get to see? Is it a problem? Or a small enough number of users that we just don't worry about it?
&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/737#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/662</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/662</guid>
        <title>#662: Subscriptions' links in text emails breaking</title>
        <pubDate>Tue, 17 Dec 2013 15:37:13 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
for January - to get Sam and Jim talking - in January
&lt;/p&gt;
&lt;p&gt;
The subs sent out to subscribers: are fine in html but the text version is broken and unsatisfactory. I know we've been through this and it's a known bug etc. etc. but I'm wondering if we can switch all subs to html, or if there are any patches to this problem?
&lt;/p&gt;
&lt;p&gt;
Adding as Jim's ticket with Sam cc-ed
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/662#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/582</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/582</guid>
        <title>#582: TN.org platform and sites</title>
        <pubDate>Mon, 02 Sep 2013 09:30:02 GMT</pubDate>
        
        <dc:creator>jim</dc:creator>

        <description>&lt;p&gt;
The TN.org platform and Drupal site updates are to be tracked in this ticket.
&lt;/p&gt;
&lt;p&gt;
Current PROD platform build = &lt;strong&gt;P009&lt;/strong&gt;
Current STG platform build = &lt;strong&gt;S010&lt;/strong&gt;
&lt;/p&gt;
&lt;p&gt;
Updates pending:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;SECURITY UPDATE - NO RISK: Pressflow core 6.30 is due, but the security holes fixed do not affect us, low priority. Platforms: present in S010, but not in P009.
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/582#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/772</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/772</guid>
        <title>#772: new TIs not appearing on staging until caches flushed</title>
        <pubDate>Tue, 05 Aug 2014 09:26:32 GMT</pubDate>
        
        <dc:creator>annesley</dc:creator>

        <description>&lt;p&gt;
i added a new Mulling transition initiative on staging in Afghanistan and it did not appear on the map... i flushed caches and then it started appearing on the main initiatives map. is this intended? is it a known?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/772#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/774</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/774</guid>
        <title>#774: * Advisory ID: DRUPAL-SA-CORE-2014-004</title>
        <pubDate>Wed, 06 Aug 2014 19:52:54 GMT</pubDate>
        
        <dc:creator>paul</dc:creator>

        <description>&lt;p&gt;
View online: &lt;a class="ext-link" href="https://www.drupal.org/SA-CORE-2014-004"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/SA-CORE-2014-004&lt;/a&gt;
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Advisory ID: DRUPAL-SA-CORE-2014-004
&lt;/li&gt;&lt;li&gt;Project: Drupal core &lt;a class="missing changeset" title="No default repository defined"&gt;[1]&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;Version: 6.x, 7.x
&lt;/li&gt;&lt;li&gt;Date: 2014-August-06
&lt;/li&gt;&lt;li&gt;Security risk: 13/25 ( Moderately Critical)
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
AC:None/A:None/CI:None/II:None/E:Proof/TD:100 &lt;a class="missing changeset" title="No default repository defined"&gt;[2]&lt;/a&gt;
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Exploitable from: Remote
&lt;/li&gt;&lt;li&gt;Vulnerability: Denial of service
&lt;/li&gt;&lt;/ul&gt;&lt;hr /&gt;
&lt;hr /&gt;
&lt;p&gt;
Drupal 6 and Drupal 7 include an XML-RPC endpoint which is publicly available
(xmlrpc.php). The PHP XML parser used by this XML-RPC endpoint is vulnerable
to an XML entity expansion attack and other related XML payload attacks which
can cause CPU and memory exhaustion and the site's database to reach the
maximum number of open connections. Any of these may lead to the site
becoming unavailable or unresponsive (denial of service).
&lt;/p&gt;
&lt;p&gt;
All Drupal sites are vulnerable to this attack whether XML-RPC is used or
not.
&lt;/p&gt;
&lt;p&gt;
In addition, a similar vulnerability exists in the core OpenID module (for
sites that have this module enabled).
&lt;/p&gt;
&lt;p&gt;
This is a joint release as the XML-RPC vulnerability also affects &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt;
(see the announcement &lt;a class="missing changeset" title="No default repository defined"&gt;[3]&lt;/a&gt;).
&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;[4]&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;Drupal core 7.x versions prior to 7.31.
&lt;/li&gt;&lt;li&gt;Drupal core 6.x versions prior to 6.33.
&lt;/li&gt;&lt;/ul&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 Drupal 7.x, upgrade to Drupal core 7.31 &lt;a class="missing changeset" title="No default repository defined"&gt;[5]&lt;/a&gt;.
&lt;/li&gt;&lt;li&gt;If you use Drupal 6.x, upgrade to Drupal core 6.33 &lt;a class="missing changeset" title="No default repository defined"&gt;[6]&lt;/a&gt;.
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
If you are unable to install the latest version of Drupal immediately, you
can alternatively remove the xmlrpc.php file from the root of Drupal core (or
add a rule to .htaccess to prevent access to xmlrpc.php) and disable the
OpenID module. These steps are sufficient to mitigate the vulnerability in
Drupal core if your site does not require the use of XML-RPC or OpenID
functionality. However, this mitigation will not be effective if you are
using a contributed module that exposes Drupal's XML-RPC API at a different
URL (for example, the Services module); updating Drupal core is therefore
strongly recommended.
&lt;/p&gt;
&lt;p&gt;
Also see the Drupal core &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;Willis Vandevanter &lt;a class="missing changeset" title="No default repository defined"&gt;[8]&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;Nir Goldshlager &lt;a class="missing changeset" title="No default repository defined"&gt;[9]&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;hr /&gt;
&lt;hr /&gt;
&lt;ul&gt;&lt;li&gt;Andrew Nacin &lt;a class="missing changeset" title="No default repository defined"&gt;[10]&lt;/a&gt; of the &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; Security Team
&lt;/li&gt;&lt;li&gt;Michael Adams &lt;a class="missing changeset" title="No default repository defined"&gt;[11]&lt;/a&gt; of the &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; Security Team
&lt;/li&gt;&lt;li&gt;Frédéric Marand &lt;a class="missing changeset" title="No default repository defined"&gt;[12]&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;David Rothstein &lt;a class="missing changeset" title="No default repository defined"&gt;[13]&lt;/a&gt; of the Drupal Security Team
&lt;/li&gt;&lt;li&gt;Damien Tournoud &lt;a class="missing changeset" title="No default repository defined"&gt;[14]&lt;/a&gt; of the Drupal Security Team
&lt;/li&gt;&lt;li&gt;Greg Knaddison &lt;a class="missing changeset" title="No default repository defined"&gt;[15]&lt;/a&gt; of the Drupal Security Team
&lt;/li&gt;&lt;li&gt;Stéphane Corlosquet &lt;a class="missing changeset" title="No default repository defined"&gt;[16]&lt;/a&gt; of the Drupal Security Team
&lt;/li&gt;&lt;li&gt;Dave Reid &lt;a class="missing changeset" title="No default repository defined"&gt;[17]&lt;/a&gt; of the Drupal Security Team
&lt;/li&gt;&lt;/ul&gt;&lt;hr /&gt;
&lt;hr /&gt;
&lt;ul&gt;&lt;li&gt;The Drupal Security Team &lt;a class="missing changeset" title="No default repository defined"&gt;[18]&lt;/a&gt; and the &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; &lt;a class="missing changeset" title="No default repository defined"&gt;[19]&lt;/a&gt; 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="http://drupal.org/contact"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/contact&lt;/a&gt; &lt;a class="missing changeset" title="No default repository defined"&gt;[20]&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;[21]&lt;/a&gt;, writing
secure code for Drupal &lt;a class="missing changeset" title="No default repository defined"&gt;[22]&lt;/a&gt;, and securing your site &lt;a class="missing changeset" title="No default repository defined"&gt;[23]&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="http://drupal.org/project/drupal"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/project/drupal&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[2]&lt;/a&gt; &lt;a class="ext-link" href="http://drupal.org/security-team/risk-levels"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://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="https://wordpress.org/news/2014/08/wordpress-3-9-2/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://wordpress.org/news/2014/08/wordpress-3-9-2/&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[4]&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;[5]&lt;/a&gt; &lt;a class="ext-link" href="http://drupal.org/drupal-7.31-release-notes"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/drupal-7.31-release-notes&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[6]&lt;/a&gt; &lt;a class="ext-link" href="http://drupal.org/drupal-6.33-release-notes"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/drupal-6.33-release-notes&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[7]&lt;/a&gt; &lt;a class="ext-link" href="http://drupal.org/project/drupal"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/project/drupal&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/1867894"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/1867894&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/2891345"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/2891345&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[10]&lt;/a&gt; &lt;a class="ext-link" href="http://profiles.wordpress.org/nacin"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://profiles.wordpress.org/nacin&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[11]&lt;/a&gt; &lt;a class="ext-link" href="http://profiles.wordpress.org/mdawaffe"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://profiles.wordpress.org/mdawaffe&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/user/27985"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/27985&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/user/124982"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/124982&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/user/22211"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/22211&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/u/greggles"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/u/greggles&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[16]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/user/52142"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/52142&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[17]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/user/53892"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/53892&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[18]&lt;/a&gt; &lt;a class="ext-link" href="http://drupal.org/security-team"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/security-team&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[19]&lt;/a&gt; &lt;a class="ext-link" href="http://wordpress.org"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://wordpress.org&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[20]&lt;/a&gt; &lt;a class="ext-link" href="http://drupal.org/contact"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/contact&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[21]&lt;/a&gt; &lt;a class="ext-link" href="http://drupal.org/security-team"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/security-team&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[22]&lt;/a&gt; &lt;a class="ext-link" href="http://drupal.org/writing-secure-code"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/writing-secure-code&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[23]&lt;/a&gt; &lt;a class="ext-link" href="http://drupal.org/security/secure-configuration"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://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/774#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/820</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/820</guid>
        <title>#820: *.transitionnetwork.org 2015 security certificate</title>
        <pubDate>Fri, 26 Dec 2014 09:47:49 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The current wild-card &lt;tt&gt;*.transitionnetwork.org&lt;/tt&gt; cert will run out on 24th Jan, this is a ticket to track the time spent renewing it.
&lt;/p&gt;
&lt;p&gt;
See also &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/795" title="maintenance: SHA1 Deprecation: Regenerate all certs using SHA256 (closed: fixed)"&gt;ticket:795&lt;/a&gt;, SHA1 Deprecation: Regenerate all certs using SHA256.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/820#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/569</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/569</guid>
        <title>#569: 403s served to editors, admin very slow</title>
        <pubDate>Tue, 09 Jul 2013 07:52:32 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

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

        <description>&lt;p&gt;
The BOA &lt;tt&gt;/var/xdrago/second.sh&lt;/tt&gt; script is run every minute via the root crontab and if it detects a certain load level it changes the nginx config to a "high load" config which results in bots being served 503 errors when they spider the site. When the load goes higher and hits another threshold the &lt;tt&gt;second.sh&lt;/tt&gt; script stops the site, see &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/555" title="maintenance: Load spikes causing the TN site to be stopped for 15 min at a time (closed: fixed)"&gt;ticket:555&lt;/a&gt;.
&lt;/p&gt;
&lt;h2 id="OriginalDescription"&gt;Original Description&lt;/h2&gt;
&lt;p&gt;
The site is generating a lot of 503 errors, 83 since 6:30am today and there were around 750 yesterday.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/563#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/843</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/843</guid>
        <title>#843: 8.8.8.8 (US/United States/google-public-dns-a.google.com) blocked for port scanning</title>
        <pubDate>Tue, 07 Apr 2015 23:05:33 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Never seen this before:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Date: Tue,  7 Apr 2015 23:46:09 +0100 (BST)
From: root@puffin.webarch.net
To: chris@webarchitects.co.uk
Subject: lfd on puffin.webarch.net: 8.8.8.8 (US/United States/google-public-dns-a.google.com) blocked for port scanning
Time:    Tue Apr  7 23:46:09 2015 +0000
IP:      8.8.8.8 (US/United States/google-public-dns-a.google.com)
Hits:    20
Blocked: Temporary Block
Sample of block hits:
Apr  7 23:45:36 puffin kernel: [19823338.636822] Firewall: *UDP_IN Blocked* IN=eth0 OUT= MAC=00:16:3e:19:68:02:00:12:1e:13:6c:db:08:00 SRC=8.8.8.8 DST=81.95.52.103 LEN=162 TOS=0x00 PREC=0x00 TTL=45 ID=65064 PROTO=UDP SPT=53 DPT=48825 LEN=142
&lt;/pre&gt;&lt;p&gt;
I thought set the Google DNS servers for the machine via   /etc/resolv.conf but that contains:
&lt;/p&gt;
&lt;pre class="wiki"&gt;# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
&lt;/pre&gt;&lt;p&gt;
There is /etc/resolvconf/resolv.conf.d/original containing:
&lt;/p&gt;
&lt;pre class="wiki"&gt;nameserver 8.8.8.8
nameserver 8.8.4.4
&lt;/pre&gt;&lt;p&gt;
But I don't know what DNS resolver BOA has installed and the server is using.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/843#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/744</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/744</guid>
        <title>#744: Add CSS Injector module to the D6 mix</title>
        <pubDate>Thu, 19 Jun 2014 10:50:03 GMT</pubDate>
        
        <dc:creator>annesley</dc:creator>

        <description>&lt;p&gt;
CSS Injector module allows admin dynamic adding of CSS in to a live production server without code updates. this is to respond quickly to client needs whilst implementing the requests in the correct place in the themes on the next promotion from dev.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/744#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/534</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/534</guid>
        <title>#534: Add accounts for Ben</title>
        <pubDate>Fri, 26 Apr 2013 17:16:23 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Ben is a new member of the TTech team and accounts need setting up for him, this is a ticket to track the time taken to do this.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/534#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/632</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/632</guid>
        <title>#632: Add accounts for Sam</title>
        <pubDate>Mon, 25 Nov 2013 14:41:25 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Following &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/534" title="maintenance: Add accounts for Ben (closed: fixed)"&gt;ticket:534&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/632#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/649</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/649</guid>
        <title>#649: Add commenting to /films/ content type in January</title>
        <pubDate>Thu, 12 Dec 2013 10:53:16 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
seen here:
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/content/node-type/films"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/content/node-type/films&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/films"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/films&lt;/a&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/films/occupy-love"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/films/occupy-love&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/649#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/643</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/643</guid>
        <title>#643: Add paginator for /films view</title>
        <pubDate>Mon, 09 Dec 2013 11:40:08 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Please add pages links for this view:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/build/views/edit/Films?destination=films#views-tab-page_1"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/build/views/edit/Films?destination=films#views-tab-page_1&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
10 per page should do it
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/643#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/684</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/684</guid>
        <title>#684: Adding Paul and Nick to Transition Network on github.org</title>
        <pubDate>Thu, 23 Jan 2014 10:42:23 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
It looks like Ed and Jim are the only one with permissions to add members to &lt;a class="ext-link" href="https://github.com/orgs/transitionnetwork/members"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Transition Network on GitHub&lt;/a&gt; as they are listed as owners and the rest of us are members.
&lt;/p&gt;
&lt;p&gt;
Paul and Nick can you post you account names to this ticket so you can be added?
&lt;/p&gt;
&lt;p&gt;
Jim could you make me and/or Ben owners as well so we can add people?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/684#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/611</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/611</guid>
        <title>#611: Adding Trac Account for Alan</title>
        <pubDate>Thu, 17 Oct 2013 12:55:21 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

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

        <description>&lt;p&gt;
I need to add a CNAME value to verify transitionnetwork.org for google apps.
&lt;/p&gt;
&lt;p&gt;
Can I do this on my own using the zone files in gandi or is it better that you do it Chris?
&lt;/p&gt;
&lt;p&gt;
The value will be automatically generated as part of the verification process for setting the apps up, so I'll need to add it promptly
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://support.google.com/a/answer/60216"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://support.google.com/a/answer/60216&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/803#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/888</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/888</guid>
        <title>#888: Adverts on Transition Network Front Page loaded via flickrit.com embedded content</title>
        <pubDate>Sun, 06 Dec 2015 12:25:49 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
It it intentional or accidental that adverts from &lt;a class="ext-link" href="https://secureads.bitbillions.com/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://secureads.bitbillions.com/&lt;/a&gt; are being loaded on the front page of &lt;a class="ext-link" href="https://www.transitionnetwork.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/&lt;/a&gt; via the embedded content from flickrit.com?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/888#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/610</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/610</guid>
        <title>#610: Aegir database intensive (migrate, clone, restore) tasks hang for larger sites</title>
        <pubDate>Tue, 15 Oct 2013 10:18:59 GMT</pubDate>
        
        <dc:creator>jim</dc:creator>

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

        <description>&lt;p&gt;
Admins, editors, social reporters cannot create content on TN.org. Choosing to create content leads to homepage. Can't do anything on the admin menu.
&lt;/p&gt;
&lt;p&gt;
Emergency.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/548#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/779</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/779</guid>
        <title>#779: Annesley locked out of puffin?</title>
        <pubDate>Wed, 27 Aug 2014 14:28:12 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Looks like Annesley's IP has been blocked on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;wiki:PuffinServer&lt;/a&gt;.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/779#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/630</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/630</guid>
        <title>#630: Archiving Transition Town Totnes site</title>
        <pubDate>Mon, 25 Nov 2013 11:54:35 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Please estimate to archive TTT site as per conversation with Ed:
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;convert to html
&lt;/li&gt;&lt;li&gt;host on Penguin (incl. any likely issues for Penguin doing this)
&lt;/li&gt;&lt;li&gt;any ongoing maintenance
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
Then Ed will discuss with Frances at TTT as per agreement with Chris
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/630#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/702</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/702</guid>
        <title>#702: Attachments not being deleted from Trustees page</title>
        <pubDate>Fri, 21 Mar 2014 17:11:14 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
I can't remove the attachments from the Trustees page:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/about/people/trustees"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/about/people/trustees&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
please investigate and sort if you can. We need to remove all the attachments apart from those in 2013.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/702#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/854</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/854</guid>
        <title>#854: BOA 2.4.3</title>
        <pubDate>Tue, 26 May 2015 10:30:41 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
BOA 2.4.3 came out 7 days ago (BOA, for an unknown reason, no longer appears to sent out update available emails), from &lt;a class="ext-link" href="https://github.com/omega8cc/boa/blob/master/CHANGELOG.txt"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;the changelog&lt;/a&gt;:
&lt;/p&gt;
&lt;pre class="wiki"&gt;### Stable BOA-2.4.3 Release - Full Edition
### Date: Tue May 19 13:40:40 PDT 2015
### Milestone URL: https://github.com/omega8cc/boa/milestones/2.4.3
  @=&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 customized for BOA
# Release Notes:
  This BOA release is focused on Aegir platforms update with latest Drupal core
  included. There are also a few system updates and bug fixes, as listed below.
# Changes:
  * Redis Integration Module: Update to version mod-08-05-2015
  * Use HTTPS intermediate mode to support legacy systems like XP/IE8 - see #718
# System upgrades:
  * Drush mini-7-08-05-2015
  * MariaDB 10.0.19
  * MariaDB Galera Cluster 10.0.19
  * PHP 5.4.41
  * PHP 5.5.25
  * PHP 5.6.9
  * Redis 3.0.1
# Fixes:
  * CiviCRM known bugs and regressions fixed
  * Improve drush aliases cleanup
  * Redis: sync net.core.somaxconn with tcp-backlog
  * sqlmagic: do not escape backslashes and EOL character - fixes #672
&lt;/pre&gt;&lt;p&gt;
The last BOA upgrade, &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/844" title="maintenance: Stable BOA 2.4.2 Release (closed: fixed)"&gt;ticket:844&lt;/a&gt; sent a email, &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/754#comment:26" title="maintenance: Can we upgrade from PHP 5.3? (closed: wontfix)"&gt;ticket:754#comment:26&lt;/a&gt; saying:
&lt;/p&gt;
&lt;pre class="wiki"&gt;Next BOA upgrade (2.4.3) will force PHP 5.5 on all hosted Aegir
instances, unless you will explicitly opt-out *before* that upgrade
using PHP version control files, as explained in our docs at:
  https://omega8.cc/how-to-quickly-switch-php-to-newer-version-330
&lt;/pre&gt;&lt;p&gt;
And we have been discussing if we should test running the site with PHP 5.5 on &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;PuffinServer&lt;/a&gt; or if we should create a development server to test with, this upgrade needs to wait till we have agreed a way forward.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/854#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/864</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/864</guid>
        <title>#864: BOA 2.4.5</title>
        <pubDate>Sun, 12 Jul 2015 08:36:38 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
A &lt;a class="ext-link" href="https://github.com/omega8cc/boa/blob/master/CHANGELOG.txt"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;new version of BOA&lt;/a&gt; came out on Friday:
&lt;/p&gt;
&lt;pre class="wiki"&gt;### Stable BOA-2.4.5 Release - Full Edition
### Date: Fri Jul 10 11:25:43 PDT 2015
### Milestone URL: https://github.com/omega8cc/boa/milestones/2.4.5
### Latest hotfix added on: Fri Jul 10 14:49:11 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 customized for BOA
# Release Notes:
  This BOA release includes PHP security upgrade for versions 5.6, 5.5 and 5.4
  plus security upgrade for Redis server and four updated Octopus platforms.
  Support for Drupal 8 is temporarily removed, because now it would require
  an upgrade to Drush 8, which in turn completely removes support for PHP 5.3,
  while it's still more important to support legacy Pressflow 6 sites, if they
  are not ready to move beyond PHP 5.3 yet, than trying to support some
  (too fast) moving targets like Drupal 8 beta, and Drush 8 head.
# Updated Octopus platforms:
  Commerce 2.26 ---------------- https://drupal.org/project/commerce_kickstart
  Commons 3.28 ----------------- https://drupal.org/project/commons
  OpenAtrium 2.43 -------------- https://drupal.org/project/openatrium
  Panopoly 1.25 ---------------- https://drupal.org/project/panopoly
# Changes:
  * Drupal 8 is not supported until we can switch to Drush 8 and remove PHP 5.3
# System upgrades:
  * Nginx 1.9.2
  * PHP 5.4.43
  * PHP 5.5.27
  * PHP 5.6.11
  * Redis 3.0.2
&lt;/pre&gt;&lt;p&gt;
See also:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/863" title="maintenance: BOA-2.4.4 (closed: wontfix)"&gt;ticket:863&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/854" title="maintenance: BOA 2.4.3 (closed: wontfix)"&gt;ticket:854&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;&lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/754" title="maintenance: Can we upgrade from PHP 5.3? (closed: wontfix)"&gt;ticket:754&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/864#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/872</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/872</guid>
        <title>#872: BOA 2.4.6</title>
        <pubDate>Tue, 22 Sep 2015 08:50:36 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
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;:
&lt;/p&gt;
&lt;pre class="wiki"&gt;### Stable BOA-2.4.6 Release - Full Edition
### Date: Sat Sep 19 11:09:09 PDT 2015
### Milestone URL: https://github.com/omega8cc/boa/milestones/2.4.6
### Latest hotfix added on: Mon Sep 21 05:18:33 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 customized for BOA
# Release Notes:
  This BOA release includes several important system upgrades and bug fixes.
  All supported Aegir platforms have been updated with latest Drupal cores.
  @=&amp;gt; Latest Drupal 8.0.0-beta15 works great, but currently only when installed
      as a custom platform in the ~/static directory tree, because it is not
      really symlinks-friendly. We will re-introduce built-in Drupal 8 platforms
      once this situation is improved.
# Changes:
  * Add Twig C extension to PHP - v.1.22.1
  * Allow to customize auto-upgrades mode
  * Disable support for broken OpenScholar and Recruiter
  * Open default Postgres port for outgoing connections
  * Remove support for deprecated Feature Server distro
  * Remove support for deprecated OpenAcademy distro
  * Remove support for deprecated OpenBlog distro
  * Remove support for deprecated OpenChurch v.1 distro
  * Remove support for deprecated OpenDeals distro
  * Use distro specific Drupal core for problematic distros
# System upgrades:
  * cURL 7.44.0 (if installed from sources)
  * Duplicity 0.7.05 (please run 'backboa install' to upgrade)
  * Jetty 7.6.17.v20150415
  * Jetty 8.1.17.v20150415
  * MariaDB 10.0.21
  * MariaDB 5.5.45
  * MariaDB Galera Cluster 10.0.21
  * Nginx 1.9.4
  * OpenSSH 7.1p1 (if installed from sources)
  * PHP 5.6.13, 5.5.29, 5.4.45
  * PHP: ionCube loader 5.0.18
  * Pure-FTPd 1.0.42
  * Redis 3.0.4
  * Ruby 2.2.3, 2.0.0-p647
  * Use pecl-jsmin-1.1.0
# Fixes:
  * Allow to re-install deleted D7/D6 platforms when dev doesn't exist
  * Do not install phpunit -- it adds many PHP tools we don't need
  * Drush requires php-eval to run drush_find_tmp() in sql-sync
  * Fix apache cleanup
  * Fix invalid regex in the INI docs
  * Improve auto-healing for SSHd
  * Improve Nginx DoS an DDoS protection
  * Improve pdnsd auto-healing
  * Improve SSL Docs to add more detail about multidomain certificates #757
  * Issue #766 - Fix for broken boa in-octopus procedure
  * Nginx: Fix support for s3/files/styles (s3fs)
  * Restart PHP-FPM if too many running childs are detected
  * Sync .htaccess with D7 core
  * Sync keywords for exceptions in daily.sh with global.inc
  * Use short sleep on firewall temp blocks cleanup
&lt;/pre&gt;&lt;p&gt;
Previous, un-applied BOA update tickets:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;BOA 2.4.5 &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/864" title="maintenance: BOA 2.4.5 (closed: wontfix)"&gt;ticket:864&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;BOA 2.4.4 &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/863" title="maintenance: BOA-2.4.4 (closed: wontfix)"&gt;ticket:863&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;BOA 2.4.3 &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/854" title="maintenance: BOA 2.4.3 (closed: wontfix)"&gt;ticket:854&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Is there any chance we might be able to discuss what we are going todo regarding the on-going hosting of the &lt;a class="ext-link" href="https://www.transitionnetwork.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Transition Network Drupal site&lt;/a&gt;? Some ideas were posted two weeks ago here &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/754#comment:61" title="maintenance: Can we upgrade from PHP 5.3? (closed: wontfix)"&gt;ticket:754#comment:61&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/872#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/798</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/798</guid>
        <title>#798: BOA-2.3.5</title>
        <pubDate>Thu, 16 Oct 2014 12:40:58 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The &lt;a class="ext-link" href="https://raw.githubusercontent.com/omega8cc/boa/master/CHANGELOG.txt"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;changelog&lt;/a&gt;:
&lt;/p&gt;
&lt;pre class="wiki"&gt;### Stable BOA-2.3.5 Release - Full Edition
### Date: Wed Oct 15 16:28:25 PDT 2014
### Includes Aegir 2.1 with improvements
### Latest hotfix added on: Wed Oct 15 20:09:52 PDT 2014
# Release Notes:
  This new BOA release includes important updates and bug fixes.
  * All new Drupal 7 platforms received Drupal core security upgrade.
    For details please read: https://www.drupal.org/SA-CORE-2014-005
  * All existing Drupal 7 built-in platforms will receive a hot-fix for
    this known vulnerability: https://www.drupal.org/SA-CORE-2014-005
    once you will run 'barracuda up-stable' command on your server.
    This procedure is automated on hosted and managed Aegir at Omega8.cc
  * Your custom D7 platforms created in the ~/static directory tree
    will be checked in the next 12 hours after the upgrade, and if you
    have not applied this patch yet, it will be applied automatically
    for you - but only if there is at least one active site present
    in the given custom D7 platform. Note that while this procedure is
    automated on hosted and managed Aegir at Omega8.cc, on self-hosted
    BOA systems it will work only if you will set _PERMISSIONS_FIX=YES
    in /root/.barracuda.cnf (default is NO)
  We recommend that you upgrade your D7 sites using safe workflow:
    https://omega8.cc/your-drupal-site-upgrade-safe-workflow-298
# Updated Octopus platforms:
  aGov 1.5 --------------------- https://drupal.org/project/agov
  Commerce 1.31 ---------------- https://drupal.org/project/commerce_kickstart
  Commerce 2.19 ---------------- https://drupal.org/project/commerce_kickstart
  Guardr 1.14 ------------------ https://drupal.org/project/guardr
  Open Atrium 2.22 ------------- https://drupal.org/project/openatrium
  Open Outreach 1.12 ----------- https://drupal.org/project/openoutreach
  OpenPublic 1.2 --------------- https://drupal.org/project/openpublic
  Panopoly 1.12 ---------------- https://drupal.org/project/panopoly
# New features and enhancements in this release:
  * Explain that Solr self-provisioning works only if _MODULES_FIX=YES is set.
  * Reverify all sites daily if /root/.force.sites.verify.cnf ctrl file exists
    and _PERMISSIONS_FIX=YES is set in /root/.barracuda.cnf (default is NO)
# Changes in this release:
  * Security: Remove support for SSLv3 due to POODLE vulnerability.
  * Disable Redis in Hostmaster until we will fix the Views based pages/blocks.
  * Disable site_readonly for non-dev sites by default.
  * Drush: Upgrade command line version 6 to mini-6-04-10-2014
  * Enable AllowUserFXP in Pure-FTPd config by default.
  * Remove support for already deprecated non-LTS Ubuntu versions.
  * Run manage_ip_auth_access only once per minute.
  * The INI variable redis_flush_forced_mode is enabled by default (again).
  * Use sysklogd instead of rsyslog on Ubuntu.
# System upgrades in this release:
  * MariaDB 5.5.40
  * Nginx 1.7.6
  * OpenSSH 6.7p1 (if installed from sources)
  * OpenSSL 1.0.1j (if installed from sources) - security upgrade.
  * PHPRedis: master-03-10-2014
# Fixes in this release:
  * Add auto-detection of Legacy Ruby patch level update on old systems.
  * Add cleanup for ghost/broken sites dirs leftovers.
  * Add missing cleanup for backup_migrate leftovers.
  * Always cleanup pid files on exit/abort.
  * Apply patch for SA-CORE-2014-005 in all shared D7 cores/built-in platforms.
  * Compass Tools: Install 1.9.3 ffi expected by older themes.
  * Fix db_port entry in all vhosts hourly.
  * Fix for broken erpal-7.x-2.0-7.31.1
  * Fix for broken site level drushrc.php file.
  * Fix for false alarm caused by ghost sites leftovers.
  * Fix for incorrect hash filtering on systems with OpenSSL built from sources.
  * Fix locales: Numerous fixes and improvements -- thanks ar-jan!
  * Fix typo in REVISIONS.
  * Force site Verify via frontend if drushrc.php has been fixed.
  * Issue #435 - SQL: Remove deprecated table_cache +update table_open_cache
  * Issue #440 - Improve innodb_buffer_pool_size calculation and add 10%
  * Issue #441 - New Relic is not disabled after removing newrelic.info file.
  * Issue #442 - Skip locked/fpmcheck if /root/.high_traffic.cnf exists.
  * Issue #444 - PHP: Remove useless sed replacement in pool.d/www{*}.conf
  * Issue #445 - Remote Import: update 6.x-2.x branch for Aegir 2.x and Drush 6
  * Issue #447 - Export LANG, LANGUAGE and all LC_ environment variables.
  * Issue #447 - Improve locales consistency.
  * Issue #447 - Set default LC_CTYPE and LC_COLLATE environment variables.
  * Issue #447 - Simplify locales configuration on Ubuntu.
  * Issue #448 - Enforce locale settings by configuring defaults.
  * Issue #452 - PHP build is broken with latest MariaDB 5.5.40
  * Make sure that db_port is never empty and defaults to 3306.
  * Make sure that firewall monitoring scripts never run simultaneously.
  * Make sure that standard caching is enabled in hostmaster.
  * Pause hostmaster tasks when RVM install for any user is running.
  * PHP: Do not run rebuilds if not needed.
  * PHP: Fix for broken upgrade logic on libcurl or libssl packages upgrade.
  * Remove acquia_connector from latest Commons to avoid broken installs.
  * Remove all legacy gems and re-install RVM/Ruby for root from scratch.
  * Remove legacy replacement to avoid converting symlinked includes into files.
  * SQL: Use correct defaults if MySQLTuner test failed.
  * Workaround for Drupal flood using 127.0.0.1 for all requests behind proxy.
### Stable BOA-2.3.4 Release - Full Edition
### Date: Wed Oct 15 09:51:08 PDT 2014
### Includes Aegir 2.1 with improvements
  Release Notes and changelog for BOA-2.3.4 has been merged into BOA-2.3.5
  above after security upgrades related to OpenSSL and SSLv3 have been added
  shortly after 2.3.4 release.
&lt;/pre&gt;&lt;p&gt;
I'm going to run this update tonight.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/798#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/863</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/863</guid>
        <title>#863: BOA-2.4.4</title>
        <pubDate>Thu, 09 Jul 2015 13:36:20 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Last Friday &lt;a class="ext-link" href="https://github.com/omega8cc/boa/blob/master/CHANGELOG.txt"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;a new version of BOA came out&lt;/a&gt; (for unknown reason(s) the automatic notification of new versions stopped working some months ago):
&lt;/p&gt;
&lt;pre class="wiki"&gt;### Stable BOA-2.4.4 Release - Full Edition
### Date: Fri Jul  3 12:08:29 PDT 2015
### Milestone URL: https://github.com/omega8cc/boa/milestones/2.4.4
### Latest hotfix added on: Wed Jul  8 01:28:08 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 customized for BOA
# Release Notes:
  This BOA release includes several important system upgrades and bug fixes.
  All supported Aegir platforms have been updated with latest Drupal cores.
  This version automatically switches all hosted sites to PHP 5.5 on systems
  hosted and managed remotely by Omega8.cc support team, unless you have
  explicitly switched your Octopus instance to use PHP version you prefer.
  Using PHP older than 5.5 is strongly discouraged, for security, stability and
  performance reasons.
# Changes:
  * Do not change mysql root password by default -- workaround for #642
  * Enable advagg_async_generation by default
  * Logic update for /root/.high_traffic.cnf
  * Redis Integration Module: Update to version mod-26-06-2015
  * Use modern ssl_ciphers in all templates by default
# System upgrades:
  * cURL 7.43.0 (if installed from sources)
  * Drush mini-7-30-06-2015 -- fixes #734
  * MariaDB 5.5.44
  * MariaDB Galera Cluster 10.0.20
  * Nginx 1.9.1
  * OpenSSH 6.9p1 (if installed from sources)
  * OpenSSL 1.0.1o (if installed from sources)
  * PHP 5.4.42
  * PHP 5.5.26
  * PHP 5.6.10
  * PHPRedis master-27-06-2015
  * Pure-FTPd 1.0.41
  * vnStat 1.14
# Fixes:
  * Add 'grep' to overssh -- a list of commands allowed to execute over SSH
  * Broken pdnsd configuration breaks DNS resolver -- fixes #701
  * Do not force update_agents()
  * Do not modify rkey/debug args in barracuda log/system upgrade mode
  * Don't remove Drupal 6 core themes -- fixes #738
  * Fix for legacy vnStat config
  * Fixed backboa/duobackboa retrieve from remote host -- fixes #741
  * Improve system cron tasks queue
  * Incorrect permissions on /usr/bin/optipng - fixes #722
  * Mitigate LOGJAM - fixes #723
  * Restart Postfix after system DNS update -- #701
  * Skip daily reload on high traffic instances
  * Sync SQL connection limits with _PHP_FPM_WORKERS variable - fixes #699
  * Use _AWS_URL to properly handle us-east-1 exception
  * Use 2048 bit where possible - see #723
  * Use better default value for advagg_cache_level - fixes #726
&lt;/pre&gt;&lt;p&gt;
I no longer know what the Transition Network policy is regarding BOA updates, the last one BOA 2.4.3, on &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/854" title="maintenance: BOA 2.4.3 (closed: wontfix)"&gt;ticket:854&lt;/a&gt; was never applied and as far as I'm aware there is no agreement / policy regarding what to do regarding PHP 5.3, see &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/754" title="maintenance: Can we upgrade from PHP 5.3? (closed: wontfix)"&gt;ticket:754&lt;/a&gt;.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/863#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/889</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/889</guid>
        <title>#889: BOA-2.4.7</title>
        <pubDate>Tue, 08 Dec 2015 17:35:35 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Following is 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;, please note this contains:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
&lt;strong&gt;This BOA release (2.4.7) is the last release which still supports deprecated PHP versions: 5.3 and 5.4&lt;/strong&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
And:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
&lt;strong&gt;We will support Drupal/Pressflow 6 in all new releases, as long as available PHP versions will allow to use it (we run our own Pressflow 6 based site on PHP 5.6 for many months with zero issues). For more details please check: &lt;a class="ext-link" href="https://github.com/omega8cc/boa/issues/824"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://github.com/omega8cc/boa/issues/824&lt;/a&gt;&lt;/strong&gt;
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
If we are sticking with Drupal 6 and BOA then I would suggest we should test the site on PHP 5.6 and if it is OK then upgrade, perhaps this should be done by spinning up a new virtual server and installing a new version of BOA on it and then copying the site over for testing?
&lt;/p&gt;
&lt;p&gt;
See also the tickets for the previous, un-applied, updates:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;BOA 2.4.6 &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/872" title="defect: BOA 2.4.6 (closed: wontfix)"&gt;ticket:872&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;BOA 2.4.5 &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/864" title="maintenance: BOA 2.4.5 (closed: wontfix)"&gt;ticket:864&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;BOA 2.4.4 &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/863" title="maintenance: BOA-2.4.4 (closed: wontfix)"&gt;ticket:863&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;BOA 2.4.3 &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/854" title="maintenance: BOA 2.4.3 (closed: wontfix)"&gt;ticket:854&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
And this ticket on the question of updating PHP: &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/754" title="maintenance: Can we upgrade from PHP 5.3? (closed: wontfix)"&gt;ticket:754&lt;/a&gt;
&lt;/p&gt;
&lt;pre class="wiki"&gt;### Stable BOA-2.4.7 Release - Full Edition
### Date: Fri Dec  4 08:09:21 PST 2015
### Milestone URL: https://github.com/omega8cc/boa/milestones/2.4.7
### Latest hotfix added on: Mon Dec  7 15:32:44 PST 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 customized for BOA
# Release Notes:
  This BOA release includes several important system upgrades and bug fixes,
  with most notable features and changes listed below.
  @=&amp;gt; All supported Aegir platforms have been updated with latest Drupal cores
  @=&amp;gt; Drupal 8 support for custom platforms in the ~/static directory tree
      will be included, along with Drush 8 and PHP 7 in the *upcoming*
      BOA-3.0.0 release: https://github.com/omega8cc/boa/milestones/3.0.0
  @=&amp;gt; This BOA release (2.4.7) is the last release which still supports
      deprecated PHP versions: 5.3 and 5.4 -- You should switch to PHP 5.6
      or at least 5.5 as soon as possible, or you will not be able to upgrade
      to newer BOA versions after 2.4.7 -- https://omega8.cc/node/330
  @=&amp;gt; What are BOA plans for Drupal 6 support after February 24th, 2016?
      We will support Drupal/Pressflow 6 in all new releases, as long as
      available PHP versions will allow to use it (we run our own Pressflow 6
      based site on PHP 5.6 for many months with zero issues). For more details
      please check: https://github.com/omega8cc/boa/issues/824
  @=&amp;gt; SSH keys for root are required by newer OpenSSH versions used in BOA
      BOA installs SSH from sources by default (Debian only). This means that
      password based access for root will not work once BOA is installed or
      upgraded to current stable version. It is a result of OpenSSH changes
      in recent releases and not BOA specific change. BOA will deny the initial
      install and Barracuda will refuse to run upgrade if it detects that system
      root has no SSH keys added and only password based access is available.
      You can still modify this behaviour in /usr/etc/sshd_config but future
      OpenSSH versions may still revert such changes, so it is not recommended.
  @=&amp;gt; BOA switched from SPDY to HTTP/2 + PFS on all supported OS versions
# Changes:
  * Allow to disable SQL monitoring with /root/.no.sql.cpu.limit.cnf -- #799
  * Disable page caching on the fly where needed
  * Disable temporarily support for broken Restaurant distro
  * Do not rebuild features and entities on cache clear
  * Document new requirement: SSH keys for root -- fixes #786 #833
  * Make ioncube_loader optional and disable by default with _PHP_IONCUBE=NO
  * Nginx SSL: enable OCSP stapling by default
  * Nginx SSL: enable OCSP stapling for existing HTTPS vhosts
  * Nginx: Add ssl_dhparam to existing vhosts, if needed
  * Nginx: HTTP/2 replaces SPDY -- fixes #624
  * PHP: Add YAML extension with LibYAML
  * Preserve customized /etc/sysctl.conf -- fixes #789
  * Run modules ON/OFF only weekly -- requires _MODULES_FIX=YES (default is NO)
  * Run most of crontab, install and upgrade tasks with low priority using
    nice and ionice -- fixes #780
# System upgrades:
  * cURL 7.45.0 (if installed from sources)
  * GEOS 3.5.0 (requires _PHP_GEOS=YES)
  * Git 2.6.1 (if installed from sources)
  * MariaDB 10.0.22
  * MariaDB 5.5.46
  * MariaDB Galera Cluster 10.0.22
  * Nginx 1.9.7
  * OpenSSL 1.0.2e (used only in custom built Nginx)
  * PHP 5.5.30
  * PHP 5.6.16
  * Redis 3.0.5
# Fixes:
  * Add /root/.skip_cleanup.cnf support
  * Add feature branch testing in HEAD
  * Avoid load spikes caused by long running tasks
  * Avoid race conditions on multi-line sed replacement -- fixes #806
  * Clean up any remaining procs zombies
  * Clean up postfix queue to get rid of bounced emails
  * Disable ioncube and opcache for HHVM
  * Disable Redis for Hostmaster in the backend
  * Do not allow to install non-standard OpenSSH on Ubuntu
  * Do not break /data/all/cpuinfo permissions on Octopus upgrade
  * Do not run 'apt-get autoremove' automatically
  * Do not use wrapper for dot-files cleanup
  * Document better BOA aggressive installation behavior -- fixes #811
  * Document boa in-octopus command -- fixes #817
  * Don't strip $args from $request_uri in redirects
  * Fix cron schedule for upgrades
  * Fix for broken Git on Ubuntu
  * Fix for not working PHP rebuild check
  * Fix for not working syncpass tool
  * Fix PHP deprecated warning in D8 -- fixes #804
  * Ignore 'env COLUMNS' sent by Drush remotely -- fixes #373
  * Ignore daily.sh in clear.sh
  * Improve _SQUEEZE_TO_WHEEZY procedure -- #627
  * Improve cron tasks schedule
  * Improve daily cleanup performance + support for /root/.giant_traffic.cnf
  * Improve devpts check -- fixes #788
  * Improve docs/MIGRATE.txt
  * Improve resolv.conf auto-recovery procedure
  * Improve system check -- fixes #811
  * Move Redis restart procedure to correct script
  * PHP: Add missing path to open_basedir for CLI
  * Remove debug code to not kill the initial install
  * Remove not working /etc/logrotate.d/lshell -- fixes #823
  * Update advagg auto configuration variables -- fixes #792
  * Update boa/lib/functions/helper.sh.inc with current OS -- fixes #787
  * Update FPM workers autoconf logic
  * Update the cache cleanup logic
  * Use better placeholder for solr_integration_module variable
  * Use correct DPkg::Options for dist-upgrade -- fixes #627
  * Use known MySQLTuner version -- fixes #827
  * Use LibYAML 0.1.6
  * Use opcache.restrict_api
  * Use sha256 for self-signed certs
&lt;/pre&gt;&lt;p&gt;
If we are not going to stick with BOA then can we please consider the suggestions in this comment? &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/754#comment:61" title="maintenance: Can we upgrade from PHP 5.3? (closed: wontfix)"&gt;ticket:754#comment:61&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/889#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/589</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/589</guid>
        <title>#589: Blocking spammers at a firewall level</title>
        <pubDate>Fri, 06 Sep 2013 09:48:59 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
At the meeting on 5th September &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/585" title="maintenance: TTech Meeting 5th September 2013 (closed: fixed)"&gt;ticket:585&lt;/a&gt; one thing we discussed was that for August 2013:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;blockquote&gt;
&lt;p&gt;
More data is transferred for /user/register than the front page, 5.1GB compared to 3.6GB.
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;/blockquote&gt;
&lt;p&gt;
Most of this will be spam bots trying to register to post spam. Jim suggested that we could look at blocking some of these spam bots at a firewall level to save on resources. This ticket is to follow up on this suggestion.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/589#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/565</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/565</guid>
        <title>#565: Blogs breadcrumbs incorrect on listings views</title>
        <pubDate>Tue, 25 Jun 2013 13:21:56 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Blogs breadcrumbs are wrong at main all blogs view and one author's full list view:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/blog"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/blog&lt;/a&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/blogs/ed-mitchell"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/blogs/ed-mitchell&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Jim can you sort this in under 15 minutes (which is what you have left)
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/565#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/544</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/544</guid>
        <title>#544: CSF / LDF false positive blocks on Puffin</title>
        <pubDate>Sat, 04 May 2013 11:02:53 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Ticket to keep track of CSF /LDF issues on Puffin, see &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer#CSFLDF"&gt;wiki:PuffinServer#CSFLDF&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/544#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/605</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/605</guid>
        <title>#605: Can we make the subscriptions management admin view re-order-able?</title>
        <pubDate>Thu, 03 Oct 2013 13:35:17 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
I use this view when I need to find subscriptions for users who are receiving email alerts to old accounts:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/messaging/subscriptions"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/messaging/subscriptions&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
I am finding that if a user changes their email address in their user account, it does not update that email address in the subscriptions settings, so they continue to receive alerts to their old address. So I go to this view, dig out the incorrect sub, and kill it.
&lt;/p&gt;
&lt;p&gt;
Which is a PITA.
&lt;/p&gt;
&lt;p&gt;
Can we make it possible to make the 'users' column clickable so I could re-order it alphabetically? That would be really cool.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/605#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/754</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/754</guid>
        <title>#754: Can we upgrade from PHP 5.3?</title>
        <pubDate>Sat, 05 Jul 2014 20:52:48 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The Transition Network site is running on PHP 5.3 and it's got &lt;a class="ext-link" href="https://www.sektioneins.de/en/blog/14-07-04-phpinfo-infoleak.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;a very serious security issue&lt;/a&gt; which potentially enables a remote attacked to get the servers private SSL key. Would Drupal work OK with PHP 5.4?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/754#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/628</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/628</guid>
        <title>#628: Change space notifications email from IJK.co.uk to TN.org</title>
        <pubDate>Thu, 21 Nov 2013 16:50:37 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
The space notifications are coming from "space.transitionnetwork.org" &amp;lt;jim@…&amp;gt;
&lt;/p&gt;
&lt;p&gt;
can you make them from
"space.transitionnetwork.org" and a suitable TN address?
&lt;/p&gt;
&lt;p&gt;
Do I need to set up a suitable TN address? Perhaps
&lt;/p&gt;
&lt;p&gt;
space@…?
&lt;/p&gt;
&lt;p&gt;
Or is there a standard drupal system one in place already?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/628#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/621</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/621</guid>
        <title>#621: Check and speed up updates to homepage sections: TC and slideshow</title>
        <pubDate>Mon, 18 Nov 2013 09:22:59 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

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

        <description>&lt;p&gt;
The SRs are reporting very slow site updates - is this to do with not switching them over to the new views content caching? please check:
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/build/views/edit/blogs?destination=stories#views-tab-panel_pane_2"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/build/views/edit/blogs?destination=stories#views-tab-panel_pane_2&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/build/block/configure/views/blogs-block_1?destination=newhome"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/build/block/configure/views/blogs-block_1?destination=newhome&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
And elsewhere there may be SR latest views?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/658#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/896</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/896</guid>
        <title>#896: Chive access to TN Drupal DB</title>
        <pubDate>Mon, 18 Jan 2016 17:56:44 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Ade would like to give the developers of the new Transition Network  &lt;a class="wiki" href="http://localhost:8080/trac/wiki/WordPress"&gt;WordPress&lt;/a&gt; site access to the live database via Chive.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/896#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/624</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/624</guid>
        <title>#624: Comment handling on pages: particularly Austerity one</title>
        <pubDate>Tue, 19 Nov 2013 11:16:02 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Rob is doing an austerity special over 8 days, with a different clip from an interview with NEF every day. I've set up a page here:
/austerity-basics
&lt;/p&gt;
&lt;p&gt;
Question:
&lt;/p&gt;
&lt;p&gt;
I know we can handle comments on pages, and I know that I don't get notifications of them. Can we arrange comment notifications for a page - asap - so that commenters get updates?
&lt;/p&gt;
&lt;p&gt;
If not, no problem. I heard about this plan *today* so am not expecting any massive tech leaps.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/624#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/578</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/578</guid>
        <title>#578: Comments subscriptions: enable user alerts if a user has made a comment</title>
        <pubDate>Mon, 12 Aug 2013 13:33:58 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Can we set the email alerts to auto-subscribe users to comments threads that they have made comments on? ie I make a comment to blog post x, then I get email alerts of the new comments made to blog post x.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/578#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/777</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/777</guid>
        <title>#777: Comments to blog post only showing up when logged in</title>
        <pubDate>Mon, 25 Aug 2014 09:18:39 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Most of the comments to this blog post are only showing up when you are logged in:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/blogs/rob-hopkins/2014-07/fiona-ward-learning-celebrate-10000-failure#comment-17492"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/blogs/rob-hopkins/2014-07/fiona-ward-learning-celebrate-10000-failure#comment-17492&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Logged in: 5 comments
Not logged in: 1 comment
&lt;/p&gt;
&lt;p&gt;
Handing this to Sam but happy for it to escalate. Presumably this issue won't be on this one post only - and it is important.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/777#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/683</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/683</guid>
        <title>#683: Create Aegir account for Paul</title>
        <pubDate>Wed, 22 Jan 2014 12:42:48 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Jim
&lt;/p&gt;
&lt;p&gt;
It looks like i@… will be joining us to pick up some of your work.
&lt;/p&gt;
&lt;p&gt;
Could you create an Aegir account for him please?
&lt;/p&gt;
&lt;p&gt;
I was also wondering about the Transition Network Github repo, do we need to do anything to hand that over?
&lt;/p&gt;
&lt;p&gt;
Thanks
&lt;/p&gt;
&lt;p&gt;
Sam
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/683#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/822</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/822</guid>
        <title>#822: Create TRAC id for Ade</title>
        <pubDate>Wed, 07 Jan 2015 09:54:13 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
name: ade
email: adestuart@…
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/822#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/682</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/682</guid>
        <title>#682: Create Trac &amp; Wiki account for Paul</title>
        <pubDate>Wed, 22 Jan 2014 12:39:18 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi it looks like i@… will be joining us to pick up some of Jim's role as he moves on.
&lt;/p&gt;
&lt;p&gt;
Chris could you create a trac &amp;amp; Wiki account for him please?
&lt;/p&gt;
&lt;p&gt;
His email is; i@…
&lt;/p&gt;
&lt;p&gt;
Thanks
&lt;/p&gt;
&lt;p&gt;
Sam
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/682#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/705</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/705</guid>
        <title>#705: Create a contents page on TransitionCulture.org Wordpress site</title>
        <pubDate>Wed, 26 Mar 2014 15:33:43 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Create a contents page on TC.org to see a listing of all the blog posts. Mike suggests:
"use category post list widget to pull in the titles and then use widgetise pages to add widget to a standard page.:
&lt;/p&gt;
&lt;p&gt;
Sam to follow up. MAX time: 1 hour.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/705#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/829</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/829</guid>
        <title>#829: Creation of web space request</title>
        <pubDate>Mon, 02 Feb 2015 10:11:03 GMT</pubDate>
        
        <dc:creator>ade</dc:creator>

        <description>&lt;p&gt;
Hi Chris,
As discussed, can you please set up some webspace on Penguin?
If you could also set up a sub-domain of 'projects' and confirm the FTP access details?
&lt;/p&gt;
&lt;p&gt;
Many thanks
Ade
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/829#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/208</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/208</guid>
        <title>#208: Dblog Issues</title>
        <pubDate>Fri, 17 Dec 2010 14:53:29 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

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

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

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

        <description>&lt;p&gt;
Ben reported that the default owner for tickets is laura and that this should be changed.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/597#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/572</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/572</guid>
        <title>#572: Design changes for homepage and TC section</title>
        <pubDate>Wed, 17 Jul 2013 14:17:25 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Design changes for TN homepage and TC section done by Ben to be part of maintenance budget.
&lt;/p&gt;
&lt;p&gt;
list here:
&lt;a class="ext-link" href="https://docs.google.com/spreadsheet/ccc?key=0An7ZaZdq6UfJdDhxS0JxbXZLYnhLRkN4X3h5aVV3R1E#gid=0"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://docs.google.com/spreadsheet/ccc?key=0An7ZaZdq6UfJdDhxS0JxbXZLYnhLRkN4X3h5aVV3R1E#gid=0&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/572#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/667</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/667</guid>
        <title>#667: Development handover process</title>
        <pubDate>Wed, 08 Jan 2014 16:40:47 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Work by the Ttech team to share Jim's knowledge and tasks around the team before he leaves in early February 2014. Please use this ticket to log your time spent on this.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/667#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/696</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/696</guid>
        <title>#696: Disk space error on parrot for TTT site</title>
        <pubDate>Mon, 03 Mar 2014 10:51:46 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

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

        <description>&lt;p&gt;
Getting this alert from &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;ParrotServer&lt;/a&gt; every 5 mins:
&lt;/p&gt;
&lt;pre class="wiki"&gt;transitionnetwork.org :: parrot.transitionnetwork.org :: Disk usage in percent
        WARNINGs: /home is 96.06 (outside range [:96]).
        OKs: /run/shm is 0.00, /run is 0.09, /dev is 0.00, / is 95.94, / is 95.94, /run/lock is 0.00.
&lt;/pre&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/911#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/531</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/531</guid>
        <title>#531: Disk usage on puffin</title>
        <pubDate>Wed, 10 Apr 2013 13:12:24 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The disk usage on puffing is currently at 85% and it's been going up at around 5% a week, see:
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://penguin.transitionnetwork.org/munin/transitionnetwork.org/puffin.transitionnetwork.org/df.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://penguin.transitionnetwork.org/munin/transitionnetwork.org/puffin.transitionnetwork.org/df.html&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
This will become a critical issue in a couple of weeks, it would be good to find and address the cause before then.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/531#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/574</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/574</guid>
        <title>#574: EFF: How HTTPS Everywhere affects transitionnetwork.org</title>
        <pubDate>Thu, 25 Jul 2013 08:09:31 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The following email was sent via the whois contact details for the  transitionnetwork.org domain name, see also &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/571" title="enhancement: Force HTTP for anonymous, HTTPS for logged in users (closed: fixed)"&gt;ticket:571&lt;/a&gt; -- the changes made on &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/571" title="enhancement: Force HTTP for anonymous, HTTPS for logged in users (closed: fixed)"&gt;ticket:571&lt;/a&gt; has broken the site for anon Firefox users with the EFF HTTPS Everywhere browser extension installed.
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Hi,
&lt;/p&gt;
&lt;p&gt;
You're receiving this note because transitionnetwork.org is part of our HTTPS
Everywhere browser extension, and an upcoming change to the way
Firefox handles HTTPS pages may cause your site to display or function
incorrectly. We want to make sure that the nearly 3 million HTTPS
Everywhere users have the best possible experience while browsing, so
we're asking you to please take a minute and test how your site
behaves in Firefox 23.  You can find out more about our software at
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.eff.org/https-everywhere"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.eff.org/https-everywhere&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
To see the rules affecting your site, you can visit the HTTPS Everywhere
Atlas at
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.eff.org/https-everywhere/atlas/domains/transitionnetwork.org.html"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.eff.org/https-everywhere/atlas/domains/transitionnetwork.org.html&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
The Atlas shows both rules in the development and stable versions of
our extension.  Rules in the stable version are used by millions of
users, while development rules are used by tens of thousands of users.
Development rules are now being tested but will be migrated to the stable
version in the future.
&lt;/p&gt;
&lt;p&gt;
&lt;strong&gt;An upcoming change (described below) in how the Firefox browser renders
HTTPS content makes it especially important that you check that your site
is prepared for HTTPS access.  We urge you review the rules affecting
your site and also to test it using HTTPS Everywhere with the upcoming
version of Firefox.&lt;/strong&gt;
&lt;/p&gt;
&lt;p&gt;
*NEW FIREFOX CONTENT SECURITY POLICY*: In the upcoming Firefox 23 browser
release, due out the week of August 6, Firefox will stop loading certain
"active" content such as scripts and stylesheets from insecure &lt;a class="ext-link" href="http://"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://&lt;/a&gt;
URLs if they've been included from a secure &lt;a class="ext-link" href="https://"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://&lt;/a&gt; site.  If the HTTPS
Everywhere rules send users to the secure version of your site but the
secure version includes some content loaded over an insecure connetion,
the rendering of your site may become broken for Firefox users with HTTPS
Everywhere installed after they upgrade to Firefox 23.  You can check
this by downloading a preview release of Firefox 23, installing HTTPS
Everywhere, and visiting your site.  We urge all web site operators
to protect their users by making sure that all site content is always
loaded over a secure connection.  A preview version of Firefox 23 is
available now at &lt;a class="ext-link" href="https://www.mozilla.org/en-US/firefox/beta/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.mozilla.org/en-US/firefox/beta/&lt;/a&gt; and the
HTTPS Everywhere extension is at &lt;a class="ext-link" href="https://www.eff.org/https-everywhere"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.eff.org/https-everywhere&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
HTTPS Everywhere rules instruct browsers to access certain specified
resources securely -- over HTTPS -- even if the user typed or followed
a non-HTTPS link or even if the resources were included in a page
via a non-HTTPS URL.  For example, it might automatically rewrite
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="http://www.transitionnetwork.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.transitionnetwork.org/&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
to
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
or make some similar change.
&lt;/p&gt;
&lt;p&gt;
The goal of this rewriting is to protect as much as possible of every web
site against sniffing and tampering by ensuring that as many site resources
as possible are loaded over a secure HTTPS connection.
&lt;/p&gt;
&lt;p&gt;
When web sites are accessed insecurely, users are vulnerable to attacks by
other users on their networks.  HTTPS Everywhere aims to activate sites'
existing HTTPS protection more consistently to make sure users are as
well-protected from these attacks as possible -- including attacks like
sidejacking and SSL stripping.
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="http://www.firesheep.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.firesheep.org/&lt;/a&gt;
&lt;a class="ext-link" href="http://www.thoughtcrime.org/sslstrip"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.thoughtcrime.org/sslstrip&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
As a result, we think there's an emerging consensus to make all web sites
secure, not just financial sites and login pages.  Providing a secure
connection helps protect users' login credentials, but also helps protect
their privacy and security even when accessing public resources, for
example by preventing network operators from injecting malware downloads.
&lt;/p&gt;
&lt;p&gt;
The goal of HTTPS Everywhere is to make the web more secure and help
users express their preference to use the secure version of every site
automatically, even on sites where this is not the default.  We don't want
to break sites or harm users' experience.  So, we encourage webmasters to
test the effect of HTTPS Everywhere on their sites and fix any problems
that result -- ideally, by making sure that all resources that make up
a site are available over HTTPS, using a current, valid certificate.
Although we only include rules that we've been told and believe work
properly, we can't always anticipate whether a rule adversely affects a
site, especially if the site's URL structure, use of CDNs, or level of
HTTPS support changes over time.
&lt;/p&gt;
&lt;p&gt;
We are always happy to receive bug reports, updates, and fixes to HTTPS
Everywhere rules.  We will also make rules inactive by default if a
site operator asks us to.  Although we are working for a web where
all sites are secure, we are not trying to use this software to force
sites to use HTTPS against their operators' wishes.  You can send any
corrections, updates, or requests to https-everywhere-rules@…
(which is a public and publicly-archived mailing list), or by replying
to this e-mail address.
&lt;/p&gt;
&lt;p&gt;
Thanks for your attention!
&lt;/p&gt;
&lt;p&gt;
Seth Schoen, Senior Staff Technologist, Electronic Frontier Foundation
for the HTTPS Everywhere development team
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/574#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/648</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/648</guid>
        <title>#648: Edit the contact form reply in January</title>
        <pubDate>Thu, 12 Dec 2013 10:49:39 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

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

        <description>&lt;p&gt;
Set up: 'trac@…'
Password: going to Chris separately
Secure SSL/TLS Settings
Username: trac@…
Password: Use the email account’s password.
Incoming Server: mail.xssl.net
IMAP: Port 993
POP3: Port 995
Outgoing Server: mail.xssl.net
SMTP: Port 465
Authentication is required for IMAP, POP3, and SMTP.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/494#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/751</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/751</guid>
        <title>#751: Email alert changes</title>
        <pubDate>Tue, 01 Jul 2014 11:14:42 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;ol&gt;&lt;li&gt;Change the email alert template for news items to include the term 'news item' so it is:
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
"New news item: [title]"
&lt;/p&gt;
&lt;ol start="2"&gt;&lt;li&gt;When users click on the subs links at the bottom of their email alerts, and they are not logged in they get the ‘access denied’ screen. This is not good. Please investigate
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
(a) can this be changed (with small time investment)
(b) can we change the access denied blurb to include something human encouraging the user to login to continue the journey:
&lt;/p&gt;
&lt;p&gt;
"We are sorry for the inconvenience, but if you are seeing this screen having followed a link, you will probably need to login to continue with your request" (NB if they are coming from an email link with their id in it, how do we keep that journey so they get to the destinateion they wanted?)
&lt;/p&gt;
&lt;ol start="3"&gt;&lt;li&gt;When user clicks on the general subs link at the bottom of an email alert (and is not logged in), they get a 403 forbidden page. Not good - pls investigage
&lt;/li&gt;&lt;/ol&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/751#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/634</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/634</guid>
        <title>#634: Embeds - some don't work</title>
        <pubDate>Wed, 27 Nov 2013 11:50:23 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
I couldn't embed a 'paper.li' embed into a page recently and forgot about it. Now I can't embed a slideshare embed either adn wonder if I am seeing a pattern.
&lt;/p&gt;
&lt;p&gt;
Please look and advise:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/blogs/ed-mitchell/2013-11/web-strategy-update"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/blogs/ed-mitchell/2013-11/web-strategy-update&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/634#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/641</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/641</guid>
        <title>#641: Enable dynamic Munin graphs</title>
        <pubDate>Mon, 02 Dec 2013 15:25:45 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
If we only generate munin graphs on the fly we will also get the zoom function working, this example config looks good: &lt;a class="ext-link" href="http://uname.pingveno.net/blog/index.php/post/2013/08/25/Configure-Munin-graphs-with-Nginx-and-Debian-7"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://uname.pingveno.net/blog/index.php/post/2013/08/25/Configure-Munin-graphs-with-Nginx-and-Debian-7&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/641#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/659</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/659</guid>
        <title>#659: Featured story on homepage not updating</title>
        <pubDate>Mon, 16 Dec 2013 17:03:41 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Rob cleared the nodequeue for the featured story on the homepage about three hours ago, removed all but one story. No change has been observed. Please investigate:
&lt;/p&gt;
&lt;p&gt;
Nodequeue:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/content/nodequeue/6/view/5"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/content/nodequeue/6/view/5&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
This view:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/build/views/edit/featured_content?destination=newhome#views-tab-panel_pane_1"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/build/views/edit/featured_content?destination=newhome#views-tab-panel_pane_1&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
This is using content cache
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/659#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/695</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/695</guid>
        <title>#695: File upload problem with TTT WordPress site</title>
        <pubDate>Sun, 02 Mar 2014 19:46:50 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Laura has reported:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Had a report this evening that the TTT website isn't letting any uploads happen (adding of a new plugin by another admin, and also media/image uploads not being able to uploaded - no real error message as such just doesn't upload).
&lt;/p&gt;
&lt;p&gt;
I just logged in quickly to see if I could upload a pic to test and wouldn't upload.
Just wanted to check if anything had changed server side re permissions.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/695#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/679</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/679</guid>
        <title>#679: Filter Initiative by Country not working</title>
        <pubDate>Fri, 17 Jan 2014 17:15:58 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Filtering the initiatives by country is not working
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/initiatives?themes=All&amp;amp;community_type=All&amp;amp;status_value=All&amp;amp;country=at&amp;amp;field_title_search="&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/initiatives?themes=All&amp;amp;community_type=All&amp;amp;status_value=All&amp;amp;country=at&amp;amp;field_title_search=&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
I had a play with the view on stg2.transitionnetwork.org but I couldn't get it working.
&lt;/p&gt;
&lt;p&gt;
It should display only initiatives from the country selected in the filter. It is displaying initiatives from all countries &amp;amp; not respecting the filter.
&lt;/p&gt;
&lt;p&gt;
This view is used a lot by international initiatives.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/679#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/571</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/571</guid>
        <title>#571: Force HTTP for anonymous, HTTPS for logged in users</title>
        <pubDate>Tue, 16 Jul 2013 11:59:54 GMT</pubDate>
        
        <dc:creator>jim</dc:creator>

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

        <description>&lt;p&gt;
I'm getting three copies of the stats reports (weekly) that I've set up here:
&lt;a class="ext-link" href="https://stats.transitionnetwork.org/index.php?module=PDFReports&amp;amp;action=index&amp;amp;idSite=1&amp;amp;period=day&amp;amp;date=today"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://stats.transitionnetwork.org/index.php?module=PDFReports&amp;amp;action=index&amp;amp;idSite=1&amp;amp;period=day&amp;amp;date=today&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Please investigate
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/607#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/786</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/786</guid>
        <title>#786: GitHub Transition: Annesley needs permission to create repositories</title>
        <pubDate>Mon, 15 Sep 2014 07:17:03 GMT</pubDate>
        
        <dc:creator>annesley</dc:creator>

        <description>&lt;p&gt;
is Paul the owner of Transition &lt;a class="missing wiki"&gt;GitHub?&lt;/a&gt;?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/786#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/895</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/895</guid>
        <title>#895: HTTPS wildcard *.transitionnnetwork.org expires on 22nd January 2016</title>
        <pubDate>Mon, 11 Jan 2016 09:56:17 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Unless I hear otherwise I'll renew the &lt;tt&gt;*.transitionnnetwork.org&lt;/tt&gt; cert which is used by &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer"&gt;PuffinServer&lt;/a&gt;, &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PenguinServer"&gt;PenguinServer&lt;/a&gt; and &lt;a class="wiki" href="http://localhost:8080/trac/wiki/ParrotServer"&gt;ParrotServer&lt;/a&gt; at a cost of &lt;a class="ext-link" href="https://www.webarch.net/certs"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;£130.50&lt;/a&gt; on or before the 22nd January 2016 when the &lt;a class="ext-link" href="https://www.ssllabs.com/ssltest/analyze.html?d=transitionnetwork.org&amp;amp;latest"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;current one expires&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
An alternative would be to use &lt;a class="new ticket" href="http://localhost:8080/trac/ticket/875" title="maintenance: Free HTTPS certificates from Let's Encrypt (new)"&gt;Free HTTPS certificates from Let's Encrypt&lt;/a&gt; but this would take some time to set up as &lt;a class="ext-link" href="https://www.letsencrypt.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Let's Encrypt&lt;/a&gt; don't provide wild card certs.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/895#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/921</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/921</guid>
        <title>#921: HTTP_PROXY env var vulnerability</title>
        <pubDate>Tue, 19 Jul 2016 12:34:30 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
See &lt;a class="ext-link" href="https://httpoxy.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://httpoxy.org/&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/921#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/717</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/717</guid>
        <title>#717: Heartbleed / Open SSL vunerability</title>
        <pubDate>Wed, 09 Apr 2014 20:50:37 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Chris
&lt;/p&gt;
&lt;p&gt;
I don't think I have seen a ticket for this? &lt;a class="ext-link" href="http://heartbleed.com/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://heartbleed.com/&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Does it affect us?
&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/717#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/617</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/617</guid>
        <title>#617: Help adding text to account creation email</title>
        <pubDate>Mon, 11 Nov 2013 17:16:37 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
I want to add a link to the email a user receives following their creation of an account.
&lt;/p&gt;
&lt;p&gt;
this one: Subject: Account details for [user] at Transition Network
&lt;/p&gt;
&lt;p&gt;
Can I do this myself? I've looked in subs, notifications, logintoboggan etc. and can't find the place
&lt;/p&gt;
&lt;p&gt;
is it do-able?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/617#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/650</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/650</guid>
        <title>#650: Helping TN strategy consultation with online publishing</title>
        <pubDate>Thu, 12 Dec 2013 11:00:08 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

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

        <description>&lt;p&gt;
Big picture slideshow on TN homepage: Rob can't get it to go in the order he wants - please investigate:
&lt;/p&gt;
&lt;p&gt;
It is this nodequeue:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/content/nodequeue/9/view/8"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/content/nodequeue/9/view/8&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Made up with these CTs:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/content/node-type/slide"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/content/node-type/slide&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/657#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/906</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/906</guid>
        <title>#906: I borked it</title>
        <pubDate>Tue, 01 Mar 2016 22:27:10 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Chris
&lt;/p&gt;
&lt;p&gt;
I recklessly tried to enable a module on the site that enabled sending articles to friends by email, this seems to have been one of my less-good ideas.
&lt;/p&gt;
&lt;p&gt;
It tried to enable a print-friendly page and this seems to have brought the whole crumbling edifice down
&lt;/p&gt;
&lt;p&gt;
Sorry about that. Can you fix it?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/906#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/837</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/837</guid>
        <title>#837: Iframe in a panel page</title>
        <pubDate>Thu, 12 Mar 2015 11:55:21 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Ben
&lt;/p&gt;
&lt;p&gt;
I'm trying to embed a Eventbrite form into the 'tickets' block on this page: &lt;a class="ext-link" href="https://www.transitionnetwork.org/conference-2015"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/conference-2015&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
It looks like it's going to appear in the preview here: &lt;a class="ext-link" href="https://www.transitionnetwork.org/node/39195/panel_content"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/node/39195/panel_content&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
But when I view the actual page it's just a big white space.
&lt;/p&gt;
&lt;p&gt;
Could you estimate how long it would take to get it working?
&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/837#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/703</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/703</guid>
        <title>#703: Image not scaling on project</title>
        <pubDate>Wed, 26 Mar 2014 13:06:15 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
The REconomy logo is not scaling and being re-presented well on the project page:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/projects/reconomy"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/projects/reconomy&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Is this a theme/design issue or a problem with image re-sizing?
&lt;/p&gt;
&lt;p&gt;
What can we do about it?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/703#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/704</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/704</guid>
        <title>#704: Image not scaling on project</title>
        <pubDate>Wed, 26 Mar 2014 13:51:48 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
The REconomy logo is not scaling and being re-presented well on the project page:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/projects/reconomy"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/projects/reconomy&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Is this a theme/design issue or a problem with image re-sizing?
&lt;/p&gt;
&lt;p&gt;
What can we do about it?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/704#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/710</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/710</guid>
        <title>#710: Incorrect email address for Sam on Transition Culture</title>
        <pubDate>Tue, 01 Apr 2014 12:01:47 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

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

        <description>&lt;p&gt;
Initiatives Map not showing on http
&lt;/p&gt;
&lt;p&gt;
here error message:
This web site needs a different Google Maps API key. A new key can be generated at &lt;a class="ext-link" href="http://code.google.com/apis/maps/documentation/javascript/v2/introduction.html#Obtaining_Key"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://code.google.com/apis/maps/documentation/javascript/v2/introduction.html#Obtaining_Key&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
is this related to &lt;a class="closed ticket" href="http://localhost:8080/trac/ticket/615" title="task: Move to GMap 6.x-2.x-dev as and get clusterer to work (closed: fixed)"&gt;#615&lt;/a&gt;?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/616#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/560</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/560</guid>
        <title>#560: Install drupal-based project management system onto our servers</title>
        <pubDate>Tue, 11 Jun 2013 17:00:28 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Please can you install a suitable project management drupal-based tool onto the suitable server? I am thinking of Open Atrium. It's for staff and partners to use for management stuff (ie not a ticketing system or mediawiki).
&lt;/p&gt;
&lt;p&gt;
Open Atrium?
&lt;/p&gt;
&lt;p&gt;
Can you let me know how long it would take to install to a point where I can manage it and get a pilot project up and running?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/560#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/673</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/673</guid>
        <title>#673: Install mosh - the mobile shell</title>
        <pubDate>Mon, 13 Jan 2014 11:27:40 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The mobile shell enables terminal connections to stay up when using really bad connections, for example on a train, see:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="http://mosh.mit.edu/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://mosh.mit.edu/&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/673#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/553</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/553</guid>
        <title>#553: Invalid response from server ERROR message</title>
        <pubDate>Tue, 28 May 2013 15:13:43 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Trying to add a user. Get error message: "Received an Invalid response from the server" then served a blank screen. Same with project profile:
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/user/user/create"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/user/user/create&lt;/a&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/node/add/project-profile"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/node/add/project-profile&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
This has also happened for a user trying to add a project.
&lt;/p&gt;
&lt;p&gt;
Ed can add an event and blog post, ingredient, panel page.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/553#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/891</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/891</guid>
        <title>#891: Issue with TTT and REconomy websites after upgrade to WP 4.4</title>
        <pubDate>Thu, 17 Dec 2015 11:18:38 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Email from Laura:
&lt;/p&gt;
&lt;blockquote class="citation"&gt;
&lt;p&gt;
Just to let you know there's a bit of an oddity going on with both the TTT and
Reconomy websites.
&lt;/p&gt;
&lt;p&gt;
I upgraded to WP 4.4 after running full tests on my local copies here, and for
some odd reason images aren't showing on the site.  If you try to open an
image in the browser eg
&lt;a class="ext-link" href="https://www.reconomy.org/wp-content/uploads/2015/10/hubs-logos-landscape.jpg"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.reconomy.org/wp-content/uploads/2015/10/hubs-logos-landscape.jpg&lt;/a&gt;
takes you to the -
"Server error!
The server encountered an internal error and was unable to complete your
request
Either the server is overloaded or there was an error in a CGI script.
Please return to the front page of the site."
&lt;/p&gt;
&lt;p&gt;
I've updated over 20 sites over the past few days (!) and these are the only
two this has happened on.
There are a few discussions here, (and have tried the temp fix of various
functions.php tweaks in the theme files to see if that helps, but it
doesn't)...
&lt;a class="ext-link" href="https://wordpress.org/support/topic/after-upgrade-to-44-media-files-are-not-showing"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://wordpress.org/support/topic/after-upgrade-to-44-media-files-are-not-showing&lt;/a&gt;
and even though sites are not appearing to use SSL wondering if related
somehow to that or other? Has this happened to any other WP 4.4 sites on your
servers?
&lt;/p&gt;
&lt;p&gt;
I'll let TTT and REconomy know their site has been updated, but there is a
glitch at present.
&lt;/p&gt;
&lt;p&gt;
I've also added Wordfence to the sites too as there are swathes of brute force
attacks happening on lots of WP sites everywhere currently and this plugin
seems to help somewhat currently.  I don't think it's the Wordfence plugin, as
disabled it to test the missing images issue.
&lt;/p&gt;
&lt;/blockquote&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/891#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/846</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/846</guid>
        <title>#846: Load Spikes on BOA PuffinServer</title>
        <pubDate>Thu, 16 Apr 2015 11:16:00 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Creating this as a ticket to record load spikes and related site outages.
&lt;/p&gt;
&lt;p&gt;
See &lt;a class="wiki" href="http://localhost:8080/trac/wiki/PuffinServer#LoadSpikes"&gt;wiki:PuffinServer#LoadSpikes&lt;/a&gt; for links to historic issues of this nature.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/846#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/555</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/555</guid>
        <title>#555: Load spikes causing the TN site to be stopped for 15 min at a time</title>
        <pubDate>Wed, 29 May 2013 09:53:52 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

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