<?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?component=Drupal+modules+%26+settings&amp;milestone=Maintenance&amp;group=status&amp;desc=1&amp;order=id</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?component=Drupal+modules+%26+settings&amp;milestone=Maintenance&amp;group=status&amp;desc=1&amp;order=id</link>
    </image>
    <generator>Trac 0.12.5</generator>
    <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/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/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/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/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/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/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/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/908</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/908</guid>
        <title>#908: Please enable Google Analytics</title>
        <pubDate>Thu, 10 Mar 2016 15:43:56 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi all
&lt;/p&gt;
&lt;p&gt;
The web project board has decided to move from Piwik to Google Analytics.
&lt;/p&gt;
&lt;p&gt;
I realise this has significant privacy implications, these were discussed, but it was decided that the move would go ahead.
&lt;/p&gt;
&lt;p&gt;
I have discussed with Ainslie adding an opt out in the form of a link to EFF's Privacy badger: &lt;a class="ext-link" href="https://www.eff.org/privacybadger"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.eff.org/privacybadger&lt;/a&gt; This will be added to the cookie pop up bar in the new website.
&lt;/p&gt;
&lt;p&gt;
Could we enable the Google Analytics module on the existing site so I can add in the tracking code.
&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/908#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/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/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/785</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/785</guid>
        <title>#785: SA-CONTRIB-2014-086 - Custom BreadCrumbs - Cross Site Scripting (XSS)</title>
        <pubDate>Thu, 11 Sep 2014 15:54:35 GMT</pubDate>
        
        <dc:creator>paul</dc:creator>

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

        <description>&lt;p&gt;
hi, am trying to get a copy of the current TN.org D6 database and filesystem down to my laptop to develop against. i had pulled from GIT, backed up from Backup&amp;amp;Migrate and got everything working but there are things missing.
&lt;/p&gt;
&lt;p&gt;
so i want to do a file copy. i started a tar operation but the tar size went over 1.3GB and i stopped it because it shouldn't be that big. as always BOA has restricted use of the "du" command so i can't really tell why the tar was so big. and i can't "df" to see if it's a problem
&lt;/p&gt;
&lt;p&gt;
should i let it continue? why is it so big?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/773#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/755</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/755</guid>
        <title>#755: Site administrator's file upload capacity: not responding to changes</title>
        <pubDate>Tue, 08 Jul 2014 09:21:16 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Rob Hopkins reached the limit for file uploads and could not upload any more images (not good for him as he writes posts with lots of pictures daily).
&lt;/p&gt;
&lt;p&gt;
Sam raised the limit. This change in the limit does not seem to have affected Rob's situation - he still can't upload any images.
&lt;/p&gt;
&lt;p&gt;
Looking at these settings:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/settings/uploads"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/settings/uploads&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Rob should be able to upload more - he is a site editor and admin - but he can't.
&lt;/p&gt;
&lt;p&gt;
Please investigate
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/755#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/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/724</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/724</guid>
        <title>#724: Subscription emails from Rob's blog not arriving.</title>
        <pubDate>Tue, 29 Apr 2014 09:21:12 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
A user has got in touch to let us know he is not getting Rob's updates by email. He's still subscribed.
&lt;/p&gt;
&lt;p&gt;
I just checked my mail and the last one I received was on the 11/4. I'll have a look and see if I can work it out.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/724#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/708</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/708</guid>
        <title>#708: Map not showing Indian initiative</title>
        <pubDate>Thu, 27 Mar 2014 13:44:29 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/initiatives/heal-soil-csa-community-supported-agriculture"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/initiatives/heal-soil-csa-community-supported-agriculture&lt;/a&gt;
Address is correct, but doesn’t appear. The person who put it there doesn’t appear on the people map either, so wondering what’s afoot.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/708#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/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/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/693</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/693</guid>
        <title>#693: Module security updates: February 2014</title>
        <pubDate>Thu, 27 Feb 2014 16:18:04 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Paul
&lt;/p&gt;
&lt;p&gt;
You'll see from this ticket; &lt;a class="ext-link" href="https://trac.transitionnetwork.org/trac/ticket/582"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://trac.transitionnetwork.org/trac/ticket/582&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
That the 6.29 &amp;gt; 6.30 core update patches bugs that don't affect us.
&lt;/p&gt;
&lt;p&gt;
However some recent security updates for modules have been released recently; &lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/reports/updates"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/reports/updates&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Affected modules are;
&lt;/p&gt;
&lt;p&gt;
ctools;
&lt;a class="ext-link" href="https://drupal.org/node/2194547"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://drupal.org/node/2194547&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
filefield
&lt;a class="ext-link" href="https://drupal.org/node/2194103"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://drupal.org/node/2194103&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
image resizer
&lt;a class="ext-link" href="https://drupal.org/node/2194063"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://drupal.org/node/2194063&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
mimemail
&lt;a class="ext-link" href="https://drupal.org/node/2205939"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://drupal.org/node/2205939&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
webform
&lt;a class="ext-link" href="https://drupal.org/node/2194181"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://drupal.org/node/2194181&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
The ctools &amp;amp; webform ones look like ones we should get on top of soonish, the mimemail one looks like it could be a pain.
&lt;/p&gt;
&lt;p&gt;
Are you up for testing the updates on your local box? We can then figure out how to roll them out to the live site.
&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/693#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/680</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/680</guid>
        <title>#680: Mixed content: HTTP content on HTTPS version of site</title>
        <pubDate>Mon, 20 Jan 2014 12:28:18 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
The &lt;a class="ext-link" href="https://www.transitionnetwork.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;front page of the site&lt;/a&gt; contains the following elements using HTTP when accessing the site using HTTPS:
&lt;/p&gt;
&lt;pre class="wiki"&gt;  &amp;lt;div class="views-field-field-slide-image-fid"&amp;gt;
                &amp;lt;span class="field-content"&amp;gt;&amp;lt;img src="http://www.transitionnetwork.org/sites/www.transitionnetwork.org/files/imagecache/slideshow_660/images/slides/capture1.jpg" alt="" title="" width="700" height="306" class="imagecache imagecache-slideshow_660 imagecache-default imagecache-slideshow_660_default"/&amp;gt;&amp;lt;/span&amp;gt;
  &amp;lt;/div&amp;gt;
&lt;/pre&gt;&lt;pre class="wiki"&gt;  &amp;lt;div class="views-field-field-slide-destination-link-url"&amp;gt;
                &amp;lt;span class="field-content"&amp;gt;&amp;lt;a href="http://www.transitionnetwork.org/about" 0="a:0:{}" class="learn"&amp;gt;Learn more about Transition Network »&amp;lt;/a&amp;gt;&amp;lt;/span&amp;gt;
  &amp;lt;/div&amp;gt;
&lt;/pre&gt;&lt;pre class="wiki"&gt;  &amp;lt;div class="views-field-field-slide-image-fid"&amp;gt;
                &amp;lt;span class="field-content"&amp;gt;&amp;lt;img src="http://www.transitionnetwork.org/sites/www.transitionnetwork.org/files/imagecache/slideshow_660/images/slides/clay.jpg" alt="" title="" width="700" height="306" class="imagecache imagecache-slideshow_660 imagecache-default imagecache-slideshow_660_default"/&amp;gt;&amp;lt;/span&amp;gt;
  &amp;lt;/div&amp;gt;
&lt;/pre&gt;&lt;pre class="wiki"&gt;  &amp;lt;div class="views-field-field-slide-destination-link-url"&amp;gt;
                &amp;lt;span class="field-content"&amp;gt;&amp;lt;a href="http://www.transitionnetwork.org/blogs/rob-hopkins/2014-01/can-earth-building-scale-mainstream-1-clayworks-and-clay-plasters" 0="a:0:{}" class="learn"&amp;gt;Read more here »&amp;lt;/a&amp;gt;&amp;lt;/span&amp;gt;
  &amp;lt;/div&amp;gt;
&lt;/pre&gt;&lt;pre class="wiki"&gt;  &amp;lt;div class="views-field-field-slide-image-fid"&amp;gt;
                &amp;lt;span class="field-content"&amp;gt;&amp;lt;img src="http://www.transitionnetwork.org/sites/www.transitionnetwork.org/files/imagecache/slideshow_660/images/slides/frack3.jpg" alt="" title="" width="700" height="306" class="imagecache imagecache-slideshow_660 imagecache-default imagecache-slideshow_660_default"/&amp;gt;&amp;lt;/span&amp;gt;
  &amp;lt;/div&amp;gt;
&lt;/pre&gt;&lt;pre class="wiki"&gt;  &amp;lt;div class="views-field-field-slide-destination-link-url"&amp;gt;
                &amp;lt;span class="field-content"&amp;gt;&amp;lt;a href="http://www.transitionnetwork.org/blogs/rob-hopkins/2014-01/6-reasons-why-theres-no-community-fracking" 0="a:0:{}" class="learn"&amp;gt;Read more here »&amp;lt;/a&amp;gt;&amp;lt;/span&amp;gt;
  &amp;lt;/div&amp;gt;
&lt;/pre&gt;&lt;pre class="wiki"&gt;  &amp;lt;div class="views-field-field-slide-image-fid"&amp;gt;
                &amp;lt;span class="field-content"&amp;gt;&amp;lt;img src="http://www.transitionnetwork.org/sites/www.transitionnetwork.org/files/imagecache/slideshow_660/images/slides/pc1.jpg" alt="" title="" width="700" height="306" class="imagecache imagecache-slideshow_660 imagecache-default imagecache-slideshow_660_default"/&amp;gt;&amp;lt;/span&amp;gt;
  &amp;lt;/div&amp;gt;
&lt;/pre&gt;&lt;pre class="wiki"&gt;  &amp;lt;div class="views-field-field-featured-image-fid"&amp;gt;
                &amp;lt;span class="field-content"&amp;gt;&amp;lt;a href="/news/2013-12-17/november-and-december-round-what-s-happening-out-world-transition" class="imagecache imagecache-featured_image_thumb imagecache-linked imagecache-featured_image_thumb_linked"&amp;gt;&amp;lt;img src="http://www.transitionnetwork.org/sites/www.transitionnetwork.org/files/imagecache/featured_image_thumb/chilesml.jpg" alt="Chile Transition Training" title="Chile Transition Training" width="150" height="101" class="imagecache imagecache-featured_image_thumb"/&amp;gt;&amp;lt;/a&amp;gt;&amp;lt;/span&amp;gt;
  &amp;lt;/div&amp;gt;
&lt;/pre&gt;&lt;p&gt;
Would it be possible to embed content from the site using URLS like &lt;tt&gt;/sites/www.transitionnetwork.org/files/imagecache/featured_image_thumb/chilesml.jpg&lt;/tt&gt; rather than &lt;tt&gt;http://www.transitionnetwork.org/sites/www.transitionnetwork.org/files/imagecache/featured_image_thumb/chilesml.jpg&lt;/tt&gt; ?
&lt;/p&gt;
&lt;p&gt;
Changing these links would result in the mixed content warnings in browsers going away.
&lt;/p&gt;
&lt;p&gt;
By default Firefox doesn't block HTTP content over HTTPS connections, however you can enable this by entering &lt;tt&gt;about:config&lt;/tt&gt; in the URL bar are searching for &lt;tt&gt;mixed_content&lt;/tt&gt; and then changing &lt;tt&gt;security.mixed_content.block_display_content&lt;/tt&gt; to &lt;strong&gt;true&lt;/strong&gt; if you want to see how the site looks when only secure content is loaded.
&lt;/p&gt;
&lt;p&gt;
I have checked that the site does set the &lt;strong&gt;secure&lt;/strong&gt; flag on the authentication cookie, so the mixed content shouldn't result in the authentication cookie being sent with unencrypted requests.
&lt;/p&gt;
&lt;p&gt;
Further information:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;&lt;a class="ext-link" href="https://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/680#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/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/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/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/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/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/654</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/654</guid>
        <title>#654: TIs appearing in 'TIs by list' view without a number</title>
        <pubDate>Thu, 12 Dec 2013 12:43:12 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Some TIs are appearing in the 'Initiatives by number' view - but don't have numbers:
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/initiatives/by-number"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/initiatives/by-number&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
for Sam to invesitage and solve or put to techs in January
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/654#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/653</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/653</guid>
        <title>#653: Report for ingredients content type</title>
        <pubDate>Thu, 12 Dec 2013 11:36:53 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

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

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

        <description>&lt;p&gt;
For January:
set up a report for tools content type:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;downloadable in .xls
&lt;/li&gt;&lt;li&gt;tool title
&lt;/li&gt;&lt;li&gt;URL (must be a hyperlink generated in .csv)
&lt;/li&gt;&lt;li&gt;node reference
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
No tools report exists yet - but lots of others here:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/reports"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/reports&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/651#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/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/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/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/637</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/637</guid>
        <title>#637: What is the wordcount for the /news and /blogs/rob-hopkins teasers?</title>
        <pubDate>Thu, 28 Nov 2013 09:40:48 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
&lt;a class="ext-link" href="http://www.transitionnetwork.org/news"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.transitionnetwork.org/news&lt;/a&gt;
&lt;a class="ext-link" href="http://www.transitionnetwork.org/blogs/rob-hopkins"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.transitionnetwork.org/blogs/rob-hopkins&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
what is the teaser length - ie the first paragraph of a news or blog item that is published in the listings views?
&lt;/p&gt;
&lt;p&gt;
rob wants to know how many words he has for his introductions...
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/637#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/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/633</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/633</guid>
        <title>#633: RHS blocks changes for homepage</title>
        <pubDate>Mon, 25 Nov 2013 15:27:15 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

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

        <description>&lt;p&gt;
Can users delete their own accounts?
I've looked at user settings and can't find any clues?
Can you point me to a user account setting which would enable them to delete their own accounts (and their profiles by proxy)?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/627#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/623</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/623</guid>
        <title>#623: Question about revisions</title>
        <pubDate>Mon, 18 Nov 2013 17:21:46 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
do we keep any revisions of content? we had this conversation years ago, it came up in a recent social reporters webinar, I can't see any evidence of revisions activity...
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/623#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/622</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/622</guid>
        <title>#622: Maps not working on TN.org</title>
        <pubDate>Mon, 18 Nov 2013 17:06:59 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/initiatives/map"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/initiatives/map&lt;/a&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/initiatives/exeter-nh-transition-town"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/initiatives/exeter-nh-transition-town&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
please attend
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/622#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/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/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/615</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/615</guid>
        <title>#615: Move to GMap 6.x-2.x-dev as and get clusterer to work</title>
        <pubDate>Sun, 10 Nov 2013 18:14:51 GMT</pubDate>
        
        <dc:creator>jim</dc:creator>

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

        <description>&lt;p&gt;
We want a button on the Social Reporters section that enables users to easily subscribe to the Social Reporters' blog posts CT. Offers the option to all types of user:
&lt;/p&gt;
&lt;ol class="loweralpha"&gt;&lt;li&gt;Users may not be logged in
&lt;/li&gt;&lt;li&gt;Users may not be registered
&lt;/li&gt;&lt;/ol&gt;&lt;ol&gt;&lt;li&gt;This is a bit like the sub button on Transition Culture section
&lt;/li&gt;&lt;li&gt;I can't find it in TRAC but have this memory of enabling email-only subscriptions to not-registered-users from olden days - can you enlighten me about that? I'm not sure it's the answer - we probably want them to register so they can add comments - but this request has brought up that old function
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
..
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/614#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/608</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/608</guid>
        <title>#608: User profile pictures are too big</title>
        <pubDate>Mon, 14 Oct 2013 08:37:38 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
The user profile pictures on the user profile nodes are too big.
&lt;/p&gt;
&lt;p&gt;
e.g.
&lt;a class="ext-link" href="https://transitionnetwork.org/people/tina-clarke"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://transitionnetwork.org/people/tina-clarke&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Please investigate and restrain them into a suitable maximum size
&lt;/p&gt;
&lt;p&gt;
NB: Ed is keeping a number of small UI-ish tickets back for Ben to do in a lump when we've built up enough so don't do anything yet.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/608#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/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/602</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/602</guid>
        <title>#602: RSS problems</title>
        <pubDate>Thu, 03 Oct 2013 09:14:43 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

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

        <description>&lt;p&gt;
The news CT has a featured image, but it doesn't seem to be handling it as expected (succesfully on the blogs). See this news item:
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/news/2013-09-03/new-economy-20-enterprises-report-released"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/news/2013-09-03/new-economy-20-enterprises-report-released&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
The featured image isn't visible anywhere - either:
&lt;/p&gt;
&lt;ol class="loweralpha"&gt;&lt;li&gt;in the news item itself
&lt;/li&gt;&lt;li&gt;in the /news view
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
Please investigate and resolve
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/584#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/581</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/581</guid>
        <title>#581: Remove 'add to newsletter' option for site editors/admins</title>
        <pubDate>Mon, 26 Aug 2013 13:24:17 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Please remove the option for site editors/admins to 'add this to the newsletter' (which would send it to the newsletter nodequeue). Please also for now make the newsletter nodequeue non-active.
&lt;/p&gt;
&lt;p&gt;
It's been confusing for staff members, and was for the simmplemail service really, so we're going to trial using a google doc for staff to add their stories to the newsletter instead.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/581#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/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/575</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/575</guid>
        <title>#575: User system is blocking *everyone* - needs fixing urgently</title>
        <pubDate>Wed, 31 Jul 2013 14:39:11 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Everyone who registers for the last two weeks is being blocked - check user list and see screengrab. Needs fixing promptly.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/575#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/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/570</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/570</guid>
        <title>#570: Notifications: not sending complete URL</title>
        <pubDate>Tue, 09 Jul 2013 13:19:57 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Notification for blog post does not include full URL.
&lt;/p&gt;
&lt;p&gt;
URL in notification is:
&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;
&lt;a class="ext-link" href="http://www.transitionnetwork.org/blogs/rob-hopkins/2013-07/transition-th"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.transitionnetwork.org/blogs/rob-hopkins/2013-07/transition-th&lt;/a&gt;...
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;
URL should be:
&lt;a class="ext-link" href="http://www.transitionnetwork.org/blogs/rob-hopkins/2013-07/transition-thursdays-three-down-three-go"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://www.transitionnetwork.org/blogs/rob-hopkins/2013-07/transition-thursdays-three-down-three-go&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/570#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/568</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/568</guid>
        <title>#568: TC blog: can't *not* send notifications</title>
        <pubDate>Mon, 08 Jul 2013 10:20:16 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
I can't see how to do a node edit and *not* send a notification - here seen on the Transition Culture blog:
&lt;/p&gt;
&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/node/32863/edit"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/node/32863/edit&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
please advise - there's been some kerfuffle about the TC blog move so swift resolution much appreciated
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/568#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/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/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/207</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/207</guid>
        <title>#207: Logwatch Issues</title>
        <pubDate>Fri, 17 Dec 2010 14:19:50 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

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

        <description>&lt;p&gt;
The &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; site has been "off-line" since about 7pm, I see that Paul is logged on via &lt;tt&gt;ssh&lt;/tt&gt; -- is this something that we should worry about or is this intentional?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/919#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/907</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/907</guid>
        <title>#907: TN Drupal database size</title>
        <pubDate>Wed, 02 Mar 2016 10:20:10 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
6 weeks ago the datadase dump was 447M, see &lt;a class="ext-link" href="http://trac.edgewall.org/intertrac/ticket/896%23comment%3A3" title="ticket/896#comment:3 in Trac project trac"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;trac:ticket/896#comment:3&lt;/a&gt; but now it is 1.8G:
&lt;/p&gt;
&lt;pre class="wiki"&gt;ls -lah /var/backups/mysql/sqldump/transitionnetw_0.sql
-rw------- 1 root root 1.8G Mar  2 01:23 /var/backups/mysql/sqldump/transitionnetw_0.sql
&lt;/pre&gt;&lt;p&gt;
Anyone have any idea what happened to cause this? Are we keeping too many log entries?
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/907#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/874</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/874</guid>
        <title>#874: Please check &amp; then install Georss if no problems</title>
        <pubDate>Tue, 29 Sep 2015 13:31:02 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Paul
&lt;/p&gt;
&lt;p&gt;
We'd like to play around with generating Georss from our current site.
&lt;/p&gt;
&lt;p&gt;
Could you have a glance at the code /test &lt;a class="ext-link" href="https://www.drupal.org/project/georss"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/project/georss&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
If it seems like it's going to be unproblematic then please install it on the live site.
&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/874#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/821</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/821</guid>
        <title>#821: Projects forms being hammered by Spam</title>
        <pubDate>Wed, 07 Jan 2015 09:53:33 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
Projects forms being hammered by spammers. I got 24 in the last 45 minutes.
&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;
What to do?
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;ol&gt;&lt;li&gt;Lock off to a certain type of user?
&lt;/li&gt;&lt;li&gt;
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
?
&lt;/p&gt;
&lt;p&gt;
Adding Sam as owner to follow this up
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/821#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/809</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/809</guid>
        <title>#809: [Security-news] Drupal Core - Moderately Critical - Multiple Vulnerabilities - SA-CORE-2014-006</title>
        <pubDate>Wed, 19 Nov 2014 21:35:25 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-006"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/SA-CORE-2014-006&lt;/a&gt;
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Advisory ID: DRUPAL-SA-CORE-2014-006
&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-November-19
&lt;/li&gt;&lt;li&gt;Security risk: 14/25 ( Moderately Critical)
AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:Uncommon &lt;a class="missing changeset" title="No default repository defined"&gt;[2]&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;Vulnerability: Multiple vulnerabilities
&lt;/li&gt;&lt;/ul&gt;&lt;hr /&gt;
&lt;hr /&gt;
&lt;p&gt;
.... Session hijacking (Drupal 6 and 7)
&lt;/p&gt;
&lt;p&gt;
A specially crafted request can give a user access to another user's session,
allowing an attacker to hijack a random session.
&lt;/p&gt;
&lt;p&gt;
This attack is known to be possible on certain Drupal 7 sites which serve
both HTTP and HTTPS content ("mixed-mode" &lt;a class="missing changeset" title="No default repository defined"&gt;[3]&lt;/a&gt;), but it is possible there are
other attack vectors for both Drupal 6 and Drupal 7.
&lt;/p&gt;
&lt;p&gt;
.... Denial of service (Drupal 7 only)
&lt;/p&gt;
&lt;p&gt;
Drupal 7 includes a password hashing API to ensure that user supplied
passwords are not stored in plain text.
&lt;/p&gt;
&lt;p&gt;
A vulnerability in this API allows an attacker to send specially crafted
requests resulting in CPU and memory exhaustion. This may lead to the site
becoming unavailable or unresponsive (denial of service).
&lt;/p&gt;
&lt;p&gt;
This vulnerability can be exploited by anonymous users.
&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
accordance
&lt;/li&gt;&lt;/ul&gt;&lt;blockquote&gt;
&lt;blockquote&gt;
&lt;p&gt;
with Drupal Security Team processes./
&lt;/p&gt;
&lt;/blockquote&gt;
&lt;/blockquote&gt;
&lt;hr /&gt;
&lt;hr /&gt;
&lt;ul&gt;&lt;li&gt;Drupal core 6.x versions prior to 6.34.
&lt;/li&gt;&lt;li&gt;Drupal core 7.x versions prior to 7.34.
&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.34. &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 7.x, upgrade to Drupal core 7.34. &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 have configured a custom password.inc file for your Drupal 7 site you
also need to make sure that it is not prone to the same denial of service
vulnerability.  See also the similar security advisory for the Drupal 6
contributed Secure Password Hashes module: SA-CONTRIB-2014-113 &lt;a class="missing changeset" title="No default repository defined"&gt;[7]&lt;/a&gt;
&lt;/p&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;p&gt;
Session hijacking:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Aaron Averill &lt;a class="missing changeset" title="No default repository defined"&gt;[9]&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Denial of service:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Michael Cullum  &lt;a class="missing changeset" title="No default repository defined"&gt;[10]&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;Javier Nieto &lt;a class="missing changeset" title="No default repository defined"&gt;[11]&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;Andrés Rojas Guerrero &lt;a class="missing changeset" title="No default repository defined"&gt;[12]&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;hr /&gt;
&lt;hr /&gt;
&lt;p&gt;
Session hijacking:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Klaus Purer &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;David Rothstein &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;Peter Wolanin &lt;a class="missing changeset" title="No default repository defined"&gt;[15]&lt;/a&gt; of the Drupal Security Team
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Denial of service:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Klaus Purer &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;Peter Wolanin &lt;a class="missing changeset" title="No default repository defined"&gt;[17]&lt;/a&gt; of the Drupal Security Team
&lt;/li&gt;&lt;li&gt;Heine Deelstra &lt;a class="missing changeset" title="No default repository defined"&gt;[18]&lt;/a&gt; of the Drupal Security Team
&lt;/li&gt;&lt;li&gt;Tom Phethean &lt;a class="missing changeset" title="No default repository defined"&gt;[19]&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;hr /&gt;
&lt;hr /&gt;
&lt;ul&gt;&lt;li&gt;The Drupal Security Team
&lt;/li&gt;&lt;/ul&gt;&lt;hr /&gt;
&lt;hr /&gt;
&lt;p&gt;
The Drupal security team can be reached at security at drupal.org or via the
contact form at &lt;a class="ext-link" href="https://www.drupal.org/contact"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/contact&lt;/a&gt; &lt;a class="missing changeset" title="No default repository defined"&gt;[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;
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;[24]&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[1]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/project/drupal"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.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="https://www.drupal.org/security-team/risk-levels"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/security-team/risk-levels&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[3]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/https-information"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/https-information&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="https://www.drupal.org/drupal-6.34-release-notes"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/drupal-6.34-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="https://www.drupal.org/drupal-7.34-release-notes"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/drupal-7.34-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/node/2378367"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/node/2378367&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/project/drupal"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.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/1317732"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/1317732&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/u/MichaelCu"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/u/MichaelCu&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/jnietotn"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/u/jnietotn&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/u/c0r3dump3d"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/u/c0r3dump3d&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/u/klausi"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/u/klausi&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/u/David_Rothstein"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/u/David_Rothstein&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/pwolanin"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/u/pwolanin&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/u/klausi"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/u/klausi&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/u/pwolanin"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/u/pwolanin&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/u/Heine"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/u/Heine&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/u/tsphethean"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/u/tsphethean&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/contact"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/contact&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[21]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/security-team"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/security-team&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[22]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/writing-secure-code"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/writing-secure-code&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[23]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/security/secure-configuration"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/security/secure-configuration&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[24]&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;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/809#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/792</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/792</guid>
        <title>#792: [Security-news] SA-CONTRIB-2014-094 - Webform Patched - Cross Site Scripting (XSS)</title>
        <pubDate>Mon, 29 Sep 2014 09:28:08 GMT</pubDate>
        
        <dc:creator>paul</dc:creator>

        <description>&lt;p&gt;
View online: &lt;a class="ext-link" href="https://www.drupal.org/node/2344369"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/node/2344369&lt;/a&gt;
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Advisory ID: DRUPAL-SA-CONTRIB-2014-094
&lt;/li&gt;&lt;li&gt;Project: Webform Patched &lt;a class="missing changeset" title="No default repository defined"&gt;[1]&lt;/a&gt; (third-party module)
&lt;/li&gt;&lt;li&gt;Version: 6.x, 7.x
&lt;/li&gt;&lt;li&gt;Date: 2014-September-24
&lt;/li&gt;&lt;li&gt;Security risk: 13/25 ( Moderately Critical)
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:Default &lt;a class="missing changeset" title="No default repository defined"&gt;[2]&lt;/a&gt;
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Vulnerability: Cross Site Scripting
&lt;/li&gt;&lt;/ul&gt;&lt;hr /&gt;
&lt;hr /&gt;
&lt;p&gt;
The Webform Patched module is a fork of the Webform module with Token support
added. The module enables you to create forms which can be used for surveys,
contact forms or other data collection throughout your site.
&lt;/p&gt;
&lt;p&gt;
The module doesn't sufficiently sanitize field label titles when two fields
have the same form_key, which can only be managed by carefully crafting the
webform structure via a specific set of circumstances.
&lt;/p&gt;
&lt;p&gt;
This vulnerability is mitigated by the fact that an attacker must have a role
with the permission "create webform content".
&lt;/p&gt;
&lt;hr /&gt;
&lt;hr /&gt;
&lt;ul&gt;&lt;li&gt;/A CVE identifier &lt;a class="missing changeset" title="No default repository defined"&gt;[3]&lt;/a&gt; will be requested, and added upon issuance, in
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
accordance
with Drupal Security Team processes./
&lt;/p&gt;
&lt;hr /&gt;
&lt;hr /&gt;
&lt;ul&gt;&lt;li&gt;Webform Patched 6.x-3.x versions prior to 6.x-3.20.
&lt;/li&gt;&lt;li&gt;Webform Patched 7.x-3.x versions prior to 7.x-3.20.
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Drupal core is not affected. If you do not use the contributed Webform
Patched &lt;a class="missing changeset" title="No default repository defined"&gt;[4]&lt;/a&gt; module,
there is nothing you need to do.
&lt;/p&gt;
&lt;hr /&gt;
&lt;hr /&gt;
&lt;p&gt;
Install the latest version:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;If you use the webform module for Drupal 6.x, upgrade to webform_patched
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
6.x-3.20 &lt;a class="missing changeset" title="No default repository defined"&gt;[5]&lt;/a&gt;
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;If you use the webform module for Drupal 7.x-3.x, upgrade to
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
webform_patched 7.x-3.20 &lt;a class="missing changeset" title="No default repository defined"&gt;[6]&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Also see the Webform Patched &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;Maurits Lawende &lt;a class="missing changeset" title="No default repository defined"&gt;[8]&lt;/a&gt;
&lt;/li&gt;&lt;li&gt;Matt Vance &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;Nate Haug &lt;a class="missing changeset" title="No default repository defined"&gt;[10]&lt;/a&gt; the module maintainer
&lt;/li&gt;&lt;/ul&gt;&lt;hr /&gt;
&lt;hr /&gt;
&lt;ul&gt;&lt;li&gt;Greg Knaddison &lt;a class="missing changeset" title="No default repository defined"&gt;[11]&lt;/a&gt;, Dan Smith &lt;a class="missing changeset" title="No default repository defined"&gt;[12]&lt;/a&gt; and Lee Rowlands &lt;a class="missing changeset" title="No default repository defined"&gt;[13]&lt;/a&gt; of the Drupal
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Security Team
&lt;/p&gt;
&lt;hr /&gt;
&lt;hr /&gt;
&lt;p&gt;
The Drupal security team can be reached at security at drupal.org or via the
contact form at
&lt;a class="ext-link" href="https://www.drupal.org/contact"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/contact&lt;/a&gt; &lt;a class="missing changeset" title="No default repository defined"&gt;[14]&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;[15]&lt;/a&gt;,
writing secure code for Drupal &lt;a class="missing changeset" title="No default repository defined"&gt;[16]&lt;/a&gt;, and
securing your site &lt;a class="missing changeset" title="No default repository defined"&gt;[17]&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[1]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/project/webform_patched"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/project/webform_patched&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[2]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/security-team/risk-levels"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/security-team/risk-levels&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[3]&lt;/a&gt; &lt;a class="ext-link" href="http://cve.mitre.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://cve.mitre.org/&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[4]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/project/webform_patched"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/project/webform_patched&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/node/2241675"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/node/2241675&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/node/2241685"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/node/2241685&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[7]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/project/webform_patched"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/project/webform_patched&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/user/243897"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/user/243897&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/10269"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/10269&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://drupal.org/user/35821"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/user/35821&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://drupal.org/user/36762"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/user/36762&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[12]&lt;/a&gt; &lt;a class="ext-link" href="http://drupal.org/user/241220"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://drupal.org/user/241220&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://drupal.org/user/395439"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://drupal.org/user/395439&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/contact"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/contact&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[15]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/security-team"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/security-team&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[16]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/writing-secure-code"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/writing-secure-code&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[17]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/security/secure-configuration"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/security/secure-configuration&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/792#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/789</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/789</guid>
        <title>#789: SA-CONTRIB-2014-088 - Mollom - Cross-site scripting (XSS)</title>
        <pubDate>Mon, 22 Sep 2014 13:09:48 GMT</pubDate>
        
        <dc:creator>paul</dc:creator>

        <description>&lt;p&gt;
View online: &lt;a class="ext-link" href="https://www.drupal.org/node/2340029"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/node/2340029&lt;/a&gt;
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Advisory ID: DRUPAL-SA-CONTRIB-2014-088
&lt;/li&gt;&lt;li&gt;Project: Mollom &lt;a class="missing changeset" title="No default repository defined"&gt;[1]&lt;/a&gt; (third-party module)
&lt;/li&gt;&lt;li&gt;Version: 6.x, 7.x
&lt;/li&gt;&lt;li&gt;Date: 2014-September-17
&lt;/li&gt;&lt;li&gt;Security risk: 11/25 ( Moderately Critical)
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
AC:Complex/A:User/CI:Some/II:Some/E:Theoretical/TD:Uncommon &lt;a class="missing changeset" title="No default repository defined"&gt;[2]&lt;/a&gt;
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Vulnerability: Cross Site Scripting
&lt;/li&gt;&lt;/ul&gt;&lt;hr /&gt;
&lt;hr /&gt;
&lt;p&gt;
Mollom is an "intelligent" content moderation web service which determines if
a post is potentially spam; not only based on the posted content, but also on
the past activity and reputation of the poster across multiple sites.
&lt;/p&gt;
&lt;p&gt;
Mollom offers a feature to report submitted content as inappropriate which
allows end users to indicate that a piece of site content is objectionable or
out of place. When reporting content, the content title is not sufficiently
sanitized to prevent cross-site scripting (XSS) attacks.
&lt;/p&gt;
&lt;p&gt;
This vulnerability is mitigated by the fact that an attacker must have a role
with the permission to create content and the content type must be enabled
for "Flag as Inappropriate" within the Mollom advanced configuration settings
(which is not the default setting).
&lt;/p&gt;
&lt;hr /&gt;
&lt;hr /&gt;
&lt;ul&gt;&lt;li&gt;/A CVE identifier &lt;a class="missing changeset" title="No default repository defined"&gt;[3]&lt;/a&gt; will be requested, and added upon issuance, in
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
accordance
with Drupal Security Team processes./
&lt;/p&gt;
&lt;hr /&gt;
&lt;hr /&gt;
&lt;ul&gt;&lt;li&gt;Mollom 6.x-2.x versions from 6.x-2.7 to 6.x-2.10
&lt;/li&gt;&lt;li&gt;Mollom 7.x-2.x versions from 7.x-2.9 to 7.x-2.10
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
Drupal core is not affected. If you do not use the contributed Mollom &lt;a class="missing changeset" title="No default repository defined"&gt;[4]&lt;/a&gt;
module,
there is nothing you need to do.
&lt;/p&gt;
&lt;hr /&gt;
&lt;hr /&gt;
&lt;p&gt;
Install the latest version:
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;If you use the Mollom module for Drupal 6.x, upgrade to Mollom 6.x-2.11
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[5]&lt;/a&gt;
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;If you use the Mollom module for Drupal 7.x, upgrade to Mollom 7.x-2.11
&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[6]&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Also see the Mollom &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;Matt Vance &lt;a class="missing changeset" title="No default repository defined"&gt;[8]&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;hr /&gt;
&lt;hr /&gt;
&lt;ul&gt;&lt;li&gt;Lisa Backer &lt;a class="missing changeset" title="No default repository defined"&gt;[9]&lt;/a&gt; the module maintainer
&lt;/li&gt;&lt;li&gt;Matt Vance &lt;a class="missing changeset" title="No default repository defined"&gt;[10]&lt;/a&gt;
&lt;/li&gt;&lt;/ul&gt;&lt;hr /&gt;
&lt;hr /&gt;
&lt;ul&gt;&lt;li&gt;Greg Knaddison &lt;a class="missing changeset" title="No default repository defined"&gt;[11]&lt;/a&gt; of the Drupal Security Team
&lt;/li&gt;&lt;/ul&gt;&lt;hr /&gt;
&lt;hr /&gt;
&lt;p&gt;
The Drupal security team can be reached at security at drupal.org or via the
contact form at &lt;a class="ext-link" href="https://www.drupal.org/contact"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/contact&lt;/a&gt; &lt;a class="missing changeset" title="No default repository defined"&gt;[12]&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
Learn more about the Drupal Security team and their policies &lt;a class="missing changeset" title="No default repository defined"&gt;[13]&lt;/a&gt;,
writing secure code for Drupal &lt;a class="missing changeset" title="No default repository defined"&gt;[14]&lt;/a&gt;, and
securing your site &lt;a class="missing changeset" title="No default repository defined"&gt;[15]&lt;/a&gt;.
&lt;/p&gt;
&lt;p&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[1]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/project/mollom"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/project/mollom&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[2]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/security-team/risk-levels"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/security-team/risk-levels&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[3]&lt;/a&gt; &lt;a class="ext-link" href="http://cve.mitre.org/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://cve.mitre.org/&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[4]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/project/mollom"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/project/mollom&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[5]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/node/2338787"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/node/2338787&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[6]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/node/2338789"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/node/2338789&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[7]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/project/mollom"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/project/mollom&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/88338"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/88338&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/1951462"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/1951462&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/88338"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/88338&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[11]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/user/36762"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/user/36762&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[12]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/contact"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/contact&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[13]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/security-team"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/security-team&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[14]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/writing-secure-code"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/writing-secure-code&lt;/a&gt;
&lt;a class="missing changeset" title="No default repository defined"&gt;[15]&lt;/a&gt; &lt;a class="ext-link" href="https://www.drupal.org/security/secure-configuration"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.drupal.org/security/secure-configuration&lt;/a&gt;
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/789#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/761</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/761</guid>
        <title>#761: Spam account cull</title>
        <pubDate>Thu, 17 Jul 2014 08:45:33 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
There are bucketloads of spam accounts swamping us. Spam commeting is swarming again. I just did several pages of deleting spam accounts.  No doubt I nailed some humans too (sorry Sam if this comes back to you); but the overwhelming majority of new accounts are spam.
&lt;/p&gt;
&lt;p&gt;
It's crap and we need to have another spam sweep - especially if we're staying in D6 for a while.
&lt;/p&gt;
&lt;p&gt;
See work done in Feb 2013: &lt;a class="assigned ticket" href="http://localhost:8080/trac/ticket/461" title="enhancement: Spam account war (assigned)"&gt;#461&lt;/a&gt;
See wiki page done in Feb 2013: &lt;a class="ext-link" href="https://wiki.transitionnetwork.org/Spam_accounts"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://wiki.transitionnetwork.org/Spam_accounts&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
SAM I'm going to suggest you start looking at it, and get your head around it, and the various modules and processes we've got running, then ask you to act/escalate accordingly.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/761#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/741</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/741</guid>
        <title>#741: Views editor disappears in backend</title>
        <pubDate>Thu, 12 Jun 2014 10:42:13 GMT</pubDate>
        
        <dc:creator>annesley</dc:creator>

        <description>&lt;p&gt;
admin &amp;gt; views &amp;gt; edit
the view editor interface appears and then disappears immediately
this happens in Chrome / Ubuntu and Firefox / Mac
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/741#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/731</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/731</guid>
        <title>#731: Meetings in maintenance</title>
        <pubDate>Fri, 23 May 2014 10:47:39 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

        <description>&lt;p&gt;
Ticket to record time spent on Skype call on 22nd May 2014.
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/731#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/715</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/715</guid>
        <title>#715: Views admin pages not visible.</title>
        <pubDate>Tue, 08 Apr 2014 14:51:29 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi I just tried to access the views admin interface here: &lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/build/views"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/build/views&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
It doesn't load the views admin pages, just an overview of the 'site building' pages instead.
&lt;/p&gt;
&lt;p&gt;
The page works as I expect it to on the stage site here: &lt;a class="ext-link" href="https://stg2.transitionnetwork.org/admin/build/views"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://stg2.transitionnetwork.org/admin/build/views&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
I have checked and the module is still enabled, The permissions look right (site admin is allowed to administer views: &lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/user/permissions"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/user/permissions&lt;/a&gt;)
&lt;/p&gt;
&lt;p&gt;
Anyone got an idea whats going on?
&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/715#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/661</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/661</guid>
        <title>#661: Add button block to homepage RHS: Send us your news stories</title>
        <pubDate>Tue, 17 Dec 2013 15:34:53 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
January:
&lt;/p&gt;
&lt;p&gt;
Create button for TN homepage and /news and /blogs to encourage people to send in stories.
&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;create button like the existing ones - e.g:
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
&lt;a class="ext-link" href="https://www.transitionnetwork.org/admin/build/block/configure/block/89?destination=newhome"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/admin/build/block/configure/block/89?destination=newhome&lt;/a&gt;
&lt;/p&gt;
&lt;ol start="2"&gt;&lt;li&gt;add suitably pithy text
&lt;/li&gt;&lt;/ol&gt;&lt;ol start="3"&gt;&lt;li&gt;if in doubt about style, read Ben's style cheatsheet on google docs:
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
&lt;a class="ext-link" href="https://docs.google.com/document/d/1z6JYGiy8EJ6pqjm_WyNUS26fQgIClmIFg0a-8y-Mots/edit#heading=h.siua52eim2e9"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://docs.google.com/document/d/1z6JYGiy8EJ6pqjm_WyNUS26fQgIClmIFg0a-8y-Mots/edit#heading=h.siua52eim2e9&lt;/a&gt;
&lt;/p&gt;
&lt;ol start="4"&gt;&lt;li&gt;this will need to be an email forwarder to send to Rob instead of a http link as per the other buttons, so you'll need to set one up on United's dashboard using the main 'jmcgeechan' account
&lt;/li&gt;&lt;/ol&gt;&lt;p&gt;
cc-ing benj as he can be around to help with postitioning/button make if an issue - but can't do email forwarder set up - and don't forget sam - if you're too busy you can always farm it out to ben (although this is probably a bit easy for ben, he'll know about how to get blocks in the right order)
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/661#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/606</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/606</guid>
        <title>#606: Site upgrade tasks -- pre-migration cleanup</title>
        <pubDate>Fri, 11 Oct 2013 12:00:13 GMT</pubDate>
        
        <dc:creator>jim</dc:creator>

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

        <description>&lt;p&gt;
User forwarded newsletter to themself (other email account) and was sent the wrong message - from a different user to someone else. See forwarded mail below.
&lt;/p&gt;
&lt;p&gt;
Please consider.
&lt;/p&gt;
&lt;hr /&gt;
&lt;p&gt;
From: Jeanne &amp;lt;mackeyj@…&amp;gt;
Date: Mon, Sep 9, 2013 at 11:57 AM
Subject: Jeanne is forwarding an email to you
To: jeano &amp;lt;jmackey50@…&amp;gt;
&lt;/p&gt;
&lt;p&gt;
Hi Will Sutherland,
&lt;/p&gt;
&lt;p&gt;
Kathleen L thought you'd be interested in this:
&lt;a class="ext-link" href="http://us1.forward-to-friend2.com/forward/show?u=766036b57dc1247e2964584bd&amp;amp;id=7b4f6d65d1"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://us1.forward-to-friend2.com/forward/show?u=766036b57dc1247e2964584bd&amp;amp;id=7b4f6d65d1&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Kathleen L also included this personal message to you:
&lt;/p&gt;
&lt;p&gt;
more info for ya about Transition Towns - made me think of your game with their new book and ingredients and stuff - read about it...
Did you find the link interesting?
&lt;/p&gt;
&lt;p&gt;
You can forward it on to your friends, too:
&lt;a class="ext-link" href="http://us1.forward-to-friend2.com/forward?u=766036b57dc1247e2964584bd&amp;amp;id=7b4f6d65d1"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://us1.forward-to-friend2.com/forward?u=766036b57dc1247e2964584bd&amp;amp;id=7b4f6d65d1&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
You can subscribe for more emails at:
&lt;a class="ext-link" href="http://transitionnetwork.us1.list-manage1.com/subscribe?u=766036b57dc1247e2964584bd&amp;amp;id=33e8648c8d"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;http://transitionnetwork.us1.list-manage1.com/subscribe?u=766036b57dc1247e2964584bd&amp;amp;id=33e8648c8d&lt;/a&gt;
&lt;/p&gt;
&lt;ul&gt;&lt;li&gt;Note: if any of the URLs above are not clickable, you can copy/paste them into your web browser.
&lt;/li&gt;&lt;/ul&gt;</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/603#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/521</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/521</guid>
        <title>#521: MySQL Unsafe statement warnings in the daemon.log</title>
        <pubDate>Sat, 16 Mar 2013 09:46:57 GMT</pubDate>
        
        <dc:creator>chris</dc:creator>

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

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

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

        <description>&lt;p&gt;
User reported: "I'm trying to register our fledgling initiative based in Dovje-Mojstrana, Slovenia. When I select the country, the &lt;a class="missing wiki"&gt;Province/State?&lt;/a&gt; box automatically comes up as not listed. But then when I press preview to be ready to send, it says "The specified province was not found in the specified country." So I can't submit the form :-(
Please help! I think we will be the first official Transition town in Slovenia!"
&lt;/p&gt;
&lt;p&gt;
I had a go at creating the initiative in a different country, then editing it to Slovenia as a workaround, but that didn't work either:
&lt;a class="ext-link" href="https://www.transitionnetwork.org/node/37435/edit"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/node/37435/edit&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Any idea's as to why it won't accept 'not listed' as a valid choice? Or what we can do 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/802#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/712</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/712</guid>
        <title>#712: Create a new stgX.transitionnetwork.org site</title>
        <pubDate>Tue, 01 Apr 2014 15:03:53 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi Paul
&lt;/p&gt;
&lt;p&gt;
I have been trying to build a staging site using your Github repository with the changes you made for ticket : &lt;a class="ext-link" href="https://trac.transitionnetwork.org/trac/ticket/693"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://trac.transitionnetwork.org/trac/ticket/693&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
I have edited the D6 s008 platform: &lt;a class="ext-link" href="https://tn.puffin.webarch.net/node/1157/edit"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://tn.puffin.webarch.net/node/1157/edit&lt;/a&gt; to use your makefile.
&lt;/p&gt;
&lt;p&gt;
It builds a site, but I just get an empty pressflow site at the end.
&lt;/p&gt;
&lt;p&gt;
Could you build a staging site using your makefile?
&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/712#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/681</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/681</guid>
        <title>#681: Submitting Transition event overseas: An illegal choice has been detected. Please contact the site administrator.</title>
        <pubDate>Wed, 22 Jan 2014 12:31:29 GMT</pubDate>
        
        <dc:creator>sam</dc:creator>

        <description>&lt;p&gt;
Hi I'm using &lt;a class="ext-link" href="https://www.transitionnetwork.org/node/add/event"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;https://www.transitionnetwork.org/node/add/event&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
To create a Transition Training event in Belgium in the 'Limburg' region.
&lt;/p&gt;
&lt;p&gt;
On submission I get the following error;
&lt;/p&gt;
&lt;p&gt;
"An illegal choice has been detected. Please contact the site administrator."
&lt;/p&gt;
&lt;p&gt;
It works for UK events.
&lt;/p&gt;
&lt;p&gt;
I had a look at the fields in the event content type, but couldn't spot any problems
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/681#changelog</comments>
    </item><item>
        <link>http://localhost:8080/trac/ticket/646</link>
        <guid isPermaLink="false">http://localhost:8080/trac/ticket/646</guid>
        <title>#646: Users denied access when trying to unsubscrbie</title>
        <pubDate>Thu, 12 Dec 2013 10:16:23 GMT</pubDate>
        
        <dc:creator>ed</dc:creator>

        <description>&lt;p&gt;
I'm getting noticeably more complaints about users not being able to unsubscribe to email notifications for content or comment alerts and/or the newsletter.
&lt;/p&gt;
&lt;p&gt;
The emerging pattern is that they are clicking on the unsubscribe link in their email alerts and going to an access denied page.
&lt;/p&gt;
&lt;p&gt;
My sense says there's something in https/http? Or them not being logged in?
&lt;/p&gt;
&lt;p&gt;
Something is definitely going on.
&lt;/p&gt;
&lt;p&gt;
Adding this to Sam to pick up in January. SAM - tickets like this can bounce around the tech team a bit - stay on it!
&lt;/p&gt;
</description>
        <category>Results</category>
        <comments>http://localhost:8080/trac/ticket/646#changelog</comments>
    </item>
 </channel>
</rss>