Index: README.txt =================================================================== RCS file: /cvs/drupal-contrib/contributions/modules/context/Attic/README.txt,v retrieving revision 1.1.4.2.2.7.2.2 diff -u -p -r1.1.4.2.2.7.2.2 README.txt --- README.txt 17 Sep 2010 18:40:25 -0000 1.1.4.2.2.7.2.2 +++ README.txt 11 Nov 2010 21:58:41 -0000 @@ -52,7 +52,7 @@ a book with media resources tightly to t like a contact block you've made to appear whenever a user is in the pressroom section. -1. Add a new context on admin/build/context +1. Add a new context on admin/structure/context 2. Under "Conditions", associate the pressroom nodetype, the pressroom view, and the media kit book with the context. 3. Under "Reactions > Menu", choose the pressroom menu item to be set active. Index: context_layouts/README.txt =================================================================== RCS file: /cvs/drupal-contrib/contributions/modules/context/context_layouts/Attic/README.txt,v retrieving revision 1.1.2.1 diff -u -p -r1.1.2.1 README.txt --- context_layouts/README.txt 9 Feb 2010 19:02:59 -0000 1.1.2.1 +++ context_layouts/README.txt 11 Nov 2010 21:58:41 -0000 @@ -21,7 +21,7 @@ In order to use context layouts, your si Basic usage ----------- Once you have layouts enabled, you can have a context trigger the usage of a -particular layout in either the admin interface (`admin/build/context`) or +particular layout in either the admin interface (`admin/structure/context`) or inline context editor. Different layouts may have fewer or greater regions than the default page template, so adjust your blocks accordingly. Index: context_ui/README.txt =================================================================== RCS file: /cvs/drupal-contrib/contributions/modules/context/context_ui/Attic/README.txt,v retrieving revision 1.1.4.3 diff -u -p -r1.1.4.3 README.txt --- context_ui/README.txt 9 Feb 2010 20:20:19 -0000 1.1.4.3 +++ context_ui/README.txt 11 Nov 2010 21:58:41 -0000 @@ -17,8 +17,8 @@ Requirements Basic usage ----------- As a site administrator you can manage your site's contexts at -`admin/build/context`. The main page will show you a list of the contexts on the -site and give you some options for managing each context. +`admin/structure/context`. The main page will show you a list of the contexts +on the site and give you some options for managing each context. When editing or adding a new context, you will be presented with a form to manage some basic information about the context and then alter its conditions Index: context_ui/context_ui.module =================================================================== RCS file: /cvs/drupal-contrib/contributions/modules/context/context_ui/context_ui.module,v retrieving revision 1.13.2.48.2.1.2.19.2.8 diff -u -p -r1.13.2.48.2.1.2.19.2.8 context_ui.module --- context_ui/context_ui.module 17 Sep 2010 22:42:57 -0000 1.13.2.48.2.1.2.19.2.8 +++ context_ui/context_ui.module 11 Nov 2010 21:58:41 -0000 @@ -54,7 +54,7 @@ function context_ui_block_info() { function context_ui_block_view($delta = '') { switch ($delta) { case 'editor': - if (user_access('administer site configuration') && strpos($_GET['q'], 'admin/build/context') === FALSE && $contexts = context_active_contexts()) { + if (user_access('administer site configuration') && strpos($_GET['q'], 'admin/structure/context') === FALSE && $contexts = context_active_contexts()) { return array( 'subject' => t('Context editor'), 'content' => drupal_get_form('context_ui_editor', $contexts), @@ -97,7 +97,7 @@ function context_ui_help($path, $arg) { case 'admin/help#context_ui': $output = file_get_contents(drupal_get_path('module', 'context_ui') .'/README.txt'); return module_exists('markdown') ? filter_xss_admin(module_invoke('markdown', 'filter', 'process', 0, -1, $output)) : '
'. check_plain($output) .'
'; - case 'admin/build/context': + case 'admin/structure/context': return '

'. t('Context allows you to manage contextual conditions and reactions for different portions of your site. You can think of each context as representing a "section" of your site. For each context, you can choose the conditions that trigger this context to be active and choose different aspects of Drupal that should react to this active context.') .'

'; } } Index: plugins/context_reaction_debug.inc =================================================================== RCS file: /cvs/drupal-contrib/contributions/modules/context/plugins/Attic/context_reaction_debug.inc,v retrieving revision 1.1.2.3 diff -u -p -r1.1.2.3 context_reaction_debug.inc --- plugins/context_reaction_debug.inc 4 Aug 2010 23:43:04 -0000 1.1.2.3 +++ plugins/context_reaction_debug.inc 11 Nov 2010 21:58:41 -0000 @@ -21,7 +21,7 @@ class context_reaction_debug extends con foreach ($contexts as $context) { if (!empty($context->reactions['debug'])) { if (user_access('administer site configuration') && module_exists('context_ui')) { - $name = l($context->name, "admin/build/context/list/{$context->name}", array('query' => 'destination=' . $_GET['q'])); + $name = l($context->name, "admin/structure/context/list/{$context->name}", array('query' => 'destination=' . $_GET['q'])); } else { $name = check_plain($context->name);