blazindrop

#!/bin/bash

### What this script does is query your current git repository (in your working directory) for the provided 
### git log range to try and parse ticket numbers of the format #<number>. It then takes those ticket numbers
### and queries Redmine's API to output ticket information.

### I have used this for release management to get a basic idea of the state of changes at any given time and 
### also to follow-up on any items needing attention. This is a bit fragile if your Redmine body/subject has HTML in it
### because that makes xmllint barf on unencoded html.

blazindrop

diff --git a/docroot/sites/all/modules/contrib/term_reference_tree/term_reference_tree.module b/docroot/sites/all/modules/contrib/term_reference_tree/term_reference_tree.module
index 7dbcf84..376714e 100644
--- a/docroot/sites/all/modules/contrib/term_reference_tree/term_reference_tree.module
+++ b/docroot/sites/all/modules/contrib/term_reference_tree/term_reference_tree.module
@@ -136,25 +136,34 @@ function _term_reference_tree_get_children($tid, $vid) {
   // very bad on large vocabularies.  Instead, we load the term as necessary
   // in cases where it's needed (such as using tokens or when the locale
   // module is enabled).
-  $query = db_select('taxonomy_term_data', 't');
-  $query->join('taxonomy_term_hierarchy', 'h', 't.tid = h.tid');

blazindrop

### CD into top level sites directory; change owner writable so drush can write new file
### find -maxdepth 3 -name .htaccess -printf "%p %M\n" -exec chmod u+w '{}' \;

# public directory
drush @sites eval 'file_create_htaccess(variable_get("file_public_path"),FALSE,TRUE);'

# private directory
drush @sites eval 'file_create_htaccess(variable_get("file_private_path"),TRUE,TRUE);'

# temp directory (some platforms only need to run this on one site for shared temp directories)