Transition Technology: Ticket Query

#767: robots.txt on dev site

sam — Thu, 31 Jul 2014 11:07:39 GMT

Hi Paul

Could you fix the robots.txt here:

https://booker-stage-20140501.transitionnetwork.org/robots.txt

Sam

#100: Show users' profiles on their personal profile page

ed — Mon, 21 Jun 2010 16:36:55 GMT

show a list of the projects and intiatives that users are involved with on their personal profile page

#127: Link checker module

ed — Fri, 23 Jul 2010 09:12:15 GMT

It would be very very handy to have a link checker of some form to check for internal and external links. Site editors are adding pages, navigation is changing etc. If possible, the link module would update links as they move internally, but that's a nice to have. Please install one and Ed can manage it.

Putting to critical to get it on, shouldn't take long...

#461: Spam account war

ed — Wed, 21 Nov 2012 16:19:10 GMT

Aim:

tell drupal (and server level stuff?) to sniff out and destroy spam accounts without them knowing we did it, and ban them from doing it again

Wiki page:

https://wiki.transitionnetwork.org/Spam_accounts

#469: PSE project submission submitter cannot then edit their own project

ed — Tue, 04 Dec 2012 19:33:46 GMT

The user who has added a pse submission which has been approved cannot then edit the project profile when it has been approved. The webmaster who approved it can edit it.

This is not right - the user who added the pse submission which then got turned into a project needs to be the project owner.

The new project is set to the correct author. But that author doesn't have edit rights.

Project (unpublished): https://www.transitionnetwork.org/projects/test-user-3-test-project

#504: Images missing from widget and site in general

ed — Fri, 01 Mar 2013 16:00:39 GMT

Submit button missing from widget (see bottom right here: http://www.edmitchell.co.uk/blog/).

Quite a few images are missing from the site - profile pictures of people who don't have pictures as well.

Please have a look.

#514: Spam issues - users not being able to comment

ed — Tue, 12 Mar 2013 17:25:29 GMT

Ed is receiving a selection of users not being allowed to post since the spam changes. We are seeing a pattern now. Setting this ticket up - will add user details tomorrow.

#516: Search: not showing events or initiatives

ed — Thu, 14 Mar 2013 10:16:41 GMT

Search for Woking from homepage. I know that there are two events and two initaitives with Woking in them. Neither are shown: https://www.transitionnetwork.org/search/node/woking

Advanced search does not bring them up either (ticking the initiatives box).

If I am in the initiatives section it returns the TIs though.

General search used to show TIs and events. Now it's only showing results of word searches.

General search needs to show TIs and events, and other nodes.

Please look into this.

#517: News widgets not working

ed — Thu, 14 Mar 2013 12:39:57 GMT

News widgets not working - noticed here: http://transitionfinsburypark.org.uk/

and here: http://wwww.edmitchell.co.uk

Checked by putting code from http://www.transitionnetwork.org/syndication-and-social-media into new widget - showing a blank.

News feed working here: http://www.transitionnetwork.org/news/feed

So must be widget code.

Adding to Jim, but is it Laura?

#606: Site upgrade tasks -- pre-migration cleanup

jim — Fri, 11 Oct 2013 12:00:13 GMT

This ticket is to track the issues left over from #590 that need to be considered and tackled prior to migrating the site from D6 to D7 (or 8).

Please feel free to add as needed, but sticky to the

C) Cleanup: List of features we don't really need

Ed to add his items to following list... Need rational and alternative approaches for each.

C.1) Remove 'Geographic region' and related taxonomy and Hierarchical Select modules 1 hour, low reward, low risk -- never really been used and is effectively a duplicate of the location field. let's kill it!
C.2) Kill Microsites and the Forums -- The handful of people using the CMS feature should be migrated to Open Atrium if they need such features.
C.3) Remove forums -- 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.

D) Key development tasks

D.1) All inline PHP must be moved to modules and features -- This has great benefit for management, maintenance and developers. Eval()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: http://2bits.com/api/abuse-drupal-best-practices-your-own-peril-poor-performance.html and http://2bits.com/articles/free-your-content-php-moving-php-code-out-blocks-views-and-nodes.html

D.2) Build in ESI (Edge Side Includes) support from the outset, ensure Drupal renders only what it needs to -- BOA packages the ESI (Edge Side Includes integration) module, 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 comments in 4 & 5 below for discussion~~, should be done after proposal F, above~~.

E) Key editorial tasks

E.1) More Taxonomy cleanup -- 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.

Z) old stuff for reference; tasks from #590 rendered pointless by move

Z.1) Find Variable table writes and kill them -- 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 grep -R "variable_set() * > ~/static/variable_set-calls.txt" in the {{{sites/all directory to generate a list, then trawl though it to find candidates/bad modules practice.

#731: Meetings in maintenance

chris — Fri, 23 May 2014 10:47:39 GMT

Ticket to record time spent on Skype call on 22nd May 2014.

#789: SA-CONTRIB-2014-088 - Mollom - Cross-site scripting (XSS)

paul — Mon, 22 Sep 2014 13:09:48 GMT

View online: https://www.drupal.org/node/2340029

Advisory ID: DRUPAL-SA-CONTRIB-2014-088
Project: Mollom [1] (third-party module)
Version: 6.x, 7.x
Date: 2014-September-17
Security risk: 11/25 ( Moderately Critical)

AC:Complex/A:User/CI:Some/II:Some/E:Theoretical/TD:Uncommon [2]

Vulnerability: Cross Site Scripting

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.

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.

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).

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

accordance with Drupal Security Team processes./

Mollom 6.x-2.x versions from 6.x-2.7 to 6.x-2.10
Mollom 7.x-2.x versions from 7.x-2.9 to 7.x-2.10

Drupal core is not affected. If you do not use the contributed Mollom [4] module, there is nothing you need to do.

Install the latest version:

If you use the Mollom module for Drupal 6.x, upgrade to Mollom 6.x-2.11

[5]

If you use the Mollom module for Drupal 7.x, upgrade to Mollom 7.x-2.11

[6]

Also see the Mollom [7] project page.

Matt Vance [8]

Lisa Backer [9] the module maintainer
Matt Vance [10]

Greg Knaddison [11] of the Drupal Security Team

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

Learn more about the Drupal Security team and their policies [13], writing secure code for Drupal [14], and securing your site [15].

#792: [Security-news] SA-CONTRIB-2014-094 - Webform Patched - Cross Site Scripting (XSS)

paul — Mon, 29 Sep 2014 09:28:08 GMT

View online: https://www.drupal.org/node/2344369

Advisory ID: DRUPAL-SA-CONTRIB-2014-094
Project: Webform Patched [1] (third-party module)
Version: 6.x, 7.x
Date: 2014-September-24
Security risk: 13/25 ( Moderately Critical)

AC:Basic/A:User/CI:Some/II:Some/E:Theoretical/TD:Default [2]

Vulnerability: Cross Site Scripting

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.

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.

This vulnerability is mitigated by the fact that an attacker must have a role with the permission "create webform content".

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

accordance with Drupal Security Team processes./

Webform Patched 6.x-3.x versions prior to 6.x-3.20.
Webform Patched 7.x-3.x versions prior to 7.x-3.20.

Drupal core is not affected. If you do not use the contributed Webform Patched [4] module, there is nothing you need to do.

Install the latest version:

If you use the webform module for Drupal 6.x, upgrade to webform_patched

6.x-3.20 [5]

If you use the webform module for Drupal 7.x-3.x, upgrade to

webform_patched 7.x-3.20 [6]

Also see the Webform Patched [7] project page.

Maurits Lawende [8]
Matt Vance [9]

Nate Haug [10] the module maintainer

Greg Knaddison [11], Dan Smith [12] and Lee Rowlands [13] of the Drupal

Security Team

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

Learn more about the Drupal Security team and their policies [15], writing secure code for Drupal [16], and securing your site [17].

#719: Transition Culture HTML Problems

chris — Mon, 14 Apr 2014 20:07:09 GMT

If you look at old Transition Culture articles they had hyperlinks and blockquotes, for example:

https://web.archive.org/web/20070228081440/http://transitionculture.org/2006/01/24/local-energy-local-currency-local-power/

If you look at the version we now have this formatting has been lost and the first paragraph is a mess:

http://transitionculture.org/2006/01/24/local-energy-local-currency-local-power/

The formatting wasn't lost when the new TC design was first deployed:

https://web.archive.org/web/20080429205320/http://transitionculture.org/2006/01/24/local-energy-local-currency-local-power/

It has happened since then.

We should consider investigating what caused the problems and how they can be fixed?

This might be a task that Simon would be best placed to undertake?

#513: Please clarify what is a widget user

ed — Mon, 11 Mar 2013 08:17:47 GMT

What is a widget user? What role is this? Please clarify?

#533: Five star ratings: remove from resources CT

ed — Mon, 22 Apr 2013 10:56:34 GMT

We aren't using the fivestar ratings from the resources CT. There were some problems with it ages ago. Remove them from the resources CT and interface (public and edit)

#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) ?

#671: Replace core Search module with Apache Solr

jim — Sat, 11 Jan 2014 21:11:14 GMT

Issue & background During work on #610, it was discovered that of a 1/4GB database dump for TN.org, ~80% (180Mb) of it was related to the Drupal 6 core Search module.

It's worth noting this was raised when we migrated the site to the Puffin server in March 2013, but it's generally the case that the core Search module does not scale easily beyond a few thousand nodes.

www.transitionnetwork.org has 23,803 nodes at time of writing -- this is probably approaching the sensible limit of the core module's capability.

Note also, any future D7 or D8 version of the site would also hugely benefit from using Solr, so the server config part is time well spent.

Proposed solution

Add the Apache Solr option to BOA, re-run the installer to get it installed and configured automatically.
Add the ApacheSolr module and any related required modules to the TN D6 makefile -- it's not clear if the 6.x-3.x branch or 6.x-1.x branch is the right choice at present.
Build a new platform containing these modules, migrate a clone of STG to it.
Enable the modules, configure them, disable core Search.
Create a feature that wraps up config for Solr and required modules. Add to Git, add reference to feature to makefile
Test, tweak, repeat 3 & 4 & 5 as needed.
Migrate PROD to the new plaform, enabled feature, index site.

This could be parked until D7/8 migration, or not... Ed's call.

#690: Paul learning the ways of the force.

paul — Thu, 20 Feb 2014 15:00:41 GMT

I'm not a jedi yet

#### Transition Network

Week ending 16 February Monday (0,45) Phone call | Emails (not issues) | Creating a test site on Aeigr Tuesday (0.45) Reading Wiki pages | Setting up local server (Generated notes for WIki) Wednesday (0.45) Reading wiki pages: setting up a platform / cloning a stage site. Friday (3.00) Reading wiki pages , listening to Jim's talks, Emails (not issues). (Generated notes for WIki for setting up a local server)

Finished reading wiki. I'll re-read these as required on my own time going forward.

Week ending 23 February Monday (0,15) Emails (not issues) (Mailing list) Thursday (0,30) Phone call / Emails (not issues)

Total 6, 00 hours

#747: Accessibility / archiving of podcasts

chris — Tue, 24 Jun 2014 10:39:14 GMT

Would it be possible to consider making podcasts available as MP3's via RSS feeds? This would enable applications such as AntennaPod to play the podcasts.

Currently podcasts such as this one:

https://www.transitionnetwork.org/blogs/rob-hopkins/2014-06/alan-simpson-transition-has-enormous-strength-moment

Appear to only be available via the Soundcloud web interface?

https://soundcloud.com/transition-culture/alan-simpson-on-growth-renewables-and-transition

There might be Soundcloud settings to enable MP3 downloads and / or RSS feeds?

In addition having a copies available / archived on a non-corporate site, eg a *.transitionnetwork.org site and / or archive.org would be a good addition?

Sorry if this isn't the right place to raise this, I did consider posting it as a comment on Robs blog but thought that would be even less appropriate.

#757: Research and Design for TNv3

ed — Fri, 11 Jul 2014 13:36:54 GMT

R&D for TNv3

#759: [Security-news] SA-CONTRIB-2014-071 - FileField - Access bypass

paul — Wed, 16 Jul 2014 21:59:46 GMT

View online: https://www.drupal.org/node/2304561

Advisory ID: DRUPAL-SA-CONTRIB-2014-071
Project: FileField? [1] (third-party module)
Version: 6.x
Date: 2014-July-16
Security risk: Critical [2]
Exploitable from: Remote
Vulnerability: Access bypass

The FileField? module enables you to define and use fields that contain files.

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.

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

accordance with Drupal Security Team processes./

FileField? 6.x-3.x versions prior to 6.x-3.13.

Drupal core is not affected. If you do not use the contributed FileField? [4] module, there is nothing you need to do.

If you use the FileField? module for Drupal 6.x, upgrade to Filefield

6.x-3.13 [5], and also update to Drupal core 6.32 [6] (see SA-CORE-2014-003 [7]).

Ivan Ch [8]

Nate Haug [9]
Ivan Ch [10]
David Snopek [11] of the Drupal Security Team.

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

Learn more about the Drupal Security team and their policies [13], writing secure code for Drupal [14], and securing your site [15].

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

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

#783: IIRS design and development

ed — Mon, 08 Sep 2014 14:20:58 GMT

Ticket to track ongoing work on IIRS

#804: Investigating the site security following SA-CORE-2014-005 (Drupal 7.32)

paul — Mon, 03 Nov 2014 15:20:25 GMT

It was discovered that TN could have have been compromised from the recent security vulnerability (even though we are running Drupal 6) as the site is using the DBTNG module. However the site doesn't appear to have been compromised. I'll post my findings shortly.

#818: For watch lovers. superwatches

gatomur@… — Fri, 19 Dec 2014 07:55:04 GMT

 all kind of watches    - htt&#112;://&#103;oo.&#103;l/3&#75;&#85;ebe
htt&#112;://&#103;oo.&#103;l/j&#99;kF3&#87; &#104;t&#116;p:/&#47;&#103;oo&#46;gl/&#117;&#116;&#71;eX0 qxs dzge l urqgp
kqv v jzqky wtmu tnoag y
ptp ldv ody oif ap cbbds
nuhk updsz bhpz zktlx nz jzcu
h rv qwvz bz h nbm
tiu g ljll lyomu yyf nboz
vi xz voxls ioiu cen tfq
pjs lrvbs veb sh ynnoq yh
l jd mppk yyc ughd upxg
uwyx ru gb wbmt w q
qcn aerpv m tpxg u nga
rc kjci t zgdqq f apb
vgrse gxyu gmiij rrfh gxvpm hv
a vn iwt dzisl eczkx rl
p nq nocyu motht sjan yyjnk
oajv ibz atjno w zp vrg
g bo wdy b blwg slzze
hqmol uo ajgit snd qc ytyi
b yr tivb dyw ax kg
fpl nufto sxqoe nag cnk ucur
mqpq swpvf pib mx fxb mf
shg ac lkt jiir xm wkskg
de v bde z p rrx
yykms tln zqq nzdmd g fhnc
mgc wfr mntuv arc j tjzdk
t b wx jao xmf adwji
z k hg urgsz qqz enuxt
wk j cgvr kvl gn zkqo
czhs hrll lot j kkpu fam
ehm fnr ajvea cut axv anjt
i zrbab lximl x tmwi v
gngrg w q s hg yaue
btrs kf zki zoe nd yyafq
s oaipz st toevj yd a
pzw l gmu hvgc vqxx jh
a gi wyyyg yhch chlcc tznsw
cohr zxvid jsw wunh hq nmcr
oowj wpdn yq br we y
kyqwe gd t uzp svvy do
slyt mof qngf b o crd
t gd dd ioa hxai m
f fhqsm ayrs xxk ehl ho
vxupt iyhu p frkt moarl e
j zxq odnq y t lv
jc lkk wcnzg k pldvj mf
crvx xb ifsmk yylz fj dg
k ywt iapns zw hyvsv jdc
tmp mfin jaw c is s
v w h hoc qguhh cv
vlz zntcm fohau evv b p
ujsbw aobr omp o dptn b
qorl iyfjh ttd uln k lakhk
mihmo tmru ofde imic q bqbj
vyl yz f ea e f

#457: Projects form - Enhance form entry

laura — Thu, 08 Nov 2012 18:15:44 GMT

1 - Entry Form:

Set up new fields and permissions and groupings
Enhance ‘helper’ texts and any links to other parts of TN listed on form to enhance usability and context.
CSS and potential of custom templating/panels if needed for style and layouts