Transition Technology: Ticket Query

#676: Alternative to Skype for TTech Meetings

chris — Tue, 14 Jan 2014 13:33:51 GMT

Jim has pointed out that:

Skype costs us 15-30 minutes of grinding pain every time we do this!

So what are the alternatives and what are our requirements?

#881: Site on ParrotServer with a memory leak?

chris — Fri, 23 Oct 2015 11:19:04 GMT

It appears a site, or application, on ParrotServer might have a memory leak.

#814: Higher that usual loads on PuffinServer since early September

chris — Wed, 03 Dec 2014 17:12:35 GMT

The following load graph from PuffinServer shows that the load increased substantially in early September 2014, does anyone know why?

When I found I went to Drupal 7.33 and all I got was a slow site I thought that perhaps a Drupal 7 site on the server could be the cause but 7.33 came out on 7th November 2014.

Anyone have any ideas?

#898: Fwd: Access to Drupal

ade — Tue, 26 Jan 2016 17:35:05 GMT

Hi Chris,
The web team at the development agency are requesting access to the
webserver so that they can look at the sites make up.
(Please see below)
Would you please set up an account so that they can get root read access?
I guess this would be done via FTP, but your thoughts greatly appreciated.
best regards
Ade
---------- Forwarded message ----------
From: Ainslie Beattie <ainsliebeattie@transitionnetwork.org>
Date: 26 January 2016 at 17:25
Subject: Fwd: Access to Drupal
To: Sam Rossiter <samrossiter@transitionnetwork.org>, Ade Stuart <
adestuart@transitionnetwork.org>, Yvonne Struthers <yvonne@thisisyoke.com>
Hey both, can you please action this urgently so that Yoke can have access.
Cheers
---------- Forwarded message ----------
From: "Yvonne Struthers" <yvonne@thisisyoke.com>
Date: 26 Jan 2016 10:58
Subject: Access to Drupal
To: <ainsliebeattie@transitionnetwork.org>
Cc:
Hi Ainslie,
Just a quick email as I'm out seeing a client today,but just to say,it
looks like you have only given us access to the database. What we need
please is admin access to the Drupal site and to the code base so that we
can get a sense of how it's all set up.
Thanks in advance!
Yvonne
Sent from my iPhone
--
Ade Stuart
Web Manager - Transition network
07595 331877
The Transition Network is a registered charity
address: 43 Fore St, Totnes, Devon, TQ9 5HN, UK
website: www.transitionnetwork.org
TN company no: 6135675 TN charity no: 1128675

#655: Add social media icons with counters to blogs listings views

ed — Thu, 12 Dec 2013 13:03:11 GMT

Investigate with Rob how to add Social media icons with counters into the /blogs listings views and individual node views.

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

Sam to talk with Rob

Also cc-ing Ben as design - theme guy

#645: APC Tuning on Parrot and Penguin

chris — Tue, 10 Dec 2013 10:52:31 GMT

As part of the upgrade from Squeeze to Wheezy, see ticket:535, Munin graphs for APC were added:

There is also more APC info here:

The documentation for the variables which can be set in /etc/php5/mods-available/apc.ini can be found here:

http://php.net/manual/en/apc.configuration.php

This monitoring is generating quite a high volume of warnings about fragmentation and purges and this ticket has been created to try to sort this issue out.

#638: Question about notifications option for content creators

ed — Thu, 28 Nov 2013 12:32:57 GMT

Content creators (news, Rob's blog, social reporters) struggle with the notifications. the problem is that they forget to click the option to 'do not send notifications for this update' and then notifications are sent out. It is easy for us to think this is easy for them, but when you are bashing stuff out in a hurry, it's easy to forget this fiddly bit.

CAN WE set drupal to NOT send notifications out as standard for some of the content types?

And change it so that the content creators (news, Rob's blog, social reporters) choose to SEND notifications out instead (of NOT sending them) ?

#711: Emails & Telephone calls

paul — Tue, 01 Apr 2014 13:47:56 GMT

#596: Captions issue

benj — Mon, 16 Sep 2013 16:58:04 GMT

basically captions are appearing on body inline images and featured images on STG but not PROD and I can't see where the difference is...

The following code addition to the bottom of template.php should be (but isn't) adding the caption class to images such as the one at the top of this page:

https://www.transitionnetwork.org/blogs/ed-mitchell/2013-06/test-blog-test-caption-and-featured-image

Any reason you can think of why not? Or do you know of another easy way of adding the class caption to featured image fields? (I guess the module https://drupal.org/project/semantic_cck - but maybe overkill...)

Adds caption css class to featured images */

function transition2_imagecache_formatter_featured_image_default($element) {

Inside a view $element may contain NULL data. In that case, just return. if (empty($element#item fid?)) {

return ;

}

Extract the preset name from the formatter name. $presetname = substr($element#formatter, 0, strrpos($element#formatter, '_')); $style = 'linked'; $style = 'default';

$item = $element#item; $itemdata?alt? = isset($itemdata?alt?) ? $itemdata?alt? : ; $itemdata?title? = isset($itemdata?title?) ? $itemdata?title? : NULL;

$class = "imagecache imagecache-$presetname imagecache-$style imagecache-{$element#formatter} caption"; return theme('imagecache', $presetname, $itemfilepath?, $itemdata?alt?, $itemdata?title?, array('class' => $class));

}

#727: Change background on block from orange to white

sam — Fri, 16 May 2014 10:02:17 GMT

Hi Ben

Rob wants a list of the themes presented in a block.

I did the block: https://www.transitionnetwork.org/admin/build/block/configure/block/97

But it appears with an orange background. The block is visible towards the bottom of the page (for logged in admins) here: https://www.transitionnetwork.org/blogs/rob-hopkins

If I put the block on other pages it appears with a white background.

I tried to hack it with some inline CSS but failed.

Could you take a look?

Thanks

Sam

#541: Documentation of the WordPress sites

chris — Wed, 01 May 2013 20:25:57 GMT

These pages have been created for the documentation of the wiki:WordPress sites running on wiki:PenguinServer:

So far they only have a listing on the plugins for each site.

Ideally they would document all the plugins, the theme and the steps that need to be taken to upgrade each site and also any other things that need documenting.

Laura is this something you might be able to help with? I'm happy doing some work on it but you know your way around these sites far better than anyone else.

#587: Puffin MySQL Tuning

chris — Thu, 05 Sep 2013 12:54:47 GMT

This ticket is to track the tuning we do to MySQL on PuffinServer.

See also previous comments on this issue:

#737: SPF / Emails rejected from the website contact form

sam — Thu, 05 Jun 2014 15:46:13 GMT

We had a user report that they could not send a message via our contact form:

"Yesterday I sent a message to you via the contact form on the website. But obviously something went wrong: for I got a failure notice saying my message could not be delivered. Therefore I'm sending it directly via email (see below) hoping that you're receiving my message this way."

<info@…>: host mx1.spamfiltering.com[72.249.150.158] said:

550 81.95.XX.XX is not allowed to send mail from gmx.de. Please see http://www.openspf.net/Why?scope=mfrom;identity=userXX@gmx.de;ip=81.95.XX.XX (in reply to end of DATA command)

(User details edited as this is publicly archived)

I'm not sure I quite understand what's going on here. Chris indicated in email that this would affect other users whose email provider has set this kind of SPF record.

Can we make an educated guess as to what proportion of email providers set this kind of SPF?

How many messages do we never get to see? Is it a problem? Or a small enough number of users that we just don't worry about it?

Thanks

Sam

#582: TN.org platform and sites

jim — Mon, 02 Sep 2013 09:30:02 GMT

The TN.org platform and Drupal site updates are to be tracked in this ticket.

Current PROD platform build = P009 Current STG platform build = S010

Updates pending:

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.

#590: Drupal performance improvements

jim — Fri, 06 Sep 2013 10:27:27 GMT

This ticket is to track the work and changes done within the Drupal sphere in relation to performance enhancements done since #585.

More information is needed and will come when ticket:586 New Relic Monitoring for BOA is completed.

I also note that many of these cleanup operations will also help make the move to D7 smoother and better.

Summary of actions and status

TODO

O) Stop making so many URL aliases for non-relevant pages, clean up url_alias table -- 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):

3,579 entries where src = node/%/feed
1,856 entries where src = user/%/contact
= 5,435 or ~11% of entries in url_alias

L) Review slow query log, explain queries, tweak as necessary/flag poorly behaving modules. 2-4 hours, high reward, low risk... Keep looking at the slow query log and adjust Drupal or find patches as necessary. ALSO related Reduce your server's resource usage by moving MySQL temporary directory to tmpfs... Have opened ticket for this: #591 for Chris.

Done

A) Remove spam taxonomy entries ~~1/2 hour, Low risk, low reward -- See item 8 below. A simple delete from taxo term table where length > 50 is worth doing IMHO, and nothing I saw that would be clobbered is not spam.~~

B) Try a Taxonomy Cleanup: 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.

D) Review Views caching ~~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.~~

F) Force blocks caches to cached appropriately (and be rendered/included only as needed) 1-2 hours, medium reward, low risk -- BOA packages the Block Cache Alter, 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.

H) Remove CustomError? module all together 1/2 hour, low risk, low reward -- We should take out the PHP code from the 403 section of CustomError? 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 CustomError? 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...

I) Re-enable block caching. 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&D mainly, perhaps with some hacking/patching - but I'd stop short of doing this if so.

K) Add & enable Views Lite Pager on big views. ~~1 hour, low risk, low reward -- Using this module stops a heavy count query on views with pagers -- recommended for large sites.~~

M) Take control of Cron, and maximise time pages are cached for. .25h, high reward, low risk -- Cron is wiping the page cache, so we need to install https://drupal.org/project/elysia_cron 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...

N) Replace Admin Menu 1.x with 3.x -- will happen when #590 occurs, marking complete here -- ~~5 mins, high reward, low risk -- done when #582 happens, could be the cause of some load spikes as it occasionally goes made and does 2000-5000 queries~~~~

#636: Changes to Space.transitionnetwork.org homepage to facilitate user registration

ed — Wed, 27 Nov 2013 17:30:19 GMT

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.

RTFM for OA as to OA best practice - this is billable time. Then leave notes about it in wiki for later developers.

The homepage needs editing to sort this out. Here are some first changes:

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@…)

The /spaces listings view shows the spaces that are publicly viewable, and there is a 'request group membership' button for each of them.

Can you make this into a registration form as well?

#662: Subscriptions' links in text emails breaking

ed — Tue, 17 Dec 2013 15:37:13 GMT

for January - to get Sam and Jim talking - in January

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?

Adding as Jim's ticket with Sam cc-ed

#701: Emails & Telephone calls

paul — Tue, 18 Mar 2014 09:38:24 GMT

#758: * Advisory ID: DRUPAL-SA-CORE-2014-003

paul — Wed, 16 Jul 2014 21:55:29 GMT

View online: https://www.drupal.org/SA-CORE-2014-003

Advisory ID: DRUPAL-SA-CORE-2014-003
Project: Drupal core [1]
Version: 6.x, 7.x
Date: 2014-July-16
Security risk: Critical [2]
Exploitable from: Remote
Vulnerability: Multiple vulnerabilities

Multiple vulnerabilities were fixed in the supported Drupal core versions 6 and 7.

.... Denial of service with malicious HTTP Host header (Base system - Drupal 6 and 7 - Critical)

Drupal core's multisite feature dynamically determines which configuration file to use based on the HTTP Host header.

The HTTP Host header validation does not sufficiently check maliciously-crafted header values, thereby exposing a denial of service vulnerability.

.... Access bypass (File module - Drupal 7 - Critical)

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.

This vulnerability is mitigated by the fact that the attacker must have permission to create or edit content with a file field.

Note: The Drupal 6 FileField? [3] module is affected by a similar issue (see SA-CONTRIB-2014-071 - FileField? - Access bypass [4]) 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.

.... Cross-site scripting (Form API option groups - Drupal 6 and 7 - Moderately critical)

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.

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.

.... Cross-site scripting (Ajax system - Drupal 7 - Moderately critical)

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.

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.

/A CVE identifier [5] will be requested, and added upon issuance, in

accordance with Drupal Security Team processes./

Drupal core 6.x versions prior to 6.32.
Drupal core 7.x versions prior to 7.29.

Install the latest version:

If you use Drupal 6.x, upgrade to Drupal core 6.32. [6]
If you use Drupal 7.x, upgrade to Drupal core 7.29. [7]

Also see the Drupal core [8] project page.

The denial of service vulnerability using malicious HTTP Host headers was

reported by Régis Leroy [9].

The access bypass vulnerability in the File module was reported by Ivan

Ch [10].

The cross-site scripting vulnerability with Form API option groups was

reported by Károly Négyesi [11].

The cross-site scripting vulnerability in the Ajax system was reported by

mani22test [12].

The denial of service vulnerability using malicious HTTP Host headers was

fixed by Régis Leroy [13], and by Klaus Purer [14] of the Drupal Security Team.

The access bypass vulnerability in the File module was fixed by Nate Haug

[15] and Ivan Ch [16], and by Drupal Security Team members David Rothstein [17], Heine Deelstra [18] and David Snopek [19].

The cross-site scripting vulnerability with Form API option groups was

fixed by Greg Knaddison [20] of the Drupal Security Team.

The cross-site scripting vulnerability in the Ajax system was fixed by

Neil Drumm [21] of the Drupal Security Team.

The Drupal Security Team [22]

The Drupal security team can be reached at security at drupal.org or via the contact form at http://drupal.org/contact [23].

Learn more about the Drupal Security team and their policies [24], writing secure code for Drupal [25], and securing your site [26].

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity [27]

_ Security-news mailing list Security-news@… Unsubscribe at https://lists.drupal.org/mailman/listinfo/security-news

#772: new TIs not appearing on staging until caches flushed

annesley — Tue, 05 Aug 2014 09:26:32 GMT

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?

#635: Transition Research Patterns WEBrick monitoring

chris — Wed, 27 Nov 2013 12:51:13 GMT

Tom noticed that the wiki:TransitionResearchWagn site was unavailable today. I restarted it following the notes. We could do with something being set up to check that is it running. When it is running it's task can be found like this:

ps -lA | grep "ruby1.8"
1 S  1003  1449     1  1  80   0 - 47153 -      ?        00:00:05 ruby1.8

#665: Wagn "Problem Loading Page" error

chris — Mon, 06 Jan 2014 14:02:00 GMT

Bug report from Tom:

I've encountered a problem when trying to set up new accounts: I get a 'Problem Loading Page' error when it tries to load http://localhost:3000/wagn/Invite_Success. This seems to be explained at http://wagn.org/Special_Urls_and_Ports - which I am hoping falls under your area of responsibility as I'm not sure how to do it myself,! But let me know if not...

#668: Wagn transition_mod

chris — Sat, 11 Jan 2014 08:52:25 GMT

Email from Ethan via Tom:

I was doing some work on wagn mods today and I realized that I'd created a mod (as in "modification" or "module", whichever you like) for the transition site that probably never survived the move to the new server.

Looking at https://patterns.transitionresearchnetwork.org/Building_Resilience confirmed this for me. The confidence shows up as the words "2 stars" rather than actual star images. That's one thing the mod does. The other has to do with reducing visual redundancy (recurring names) in pattern summaries.

I've attached the mod file here. Unless you've gotten creative with your configuration, you should be able to stick this file in local/mods and restart the server and have that fixed. Let me know if any of this doesn't make sense.

#691: Upgrade Wagn hosting for patterns site

chris — Fri, 21 Feb 2014 16:53:43 GMT

The http://patterns.transitionresearchnetwork.org/ site is running using a development set up and the webrick server falls over every now and then, so the plan is to upgrade to a production style setup.

References:

ticket:635 webrick server problems
wiki:TransitionResearchWagn documentation
ticket:561 the last install
http://wagn.org/installation

#553: Invalid response from server ERROR message

ed — Tue, 28 May 2013 15:13:43 GMT

Trying to add a user. Get error message: "Received an Invalid response from the server" then served a blank screen. Same with project profile:

https://www.transitionnetwork.org/admin/user/user/create https://www.transitionnetwork.org/node/add/project-profile

This has also happened for a user trying to add a project.

Ed can add an event and blog post, ingredient, panel page.

#560: Install drupal-based project management system onto our servers

ed — Tue, 11 Jun 2013 17:00:28 GMT

Please can you install a suitable project management drupal-based tool onto the suitable server? I am thinking of Open Atrium. It's for staff and partners to use for management stuff (ie not a ticketing system or mediawiki).

Open Atrium?

Can you let me know how long it would take to install to a point where I can manage it and get a pilot project up and running?

#562: Users being subscribed to widgets newsletter on registratoin

ed — Mon, 17 Jun 2013 15:11:22 GMT

Ed added new users to system via user-->add user. They are being automatically subscribed to the widget owners newsletter. Please investigate and stop this.

#565: Blogs breadcrumbs incorrect on listings views

ed — Tue, 25 Jun 2013 13:21:56 GMT

Blogs breadcrumbs are wrong at main all blogs view and one author's full list view: https://www.transitionnetwork.org/blog https://www.transitionnetwork.org/blogs/ed-mitchell

Jim can you sort this in under 15 minutes (which is what you have left)

#566: Profile photo does not work

ed — Wed, 26 Jun 2013 14:17:35 GMT

Using this user account: https://www.transitionnetwork.org/users/patricia-benson https://www.transitionnetwork.org/people/patricia-benson

I can't get the photo to sit correctly. I have already deleted her first user account as the first photo she put in was sideways - the system presented that the right size, but sideways. Then I couldn't get the system to forget the original photo so had to delete the account and start again. Now I've tried adding bigger, smaller pictures and they all come out far too big - the system is enlarging them up to wider than the space alloted.

Very odd. Too tired and busy to do this now - will revisit in July after holiday.

#579: Special email alert for Rob Hopkins blog posts on TN.org

ed — Mon, 12 Aug 2013 13:49:30 GMT

Can we create a specific email alert for new blog posts from Rob Hopkins' blog (/blogs/rob-hopkins)?
Can Ed do this?
See below:

Proposed new alert: ~

From: [Rob Hopkins at Transition Network <site@…>] Subject: New blog post from Rob Hopkins' Transition Culture To: [subscriber email] Reply to: [<site@…>]

Hello. I've written a new blog Transition Culture blog post

You can read it and leave comments here: [LINK]

[BLOG POST TITLE] [LINE BREAK - FULL CLEAR LINE] [BLOG POST TEASER] [LINE BREAK - FULL CLEAR LINE]

Best regards, Rob

-- [TN EMAIL SUBSCRIPTION AUTO-BLURB] This is an automatic message from Transition Network To manage your subscriptions, browse to http://www.transitionnetwork.org/user/285/notifications You can unsubscribe at http://www.transitionnetwork.org/notifications/unsubscribe/subscription/...

#600: Numbers missing from Initiatives search page

ed — Mon, 30 Sep 2013 11:46:20 GMT

When users do a search on /initiatives we are missing a number which pertains to the results of the report:

It should say "XXX initiatives match your search criteria"

The XXX bit is missing

please check and resolve

#601: TTech Meeting 3rd October 2013

chris — Thu, 03 Oct 2013 09:03:42 GMT

This is a ticket for notes and times for the online meeting held on 3rd October 2013.

The ticket for the last meeting is ticket:585

#607: Getting three copies of stats reports

ed — Mon, 14 Oct 2013 08:27:59 GMT

I'm getting three copies of the stats reports (weekly) that I've set up here: https://stats.transitionnetwork.org/index.php?module=PDFReports&action=index&idSite=1&period=day&date=today

Please investigate

#609: Videos not showing if added via video link

ed — Tue, 15 Oct 2013 08:33:43 GMT

e.g. of project profile: https://www.transitionnetwork.org/projects/new-forest-transition-school-community-energy-saving-project

none showing on video page: https://www.transitionnetwork.org/video

#630: Archiving Transition Town Totnes site

ed — Mon, 25 Nov 2013 11:54:35 GMT

Please estimate to archive TTT site as per conversation with Ed:

convert to html
host on Penguin (incl. any likely issues for Penguin doing this)
any ongoing maintenance

Then Ed will discuss with Frances at TTT as per agreement with Chris

#643: Add paginator for /films view

ed — Mon, 09 Dec 2013 11:40:08 GMT

Please add pages links for this view: https://www.transitionnetwork.org/admin/build/views/edit/Films?destination=films#views-tab-page_1

10 per page should do it

#684: Adding Paul and Nick to Transition Network on github.org

chris — Thu, 23 Jan 2014 10:42:23 GMT

It looks like Ed and Jim are the only one with permissions to add members to Transition Network on GitHub as they are listed as owners and the rest of us are members.

Paul and Nick can you post you account names to this ticket so you can be added?

Jim could you make me and/or Ben owners as well so we can add people?

#705: Create a contents page on TransitionCulture.org Wordpress site

ed — Wed, 26 Mar 2014 15:33:43 GMT

Create a contents page on TC.org to see a listing of all the blog posts. Mike suggests: "use category post list widget to pull in the titles and then use widgetise pages to add widget to a standard page.:

Sam to follow up. MAX time: 1 hour.

#728: Re-patch location module

sam — Tue, 20 May 2014 12:53:16 GMT

Bugger just realised that I didn't finish the pull request into the main branch: https://trac.transitionnetwork.org/trac/ticket/681

So the location module patch is not on the live site.

I have now done the patch correctly I think: https://github.com/transitionnetwork/transitionnetwork.org-d6.profile/pull/2

Shall I additionally add the patch to the live site using Drush as I did before?

Thanks

Sam

#744: Add CSS Injector module to the D6 mix

annesley — Thu, 19 Jun 2014 10:50:03 GMT

CSS Injector module allows admin dynamic adding of CSS in to a live production server without code updates. this is to respond quickly to client needs whilst implementing the requests in the correct place in the themes on the next promotion from dev.

#803: Adding a CNAME value to TN.org zone files

ed — Mon, 27 Oct 2014 16:14:09 GMT

I need to add a CNAME value to verify transitionnetwork.org for google apps.

Can I do this on my own using the zone files in gandi or is it better that you do it Chris?

The value will be automatically generated as part of the verification process for setting the apps up, so I'll need to add it promptly

https://support.google.com/a/answer/60216

#815: Security updates need to be applied for a couple of contributed modules:

paul — Tue, 16 Dec 2014 13:45:16 GMT

DBTNG Hierarchical Select

#826: Switching MX records from United to Google

ed — Thu, 15 Jan 2015 17:15:41 GMT

TN are switching the MX records from United to Google on Friday 23/1/15.

Will this affect the website/Web Architects in any way that we need to plan for in advance? Scripts, web forms etc? Anything you can think of?

#852: TN site down

sam — Fri, 15 May 2015 18:23:38 GMT

Hi all

According to pingdom and testing in my browser TN is currently unavailable.

Is anyone around over the weekend to take a look?

Thanks

Sam

#494: Email account for TRAC

ed — Thu, 21 Feb 2013 10:16:37 GMT

Set up: 'trac@…' Password: going to Chris separately Secure SSL/TLS Settings Username: trac@… Password: Use the email account’s password. Incoming Server: mail.xssl.net IMAP: Port 993 POP3: Port 995 Outgoing Server: mail.xssl.net SMTP: Port 465 Authentication is required for IMAP, POP3, and SMTP.

#534: Add accounts for Ben

chris — Fri, 26 Apr 2013 17:16:23 GMT

Ben is a new member of the TTech team and accounts need setting up for him, this is a ticket to track the time taken to do this.

#546: Trac documentation

chris — Wed, 08 May 2013 18:47:09 GMT

Better documentation of things like how to set billing times etc

#597: Default owner for tickets

chris — Tue, 17 Sep 2013 08:04:58 GMT

Ben reported that the default owner for tickets is laura and that this should be changed.

#611: Adding Trac Account for Alan

chris — Thu, 17 Oct 2013 12:55:21 GMT

Alan, the other sysadmin at Webarchitects is in a better position than me to help with some of the more complex sysadmin issues so I hope it's OK that I have added an account for him here following the wiki:TracUserAdmin notes.

He is looking at helping with these tickets:

ticket:599 Server time drift
ticket:555 Load spikes causing the TN site to be stopped for 15 min at a time
ticket:593 Migrating Puffin to a ZFS file server

I don't expect he will be recording much time, I hope that is OK, he already has sudo access to all the servers.

#642: Trac "databasee is locked" errors in /var/log/messages

chris — Sat, 07 Dec 2013 13:46:43 GMT

I have just noticed these errors in /var/log/messages on wiki:PenguinServer:

Dec  1 23:09:00 penguin <11>Trac[chrome] ERROR: Error with navigation contributor TimingEstimationAndBillingPage: OperattionalError: database is locked
Dec  1 23:09:00 penguin <11>Trac[chrome] ERROR: Error with navigation contributor AdminModule: OperationalError: databasse is locked
Dec  1 23:09:00 penguin <11>Trac[chrome] ERROR: Error with navigation contributor SearchModule: OperationalError: databaase is locked
Dec  1 23:09:00 penguin <11>Trac[chrome] ERROR: Error with navigation contributor QueryModule: OperationalError: databasse is locked
Dec  1 23:09:00 penguin <11>Trac[chrome] ERROR: Error with navigation contributor ReportModule: OperationalError: databaase is locked
Dec  1 23:09:00 penguin <11>Trac[chrome] ERROR: Error with navigation contributor RoadmapModule: OperationalError: databbase is locked
Dec  1 23:09:00 penguin <11>Trac[chrome] ERROR: Error with navigation contributor TicketModule: OperationalError: databaase is locked
Dec  1 23:09:00 penguin <11>Trac[chrome] ERROR: Error with navigation contributor TimelineModule: OperationalError: dataabase is locked
Dec  1 23:09:00 penguin <11>Trac[chrome] ERROR: Error with navigation contributor BrowserModule: OperationalError: databbase is locked
Dec  1 23:09:00 penguin <11>Trac[chrome] ERROR: Error with navigation contributor WikiModule: OperationalError: databaseeis locked

There are lots more of these, including some from this morning.

Trac still seems to be working OK so I don't know how significant they are.

#682: Create Trac & Wiki account for Paul

sam — Wed, 22 Jan 2014 12:39:18 GMT

Hi it looks like i@… will be joining us to pick up some of Jim's role as he moves on.

Chris could you create a trac & Wiki account for him please?

His email is; i@…

Thanks

Sam

#822: Create TRAC id for Ade

ed — Wed, 07 Jan 2015 09:54:13 GMT

name: ade email: adestuart@…

#842: Trac fetchmail

chris — Thu, 02 Apr 2015 12:54:11 GMT

There is a new SSL/TLS certificate at mail.webarch.net so these steps need following: wiki:TransitionTrac#Fetchmail

#572: Design changes for homepage and TC section

ed — Wed, 17 Jul 2013 14:17:25 GMT

Design changes for TN homepage and TC section done by Ben to be part of maintenance budget.

list here: https://docs.google.com/spreadsheet/ccc?key=0An7ZaZdq6UfJdDhxS0JxbXZLYnhLRkN4X3h5aVV3R1E#gid=0

#592: Many panes on homepage are in italics

ed — Wed, 11 Sep 2013 07:29:50 GMT

they shouldn't be, but they are: ingredient of the day latest tc post featured training why do transition featured resrouce featured project social reporters all automated listings at bottom

please resolve - ben are you around to do this or is it more suitable to ask jim atm?

#371: Piwik Hosting

chris — Mon, 05 Dec 2011 21:34:51 GMT

Another option to consider for Piwik would be be to use a instance on another server, and there happens to be one here that could be used:

https://stats.webarch.net/

Could this be considered?

#382: Measurement and tracking requirements for TN and PSE

ed — Tue, 13 Dec 2011 04:57:12 GMT

to list the measurement and tracking requirements for TN and PSE so that we can assess piwik vs google and decide which way to go.

#495: Replace Google Analytics with Piwki

ed — Thu, 21 Feb 2013 10:20:25 GMT

Unless we see any issue, turn GA off on 01/03/13. Use Piwik instead.

#556: Upgrade Piwik to version 1.12

chris — Thu, 30 May 2013 21:40:48 GMT

A new version of Piwik came out today with some interesting looking features:

#660: Piwik 2.0

chris — Tue, 17 Dec 2013 09:36:18 GMT

The new version of Piwik will be out soon, the Piwik 2.0 Release Candidate just came out.

This ticket has beed created to document the upgrade.

#664: Upgrade Piwik to 2.0.2

chris — Tue, 24 Dec 2013 14:35:06 GMT

This is a bugfix version which fixes 3 issues, see http://piwik.org/changelog/piwik-2-0-1/

Upgrade notes are here, wiki:PiwikServer#Updates

#672: Upgrade to Piwik 2.0.3

chris — Mon, 13 Jan 2014 10:13:00 GMT

From the Piwik changelog:

Piwik 2.0.3 is a bug-fix release. To ensure the highest quality and reliability for your Piwik 2.0 setup, we have fixed all known major bugs, as well as made some small improvements.

...

We highly recommend that you upgrade your server to Piwik 2.0.3 today to benefit from the latest improvements.

#697: Piwik 2.1 upgrade for stats.transitionnetwork.org

chris — Tue, 04 Mar 2014 07:37:11 GMT

Full details on the piwik blog:

Piwik 2.1 is the first release after our 2.0 release and it reflects the new direction Piwik is moving in: better performance, more reliability and a better overall open platform!

#720: Upgrade to Piwik 2.2.0

chris — Thu, 17 Apr 2014 07:51:50 GMT

From the Changelog, http://piwik.org/changelog/piwik-2-2-0/

Piwik 2.2.0 is a major new release. This release is rated critical. Please update now.

We highly recommend that you upgrade your server to Piwik 2.2.0 today to benefit from design, performance and security improvements in this release.

Piwik 2.2 helps you focus on your data

All reports: display as much text as possible before the label becomes truncated (useful when you want to see more data at a glance without having to hover to view the full label)
Make Datatables more readable and flatter – we have removed some borders.
On the dashboard, the Data Tables and graph icons are now hidden by default and are now available by clicking on the widget footer.
New features

Event Tracking: track your custom events with Piwik. An event is defined by a Category, an Action, an optional Name and an optional Value. Event Tracking is a powerful feature which can be used for many purposes! http://piwik.org/docs/event-tracking/
Site Search reports are now available in Scheduled email reports and on Piwik Mobile
New Websites Groups (available on request) functionality now allows you to group a cluster of websites in the All Websites Dashboard.
Security fixes: we would like to warmly thank Security researchers Mateusz Goik and Vivek S. Jadhav for responsibly reporting two XSS security issues in Piwik which are now fixed in 2.2.0.
API breaking change for Plugins developers
Deprecated the function Schema::dropTables() and DbHelper::dropTables, for the new Db::dropTables()
Removed the code that was deprecated in 2.1.0. Learn more http://piwik.org/blog/2014/02/piwik-2-1-changes-plugin-developers/

#726: Upgrade to Piwik 2.2.1

chris — Tue, 06 May 2014 11:14:05 GMT

Piwik 2.2.1 is a new minor release which brings more stability to the platform.

http://piwik.org/changelog/piwik-2-2-1/

#729: Upgrade to Piwik 2.2.2

chris — Fri, 23 May 2014 08:21:12 GMT

2.2.2 came out on 8th May, not sure why I missed this at the time, the change log is here: http://piwik.org/changelog/piwik-2-2-2/

The last upgrade was 2.2.1 ticket:726 and the upgrade notes are at wiki:PiwikServer#Updates

#732: Upgrade Piwik to 2.3.0

chris — Tue, 27 May 2014 09:21:24 GMT

Piwik 2.3.0 is a new major release of Piwik!

http://piwik.org/changelog/piwik-2-3-0/

#752: Piwik 2.4.0 Update

chris — Thu, 03 Jul 2014 09:24:13 GMT

Piwik 2.4.0 is a new major release of Piwik! This release is rated critical. Please update now.

Security fixes

We would like to warmly thank Security researchers Aron Molnar (XSEC infosec GmbH) for reporting a XSS vulnerability which we have fixed in 2.4.0. We also thank Andrea Palazzo and Jose Luis Zayas for their security recommendations which are now implemented in 2.4.0.

http://piwik.org/changelog/piwik-2-4-0/

#756: Piwik 2.4.1 Update

chris — Fri, 11 Jul 2014 13:21:34 GMT

From the Changelog:

Piwik 2.4.1 is a new minor release of Piwik fixing a few bugs found by the community after the major 2.4.0 release.

#776: Piwik 2.0.5

chris — Sat, 16 Aug 2014 07:55:49 GMT

New version of Piwik, not a security update so no urgent need to upgrade unless there is some new required feature:

http://piwik.org/changelog/piwik-2-5-0/

#782: Piwik 2.6.1

chris — Fri, 05 Sep 2014 07:15:03 GMT

New Piwik, changes: http://piwik.org/changelog/piwik-2-6-1/

#791: Piwik 2.7.0

chris — Thu, 25 Sep 2014 17:29:12 GMT

The changelog for 2.7.0 contains:

Piwik 2.7.0 is a new major release of Piwik!

What’s new in 2.7.0?

In this release we have packed several major new features and many small improvements. The new features in this release are: User ID, New Pivot Table feature for Events reports, new plugin to count users visiting several of your websites, new Content Tracking plugin, new Browser language Report listing the user language codes, and more (see below the list of all issues that were closed in this release).

63 tickets have been closed by 15 contributors!

Database upgrade

Note: This release contains major database upgrades and upgrading your database will take a long time if you have a lot of data in your database.
Exceptionally when you upgrade your Piwik to 2.7.0 you will run through the Upgrade screen twice (instead of only once as usual). If you use the command line you will have to execute the command ‘./console core:update’ twice. This is expected and normal behavior for this release.
-> Check out this CHANGELOG.md file (in the root of Piwik) to see all changes to the platform and APIs.

https://github.com/piwik/piwik/blob/master/CHANGELOG.md#piwik-platform-changelog

#796: Piwik 2.8.0

chris — Tue, 14 Oct 2014 09:20:54 GMT

Piwik 2.8.0 is a new major release of Piwik. In this release we have focused on reliability, usability and security. 57 tickets have been closed by 12 contributors!

This release is rated critical.

http://piwik.org/changelog/piwik-2-8-0/

#800: Piwik 2.8.1

chris — Wed, 22 Oct 2014 09:28:26 GMT

Piwik 2.8.1 is a new minor release of Piwik! In this release we have focused on reliability and bug fixing. 28 tickets have been closed by 7 contributors!

Security fixes

The Piwik team warmly thank security researcher Dingjie Yang for responsibly disclosing a XSS vulnerability occurring in older Internet Explorer browsers.

http://piwik.org/changelog/piwik-2-8-1/

#801: Piwik 2.8.3

chris — Thu, 23 Oct 2014 10:05:14 GMT

New version of Piwik today:

Piwik 2.8.3 is a new minor release of Piwik, fixing an issue discovered in Piwik 2.8.3. 2 tickets have been closed by 2 contributors!

http://piwik.org/changelog/piwik-2-8-3/

And yesterday:

Piwik 2.8.2 is a new minor release of Piwik, fixing an issue affecting some users of Nginx. 6 tickets have been closed by 5 contributors!

http://piwik.org/changelog/piwik-2-8-2/

#807: Piwik 2.9.0

chris — Fri, 14 Nov 2014 10:56:27 GMT

New version of Piwik:

Piwik 2.9.0 is a new major release of Piwik! In this release we have focused on reliability and stability. 58 tickets have been closed by more than 8 contributors!

http://piwik.org/changelog/piwik-2-9-0/

#810: Piwik 2.9.1

chris — Thu, 20 Nov 2014 14:58:20 GMT

From the changelog:

Piwik 2.9.1 is a new minor release of Piwik. In this release we have fixed a few minor issues reported in 2.9.0.

#817: Piwik 2.10.0

chris — Thu, 18 Dec 2014 11:40:50 GMT

From the changelog:

Note: Piwik 2.10.0 is not released yet – we expect a release around December 25th.

Piwik 2.10.0 is a new major release of Piwik! In this release we have focused on improving performance, adding several features to the Log Analytics tool and fixed dozens of bugs to improve your Piwik experience. Almost 100 issues were closed by 11 contributors!

#823: Pwiki 2014 annual report

chris — Wed, 07 Jan 2015 12:19:55 GMT

Ed would like a some PDF reports of Transition Network site usage for 2014 from Piwik.

#832: Piwik 2.11.0

chris — Wed, 18 Feb 2015 13:11:58 GMT

The Changelog for 2.11.0, which came out on February 16, 2015 contains:

Piwik 2.11.0 is a new major release of Piwik!

In this release we have focused on overall reliability, improved Performance, improved Accessibility for visually impaired users, and also we have re-organised the User and Admin Menus for hopefully a better experience. There are even some very interesting new features such as a new icon available in most reports (check it out and let us know what you think!).

128 tickets have been closed by more than 17 contributors, our record number of contributors in one release. Thank you to everyone who participated in this release by reporting or fixing a bug or a new feature.

#833: Piwik 2.11.1

chris — Mon, 23 Feb 2015 11:23:59 GMT

Out today, from the changelog:

Piwik 2.11.1 is a new minor release of Piwik. It is a follow up to last week’s major 2.11.0 release. It includes a few bug fixes, in particular a performance regression introduced in 2.11.0. 16 tickets have been closed by 5 contributors!

#835: Piwik 2.11.2

chris — Wed, 04 Mar 2015 09:59:13 GMT

From the changelog:

Piwik 2.11.2 is a new minor release of Piwik. In this release we have fixed a few issues that were reported in Piwik 2.11.0 and 2.11.1. 16 tickets have been closed by 8 contributors!

#838: Piwik 2.12.0

chris — Mon, 23 Mar 2015 10:14:04 GMT

From the Piwik 2.12.0 announcement:

Piwik 2.12.0 is a new major release of Piwik! In this release we have focused on security, performance, and data quality improvements.

What’s new?

Loading reports in the UI will be faster overall, as well as custom date range reports and archiving. There were improvements made in both memory and CPU usage.

When you create a new website in Piwik, it will now show instructions and display the Javascript Tracking code instead of the dashboard, as long as no data has been tracked.

There is a new data quality tool: a console command to geo-locate any past visits which don’t have geo-location data.

There are also important security improvements such as the one-click update which will now be done over secure connection HTTPS, or the fact that the token_auth will be removed from all of the log outputs.

If you use the “Make it flat” feature, you may have noticed it was slow on large datasets: from Piwik 2.12.0 the Flattened reports will now render quickly even on the largest datasets (“Make it flat” is available via the bottom right icon in most reports).

There are also several other bug fixes and improvements: 49 tickets have been closed by 7 contributors! (see the list of issues below)

#840: Piwik 2.12.1

chris — Tue, 31 Mar 2015 16:31:12 GMT

From the changelog:

Piwik 2.12.1 is a new minor release of Piwik, a follow up to 2.12.0 major release.

In this release we have focused on fixing a regression in the Visitor Log as well as other smaller fixes.

11 tickets have been closed by 5 contributors!

#848: Piwik 2.13.0

chris — Mon, 27 Apr 2015 09:56:54 GMT

From the Changelog:

We are proud to announce Piwik 2.13.0: a new major release of Piwik!

What’s new?

In this release we have focused on improving performance and making Piwik much faster at loading and archiving reports. The dashboard and All websites dashboard will load faster than ever before! This is especially visible if you measure many websites (hundreds of thousands) within your Piwik, the improved Websites Manager will now let you search for websites and page through the list, and the ‘All Websites’ dashboard will now load correctly.

Performance was not our only focus and we also improved the usability and design of some parts of Piwik (such as the Updater and maintenance mode, with more design updates coming in the next releases). Log Analytics, a very popular tool within the Piwik community, has received several improvements. Many other small bugs were closed, and a XSS security bug was reported and fixed in this release.

96 tickets have been closed by 8 contributors!

#850: Piwik 2.13.1

chris — Fri, 08 May 2015 10:25:43 GMT

The changelog:

Piwik 2.13.1, a new minor release of Piwik, has been released!

What’s new?

We are releasing 2.13.1 shortly after 2.13.0 to address a few small bugs that were reported by the community. This release also includes a Tracking API performance improvements as well as other minor improvements listed below.

#858: Piwik 2.13.1

chris — Fri, 05 Jun 2015 19:14:15 GMT

From the changelog:

Piwik 2.13.1, a new minor release of Piwik, has been released!

What’s new?

We are releasing 2.13.1 shortly after 2.13.0 to address a few small bugs that were reported by the community. This release also includes a Tracking API performance improvements as well as other minor improvements listed below.

13 tickets have been closed by 6 contributors!

#861: Piwik 2.14.0

chris — Wed, 24 Jun 2015 09:04:46 GMT

From the Changelog:

We are proud to announce Piwik 2.14.0: a new major release of Piwik!

What’s new?

[…]

More than 120 tickets have been closed by 13 contributors!

Security release

This release is rated critical.

Three security issues have been fixed. We are grateful for security researchers who responsibly disclosed these security issues to us: Abdullah Hussam Gazi (CSRF issue) and Dmitriy Shcherbatov (two XSS issues).

Database upgrade

This release does not contain any major database upgrade.

Platform Changes

Piwik is an open analytics platform. In an effort to help Piwik developers learn about improvements and changes in the core APIs, we document the changes since the last release.

In this 2.14.0 release there are breaking changes, New features, Library updates, New commmands.

#866: Piwik 2.14.1

chris — Fri, 17 Jul 2015 08:41:34 GMT

The changelog:

What’s new in Piwik 2.14.1?

In this release we have focused on fixing a few regressions reported in the last major release Piwik 2.14.0, as well as 27 other small improvements. As always we – the Piwik team – are very interested to hear your feedback!

27 tickets have been closed by 6 contributors.

#867: Piwik 2.14.2

chris — Mon, 27 Jul 2015 11:18:26 GMT

The Changelog:

What’s new in Piwik 2.14.2?

In this release we have focused on fixing a few regressions reported in the last major release Piwik 2.14.0, as well as 15 other small improvements. As always we – the Piwik team – are very interested to hear your feedback!

15 tickets have been closed by 6 contributors.

#869: Piwik 2.14.3

chris — Mon, 24 Aug 2015 12:00:58 GMT

The Piwik Changelog 2.14.3 contains:

Piwik 2.14.3 is a new minor release of Piwik.

What’s new?

This release addresses a regression introduced in 2.14.2 that prevents users from installing Piwik in some cases.

11 tickets have been closed by 5 contributors!

#880: Piwik 2.15.0

chris — Fri, 16 Oct 2015 09:04:00 GMT

The Piwik 2.15.0 changelog:

We are proud to announce Piwik 2.15.0 Release Candidate: a new major release of Piwik!

What’s new?

Piwik 2.15.0 is our Long Term Support release for Piwik 2.X. This release aims to be outstanding from a performance, security, and reliability point of view. It also includes a beautiful new design which lets you focus on your data, and a new awesome search bar to lets you easily navigate to any menu, website or segment in your Piwik dashboards. For administrators and power user, this release includes new diagnostic tools, logging messages, a new Log viewer plugin, and better overall performance and scalability. There are dozens other improvements, see the full list below. Piwik 2.15.0 is built to last.

Security release

This release is rated critical.

We are grateful for Security researchers who disclosed security issues privately to the Piwik Security Response team: Elamaran Venkatraman, Egidio Romano and Dmitriy Shcherbatov. The following vulnerabilities were fixed: XSS, CSRF, possible file inclusion in older PHP versions (low impact), possible Object Injection Vulnerability (low impact).

Database upgrade

This release does not contain any major database upgrade.

Platform Changes

Piwik is an open analytics platform. In an effort to help Piwik developers learn about improvements and changes in the core APIs, we document the changes since the last release.

In this 2.15.0 release there are API deprecations, New features, New APIs, New commmands, Internal API changes.

Read more in Platform Changelog for Developers to see all changes to the platform and APIs (you can also find it in the CHANGELOG.md in the root of your Piwik)

#902: Piwik 2.16.0

chris — Sun, 07 Feb 2016 10:41:47 GMT

From the changelog:

What’s new?

Piwik 2.16.0 is a release which includes more than 250 closed issues. To learn about the most important and visible changes, read our blog post: What’s new in Piwik 2.16.0?

This release is our Long Term Support release.

263 tickets have been closed by more than 30 contributors!

#910: Piwik 2.16.1

chris — Tue, 12 Apr 2016 10:29:09 GMT

The changelog:

Security release

This release is rated critical.

#538: intransitionmovie.com checks and updates

chris — Tue, 30 Apr 2013 20:02:03 GMT

The http://www.intransitionmovie.com/ site has been migrated to wiki:ParrotServer, the DNS might not have yet updated for everybody.

Laura -- could you check that the site is working OK if you get a chance, especially the ecommerce elements?

There are some outstanding updates, WordPress is version 3.3.2 need updating to 3.5.1 and there are 12 plugins with updates available:

18 installed plugins:
 UA affiliates
 UA affiliates-woocommerce-light
 UA akismet
  A backupwordpress
 UI bad-behavior
 UA bwp-minify
  A contact-form-7
 UA event-o-matic
  A transposh-translation-filter-for-wordpress
 UA usernoise
  A woocommerce
 UA woocommerce-export-csv
  A woocommerce-currency-converter
 UA woocommerce-dynamic-pricing
  A woocommerce-delivery-notes
 UA woocommerce-shipping-table-rate
 UA wp-customer-reviews
 UI wp-super-cache
Legend: A = Active, I = Inactive, U = Update Available

I'm happy to do all these updates but I wouldn't know what exactly to check to see that the updates don't break anything -- would Laura be able to help with a quick check that updates haven't broken anything?

#539: REconomy site migration and updates

chris — Wed, 01 May 2013 10:01:00 GMT

This ticket is to keep track of the tasks undertaken and the time spent on the migration of the http://www.reconomy.org/ site to wiki:ParrotServer.

#542: Parrot RAM

chris — Wed, 01 May 2013 20:35:50 GMT

I'm concerned that wiki:ParrotServer might not be able to cope with load spikes due to it only having 1GB of RAM, these are the Munin graphs we need to key an eye on:

If the server runs out of RAM it will basically stop responding.

#550: Transition Town Totnes migration

chris — Sun, 19 May 2013 14:59:44 GMT

It has been agreed to migrate Transition Town Totnes, http://transitiontowntotnes.org/ to wiki:ParrotServer and this ticket has been created to record this process and the time spent on it and the documentation of the migration.

There is also an issue regarding what, if anything, to do with the old Drupal site at http://archive.transitiontowntotnes.org/

#577: Transition Streets Wordpress Migration

chris — Tue, 06 Aug 2013 21:28:25 GMT

This is a ticket to document the migration of the Transition Totnes http://www.transitionstreets.org.uk/ wiki:WordPress site to wiki:ParrotServer.

#583: tmp files on parrot exceeded inode limit

ed — Mon, 02 Sep 2013 12:28:46 GMT

Users are attempting to purchase a DVD and the cart always zeros out even after attempts to update cart etc.

Laura suggests that this may be a server issue and to start with Chris:

The prob could v likely be on the hosting side, so be worth contacting Chris first (and mention can add to cart all okay when logged in, view cart and alter and get to billing page, so could be a session setting that's changed) -

Does the server have disk space left on /tmp. Session data is most likely written there. (sometimes this cart faff issue can happen because of that.)

Are the PHP Session settings correct/ have they changed recently? Chris can fix this if needing a tweakette in php.ini or other places in the underworld of those types of files.

DB could potentially need check/repair.

Another one is the shop element relies on cookies so if a user has set browser to not accept cookies may poss not work! (but think thats something not to think about here, as I tested as both logged in and logged out with cookies set to work on my browser, logged out got the 'cart empty' faff factor like other users will be getting.)

If Chris can't spot the bug (does sound server side and sessions related from a quick test here, haven't looked at the server logs, but if get a mo later will see if I can), poss good to chat and I can think some more on it, but first thoughts alert me mostly to server side, sometimes a roll back to php 5.2 clicks things back into place (but shouldn't be needed). Be good to see if there is a correlation with any server changes/tweaks happening around same timing that the cart stopped working. Keep me in the loop if it is a server fix-y thing as always interested to hear results on bug fixing on sites.

#594: WordPress 3.6.1 Maintenance and Security Release

chris — Wed, 11 Sep 2013 22:05:01 GMT

The following is from http://wordpress.org/news/2013/09/wordpress-3-6-1/

WordPress 3.6.1 is also a security release for all previous WordPress versions and we strongly encourage you to update your sites immediately. It addresses three issues fixed by the WordPress security team:

Block unsafe PHP unserialization that could occur in limited situations and setups, which can lead to remote code execution. Reported by Tom Van Goethem.
Prevent a user with an Author role, using a specially crafted request, from being able to create a post “written by” another user. Reported by Anakorn Kyavatanakij.
Fix insufficient input validation that could result in redirecting or leading a user to another website. Reported by Dave Cummo, a Northrup Grumman subcontractor for the U.S. Centers for Disease Control and Prevention.
Additionally, we’ve adjusted security restrictions around file uploads to mitigate the potential for cross-site scripting.