Transition Technology: Ticket Query

#520: Session 443 config in settings.php

chris — Fri, 15 Mar 2013 23:16:49 GMT

There is this warning displaying at https://www.transitionnetwork.org/admin/reports/status

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']) && $_SERVER['HTTPS'] != 'off') {
        ini_set('session.cookie_secure', 1);
      }

Based on the check of what is happening with cookies done on ticket:371#comment:34 and ticket:371#comment:36 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 wiki:PuffinServer and I'm not clear which one the live site uses.

#521: MySQL Unsafe statement warnings in the daemon.log

chris — Sat, 16 Mar 2013 09:46:57 GMT

I don't know if these matter?

I found them when hunting for 502 errors.

grep "Unsafe statement written to the binary log" /var/log/daemon.log | wc -l
343

Some examples:

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 < 1363426040 AND eid < (SELECT MIN(eid) FROM notifications_queue)

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

#603: Forwarding newsletter sends wrong message

ed — Thu, 03 Oct 2013 09:24:09 GMT

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.

Please consider.

From: Jeanne <mackeyj@…> Date: Mon, Sep 9, 2013 at 11:57 AM Subject: Jeanne is forwarding an email to you To: jeano <jmackey50@…>

Hi Will Sutherland,

Kathleen L thought you'd be interested in this: http://us1.forward-to-friend2.com/forward/show?u=766036b57dc1247e2964584bd&id=7b4f6d65d1

Kathleen L also included this personal message to you:

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?

You can forward it on to your friends, too: http://us1.forward-to-friend2.com/forward?u=766036b57dc1247e2964584bd&id=7b4f6d65d1

You can subscribe for more emails at: http://transitionnetwork.us1.list-manage1.com/subscribe?u=766036b57dc1247e2964584bd&id=33e8648c8d

Note: if any of the URLs above are not clickable, you can copy/paste them into your web browser.

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

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

#865: synchronisation

annesley — Wed, 15 Jul 2015 13:26:48 GMT

ideas. please query them.

we are synchronising between different data structures: WordPress and Drupal and anything else the plugin is installed on. therefore standard *database level* distributed synchronisation management tools will not be appropriate. this is unfortunate because synchronisation is a big task. however, it is possible that there are some CRUD / REST based sync tools. so: we need an XML abstraction layer (partially done already) produced by the Drupal, Wordpress, etc. plugin that is standardised and can then be compared and synced via standard API calls.

Steps:

new Transition Town registration on server A notify server B that there is new data and send the GUID of this new data server B then requests only the new data from server A (incremental) using the GUID server B creates the new item in it's database with a new native ID using the abstraction layer in it's plugin / module

addtions to this universal data pool, e.g. a new Transition Town, will be propagated via a network sync request at point of addition. "listener servers" will then request the new data (incremental only) and, in turn push that out to all other listeners. each plugin will therefore extend and expose it's CRUD style synchronisation abstraction functions:

add-user add-local-group change-user etc.

many of these are already available as part of the framework-independent plugin / module

currently, i suggest that ALL plugins contain ALL the international user and Transition Town data. passwords and emails, contact info will be handled by a 3rd server, either Mozilla Persona or Open ID. user accounts will also be synchronised on to ALL plugins but without passwords as those are held on the 3rd server. thus far had already been agreed with Ed. but, ofc, can be changed :)

new plugin installations will receive a full complement of data at time of installation. check digits will be periodically shared to check that all data is in-line. all users will be able to register and edit their data on ANY website holding the plugin. TT and USER changes and registrations will then propagate via PUSH notifications across the entire network all native IDs will be different. i.e. TT Brixton will have a different ID on each server. thus, as always with synchronissation, all IDs will be transformed to GUIDs by the abstraction API and only GUIDs will be used to analyse the network of data and synchronisation. login to any website containing the plugin will be transparent (unlike the demo i set up) through the normal wordpress and drupal login screens. the plugin will intercept failed authentication and attempt to authenticate against the universal servers. new accounts created via universal registration on any server will have a framework specific configurable role and thus permissions on that server will be set by the administrator specific to that server.