<br><br><div><span class="gmail_quote">On 8/17/07, <b class="gmail_sendername">Boris Mann</b> <<a href="mailto:boris@bryght.com">boris@bryght.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 8/17/07, Kieran Lal <<a href="mailto:kieran@civicspacelabs.org">kieran@civicspacelabs.org</a>> wrote:<br><br>> 2) Extend the services in Drupal module so that hosting companies could get<br>> remote information from all their sites. We used to configure CivicSpace
<br>> distro to ping back to CivicSpace. <a href="http://Drupal.org">Drupal.org</a> used to do this as well. It<br>> would be good if service providers could get information from their sites.<br>> It would be helpful if distribution profiles maintainers could know what
<br>> sites are using their distribution. If this was extensible so that service<br>> providers could also send information to site that would also help. "We are<br>> going to upgrade your site" "We have applied the latest security updates".
<br>> This could include OpenID login to securely transmit this information back<br>> to <a href="http://Drupal.org">Drupal.org</a>, hosting provider, etc. Some of this framework is in place<br>> with updates now in D6, but it needs to be even more extensible.
<br><br>This is what I was talking about with a set of "dashboard" modules and services.<br><br>And this would all be in contrib modules in any case, nothing to do with core, and no changes to core needed.</blockquote>
<div><br>Unless we extended the Drupal module to do this. But starting with a contrib module would be a good place to begin. Nedjo did some advanced work for the Drupal module back in 4.7. It should be revisited.<br> </div>
<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> Right now, having multiple versions of modules in the bootstrap path can<br>> cause conflicts. It also means a server side OS process must remove old
<br>> modules or a system administrator must do this. My preference would be to<br>> make this all configurable through the web interface or server side policy<br>> and avoid additional server side processes. Basically, you could obsolete
<br>> modules, and even non bootstrap core code, in place.<br><br>This is Apache configuration. Hostmaster upgrades by switching a base<br>drupal core to include from, so every upgrade is, in fact, a separate<br>docroot. More than one way to skin this cat, no changes needed to
<br>Drupal core as far as I can see.</blockquote><div><br>If you have Drupal version 1 in /var/www/version1 and your required modules are in /var/www/version1/modules then the filename values in the system table will be modules/modulename/modulename.module.
<br><br>When you change document_roots the new version of the required module will be found at modules/modulename/modulename.module but it will now be pointing to version2 of that required module.<br><br>If you have Drupal version 1 in /var/www/version1 and your required modules are in /var/www/version1/sites/domain/modules/ then the filename values in the system table will be /var/www/version1/sites/domain/modules/. When you switch document_roots to do an upgrade you will encounter a problem.
<br><br>Your version2 of Drupal will have a hard coded system table filename path (/var/www/version1/sites/domain/modules/modulename/modulename.module) and will be pointing to the wrong version of the required module. When you try to bootstrap version2 drupal for the first time you'll get an error. Therefore automated upgrading will require both a check and possibly a change to the filename value in the system table.
<br><br>If the bootstrap was lighter weight you would not have to worry and the system.module could refresh the filename's for the newly upgraded document root.<br><br>For now, you are required to keep the 6 required modules in drupal_root/modules. It's not worth changing on it's own, but this problem would be solved by greater control over bootstrapping.
<br><br>Kieran<br><br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">--<br>Boris Mann<br>Office 604-682-2889<br>Skype borismann<br>
<a href="http://www.bryght.com">http://www.bryght.com</a><br>_______________________________________________<br>consulting mailing list<br><a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br><a href="http://lists.drupal.org/mailman/listinfo/consulting">
http://lists.drupal.org/mailman/listinfo/consulting</a><br></blockquote></div><br><br clear="all"><br>-- <br>To strive, to seek, to find, and not to yield.<br>