- Development - lists.drupal.org

Re: [development] Connecting to multiple databases in 5.x
by Steven Peck 30 Dec '06

30 Dec '06

Chris submitted a patch to mention this change of behavior during the install. I spent about 5 minutes being very confused last week when I came across this as well. -sp > -----Original Message----- > From: development-bounces(a)drupal.org [mailto:development- > bounces(a)drupal.org] On Behalf Of Karen Stevenson > Sent: Friday, December 29, 2006 12:54 PM > To: development(a)drupal.org > Subject: Re: [development] Connecting to multiple databases in 5.x > > In windows at least, the file is actually made read-only and I never saw > any status message telling me that. That's OK and makes sense, but was a > surprise when I tried to edit the file and couldn't. My concern was that > if I temporarily removed the read-only access and made my changes that I > was going to do something that would create big problems for me down the > road (i.e. that it was write-protected partly so that nothing on it would > get altered in any way, even by me). So at the very least, any documention > that talks about making changes to the settings.php file from 5.x on > should mention that the file may be write-protected but it is OK to remove > the protection, make the changes, and re-protect it, since the fact that > it is read-only is going to scare others away from changing it. > > This came up because I have a module that needs a connection to an > external database to work and my previous instructions to users were to > make that change in their settings file, but the fact that it is now > write-protected might frighten them unnecessarily. I did it that way > instead of asking them to input the database connection info on the > settings page because I really don't like storing info like that in the > database. > > Anyway, if I don't have to worry about breaking something by making that > change, I can go back to doing it this way and document this in my > INSTALL.txt file. > > Thanks! > > Karen > > ----- Original Message ---- > From: Chris Kennedy <chrisken(a)mail.utexas.edu> > To: development(a)drupal.org > Sent: Friday, December 29, 2006 12:29:54 PM > Subject: Re: [development] Connecting to multiple databases in 5.x > > Settings.php is made read-only on install if possible (using > drupal_verify_install_file). See http://drupal.org/node/105368 which > adds a status message to clarify this (and needs a review). Or maybe it > would be better to have the read-only change be a checkbox on the > install page that is enabled by default but can be disabled. > > Also keep in mind that Drupal gives incorrect error messages in some > cases when settings.php is unreadable or doesn't exist. This might make > you think your database settings are wrong, when it is really a > permissions issue. http://drupal.org/node/100476 fixes some of these > cases (and needs a review). > > So, theoretically http://drupal.org/node/18429 should still work. > > Morbus Iff wrote: > >> Now that the settings.php file is write protected, the instructions > >> at http://drupal.org/node/18429 no longer work to connect to multiple > >> databases. I searched around but wasn't able to find anything on a > >> recommended way to do this in 5.x. And, of course, the documentation > >> on that page needs to be updated, too. > > > > settings.php is not write-protected. More than likely: > > > > * your webserver is a user and group that you don't have access to. > > * when the install.php wrote your settings.php for you, it was > > unable to give you proper permissions to write to the file. > > > > Drupal does not enforce write protection on the settings.php. > > The above is still the right way of doing multiple databases. > > > > The installer should be creating the file as writable. Could you tell > > us more about the permissions and ownership it created for that file? > > > > > > > >

3 2

If you want to alter taxonomy select
by Karoly Negyesi 29 Dec '06

29 Dec '06

Hi, If your module was ported to 5.0 already and it works, you have not got anything new to do. But what happens when it does not work because it wants to alter the taxonomy select box on a node form? Taxonomy select #options is nothing like they were in 4.7 and the new format is harder to manipulate. In this case you need to read http://drupal.org/node/64279#options -- sorry for adding a helper this very late but it is a helper, it is needed very rarely (that's why noone realized the need until now but thanks to Derek it still made it to 5.0) and it's very useful. Regards NK

2 1

Re: [development] Connecting to multiple databases in 5.x
by Karen Stevenson 29 Dec '06

29 Dec '06

In windows at least, the file is actually made read-only and I never saw any status message telling me that. That's OK and makes sense, but was a surprise when I tried to edit the file and couldn't. My concern was that if I temporarily removed the read-only access and made my changes that I was going to do something that would create big problems for me down the road (i.e. that it was write-protected partly so that nothing on it would get altered in any way, even by me). So at the very least, any documention that talks about making changes to the settings.php file from 5.x on should mention that the file may be write-protected but it is OK to remove the protection, make the changes, and re-protect it, since the fact that it is read-only is going to scare others away from changing it. This came up because I have a module that needs a connection to an external database to work and my previous instructions to users were to make that change in their settings file, but the fact that it is now write-protected might frighten them unnecessarily. I did it that way instead of asking them to input the database connection info on the settings page because I really don't like storing info like that in the database. Anyway, if I don't have to worry about breaking something by making that change, I can go back to doing it this way and document this in my INSTALL.txt file. Thanks! Karen ----- Original Message ---- From: Chris Kennedy <chrisken(a)mail.utexas.edu> To: development(a)drupal.org Sent: Friday, December 29, 2006 12:29:54 PM Subject: Re: [development] Connecting to multiple databases in 5.x Settings.php is made read-only on install if possible (using drupal_verify_install_file). See http://drupal.org/node/105368 which adds a status message to clarify this (and needs a review). Or maybe it would be better to have the read-only change be a checkbox on the install page that is enabled by default but can be disabled. Also keep in mind that Drupal gives incorrect error messages in some cases when settings.php is unreadable or doesn't exist. This might make you think your database settings are wrong, when it is really a permissions issue. http://drupal.org/node/100476 fixes some of these cases (and needs a review). So, theoretically http://drupal.org/node/18429 should still work. Morbus Iff wrote: >> Now that the settings.php file is write protected, the instructions >> at http://drupal.org/node/18429 no longer work to connect to multiple >> databases. I searched around but wasn't able to find anything on a >> recommended way to do this in 5.x. And, of course, the documentation >> on that page needs to be updated, too. > > settings.php is not write-protected. More than likely: > > * your webserver is a user and group that you don't have access to. > * when the install.php wrote your settings.php for you, it was > unable to give you proper permissions to write to the file. > > Drupal does not enforce write protection on the settings.php. > The above is still the right way of doing multiple databases. > > The installer should be creating the file as writable. Could you tell > us more about the permissions and ownership it created for that file? >

1 0

Even more flexibility in content management
by Zohar Stolar 29 Dec '06

29 Dec '06

18 26

Connecting to multiple databases in 5.x
by Karen Stevenson 29 Dec '06

29 Dec '06

Now that the settings.php file is write protected, the instructions at http://drupal.org/node/18429 no longer work to connect to multiple databases. I searched around but wasn't able to find anything on a recommended way to do this in 5.x. And, of course, the documentation on that page needs to be updated, too. I posted a comment on http://drupal.org/node/64279, but I'm not sure that was the best place to put it. Karen

3 4

You know what would be really cool for d.o?
by Earnie Boyd 28 Dec '06

28 Dec '06

I know this really should be a feature request but I'm not sure which issue tracker to put it in. If someone could point I'll be happy to. 1) I would like to see a Subscribe button on a particular issue so that I can easily subscribe to an issue. 2) I would like to see a user profile option for the issue tracker that sets a default subscription option for new modules added. Speaking of adding new modules, is there a subscription or list that announces the addition of new modules? Earnie

8 12

Re: [development] You know what would be really cool for d.o?
by Steven Peck 28 Dec '06

28 Dec '06

> -----Original Message----- > From: development-bounces(a)drupal.org [mailto:development- > bounces(a)drupal.org] On Behalf Of Earnie Boyd > > Speaking of adding new modules, is there a subscription or list that > announces the addition of new modules? > > Earnie Yes. Oddly enough in the handbooks on the top level http://drupal.org/node/63589

1 0

has this been discussed here?
by Eric Goldhagen 27 Dec '06

27 Dec '06

http://drupal.org/node/87145 I seem to have missed any discussion of this issue. I feel very strongly that a bad decision is being made based on bad reasoning. In my opinion the break tag is not broken and changing it is not helpful or wise. also, I think that the hostility shown in this follow-up thread http://drupal.org/node/105278 exposes some things about the direction the drupal community is heading that I find worrisome (and that I will write more about later, when I have the time) What is the value to the community of stepping on people that try to participate?; what is lost when people are pushed away by hostility and threats to delete comments and negate their valid and rationally expressed concerns? --Eric -- ------------------------------------------- Openflows Community Technology Lab, Inc. New York | Toronto | Montreal | Vienna http://openflows.com People are intelligent. Machines are tools.

6 7

Auto locale module (and an interesting bug(?))
by Gabor Hojtsy 27 Dec '06

27 Dec '06

Hi All, I have been working on an automatic locale file import module, so that we can provide install profiles which automatically import the PO files for modules enabled, without any user intervention (turn on locale module, add language, file upload). The alpha quality code works, imports all PO files I have thrown at it. I have left two debug messages in the code, because I experienced very interesting database behaviour while testing the code, and would appreciate your feedback. Project here with CVS link: http://drupal.org/project/autolocale My problem is that although I do a SELECT on the system table and go through that list sequentially I get: # Handling themes/engines/phptemplate/phptemplate.engine # Handling themes/garland/page.tpl.php # Handling modules/system/system.module # Importing modules/system/po/general.hu.po # Importing modules/system/po/system-install.hu.po # Importing modules/system/po/system-module.hu.po # Handling themes/engines/phptemplate/phptemplate.engine # Handling themes/garland/page.tpl.php # Handling modules/system/system.module # Importing modules/system/po/general.hu.po # Importing modules/system/po/system-install.hu.po # Importing modules/system/po/system-module.hu.po # Handling modules/autolocale/autolocale.module # Handling modules/block/block.module # Handling modules/color/color.module # .... Seems like it does go through the phptemplate engine, the garland theme and the system module twice. I have absolutely no idea why it would do this, since these appear in the database only once. I would appreciate if someone would be able to test and provide tips. This module/install profile would invalidate the need to merge the smaller PO files used by translators and really only import needed strings finally. I am going to beta test the concept with the Hungarian translation if the above issue can be resolved. Have a merry christmas, Gabor (who is now off to christmas dinner :)

1 1

Core issue tracker
by Boris Mann 27 Dec '06

27 Dec '06

On 12/27/06, Earnie Boyd <earnie(a)users.sourceforge.net> wrote: > Is there documentation somewhere that tells me what issue trackers to > subscribe to that deal with the Core modules? Drupal of course but are > there others? All core modules are in the core Drupal issue tracker. See http://drupal.org/project/issues/drupal for the "top" of the issue tracker. -- Boris Mann Vancouver 778-896-2747 San Francisco 415-367-3595 Skype borismann http://www.bryght.com

1 0