January 2009 - Development - lists.drupal.org

MS SQL support in D7?
by O'LEARY Jeremy 12 Jan '09

12 Jan '09

Hi all, I found scattered references to people getting drupal running on MS SQL and was wondering if MS SQL would be supported in Drupal 7? Thanks, + Jeremy

5 5

integrating chart module with cck and views
by sivaji j.g 09 Jan '09

09 Jan '09

Hello I have seen discussions in groups.drupal.org pertaining to "integrating chart module with cck and views" is there anything wrong in this idea because the person who proposed this idea for gsoc2008 has not commited any code. I am interested to do this project looking forward for your help to guide me on this. -- Thanks a lot ----------------------------------------- http://ubuntuslave.blogspot.com/

1 0

node family, node profile permissions problems
by Christopher M. Jones 09 Jan '09

09 Jan '09

Sorry if this isn't the right place to ask this question. I asked on the support list, but didn't get an answer. And this is somewhat urgent. I've got a content type set up as a lonely node profile. The problem I'm having is that nobody can edit a node of this type, except the user who authored it-- not even user 1. I can see how this would be by design. But in my case I need to allow members of an editor role to have access to other users' node profiles. I've made sure that the editor role has all the permissions they need in Users->Access Control (create, edit, edit own), and I don't see any other permissions related settings in any of the above modules' configs. I've done everything else I could think of to do: clearing cache, rebuilding permissions, etc. I think I'm going to have to hack some code, which I'm up for, but I'm not sure where to start. Can anyone give me a hand? Like I said, this is about to become extremely urgent, so any help is greatly appreciated.

3 3

how to run new .install on installed module
by Tomáš Fülöpp 09 Jan '09

09 Jan '09

Hi, Probably a simple problem but I don't find solution on d.o. I have a D6 contrib module that did not use database before, but now it does. The problem is that even though a .install file has been added, the database is not created in case the older version of the module is enabled already, not even after running /update.php. http://drupal.org/node/323314 explains that ".install file is run the first time a module is enabled" -- but how to make sure the initial database is installed on an existing module? Is the only solution to solve it via hook_update_N, detecting whether the table exists, and installing it -- even though in fact we are installing, not updating? Thanks, Tomáš

3 3

Database creation on Install
by Amy Stephen 09 Jan '09

09 Jan '09

I apologize if this is not the appropriate place to ask this question but I am curious after checking out your fine development work. Why doesn't the Drupal Installation process try to create the database if it doesn't exist already? WordPress is the same. Joomla! will use the database if it exists - and create it, provided the ID has sufficient permissions. It's just another "make things easier" step (for both the "newbie" crowd, but also developers testing/working). I was curious if there were security concerns? Or, if it just never seemed to be someone's itch? Again, if I am out of place with this question, please let me know, and forgive my ignorance. Kind regards, Amy :)

10 15

how to implement hook_views_data() and add a field?
by yi yang 08 Jan '09

08 Jan '09

Hi, All I want is just return a number, which comes from a sql query count of my custom table. I want to represent that as a field so I can adjust it's position in the views ui. It doesn't sounds like very hard, right? I've looked into the views api 2, but there's really no useful information... Anybody can help? Regards, Yi Yang

4 5

Please help clear out Drupal 6 critical issue queue
by Gábor Hojtsy 07 Jan '09

07 Jan '09

Hi, The current Drupal 6 critical issue queue is 2 pages long. It was three earlier today, and I took around 1.5 - 2 hours today to clean up some of the very old cruft. Most issues were duplicates of things dealt with elsewhere, even some issues were solved already in current Drupal versions. Some really interesting items popped up however, which were not dealt with (eg. installer cannot be used to set up multisites, taxonomy term paths with views, taxonomy term deletion problems, etc). There were also developer issues, which were not critical to Drupal, but only problems with people on using our APIs. All-in-all it would be good if some other dedicated fellows could help clear out the critical issue queue, so that it only has real critical issues remaining: http://drupal.org/project/issues?projects=3060&categories=bug%2Ctask&priori… As it is, it does not shed a good light on Drupal 6 that it seems to have so many critical issues open, while many of these are either developer support requests, already solved, or interaction problems with contrib modules. Thanks for your help, Gábor Hojtsy (Drupal 6 maintainer)

2 1

default settings for new content type
by Aldo Martinez Selleras 07 Jan '09

07 Jan '09

how to setup the default options, like disable comment, promoted to frontpage? i mean, with a content type created by me, from php code. -- ---------------------- Aldo Martinez Selleras Administrador del Nodo CITMATEL GND Camaguey Tel: 32-291661 E-mail: aldo(a)caonao.cu Linux User #364356

3 4

Put a site into maintenance-mode, but not for all...
by Jens Reinemuth 07 Jan '09

07 Jan '09

Hi @all... i try to figure out how to put a live website into the maintenance-mode, but leave it fully accessible by a fixed IP-Range of developers so that bugs can be fixed and tested in a fully running site... Drupal V5.x... My way would be a modification of menu.inc: --snip-- function menu_execute_active_handler() { $client = $_SERVER['REMOTE_ADDR']; $arrAllowed = array ('www.xxx.yyy.zzz','127.0.0.1'); if (_menu_site_is_offline() && !in_array($client,$arrAllowed)) { return MENU_SITE_OFFLINE; } --/snip-- the array is just in there for testing purposes, will be replaced by a GLOBAL or something like that... Is this the only way to do it (as after an update menu.inc could be replaced...) ? Jens

4 8

A streamlined way to develop core patches
by David Timothy Strauss 07 Jan '09

07 Jan '09

I've made a post on the Four Kitchens blog about a new repository we're hosting to support streamlined core development. The post is here: http://www.fourkitchens.com/blog/2008/12/07/using-bazaar-work-drupal-core-p… And here it is in plain text: As anyone who's developed core patches knows, it's not the writing of initial patch that takes the work, it's the combination of revising the patch and keeping up to date with HEAD. With Drupal.org's CVS, this is difficult because you cannot commit your core changes to checkpoint your work. CVS's merge algorithms are also relatively poor for maintaining large divergence from CVS HEAD. One option -- which several community members used to create the huge DB-TNG patch -- was to create a Subversion repository. This is far too much overhead for smaller core patches, and it still required person-by-person approval to commit to the Subversion repository. Four Kitchens is now hosting a much more flexible system for users of Bazaar. Every hour, we synchronize core changes from CVS HEAD into our Drupal 7 branch, which is available for anonymous branching by anyone. Simply download and install Bazaar, which has packages or installers for Linux, Windows, Mac OS X, and BSD. We're using a repository format that should work with Bazaar 1.0 and newer, at a minimum. Then, where you're ready to develop, run this: bzr branch bzr://vcs.fourkitchens.com/drupal/7 [optional-working-copy-directory] You'll have a fresh working copy with a number of benefits over a CVS checkout: You can commit to your local branch to checkpoint your work: bzr commit You can integrate in changes to HEAD using Bazaar's superior merge algorithms: bzr merge You can branch from your own branch: bzr branch [existing] [new] If you're working with others and they have Bazaar branches, too, you can merge from their branches to collaborate. And when you're ready to post a patch, run bzr diff --old bzr://vcs.fourkitchens.com/drupal/7 to create a patch reflecting all of your changes relative to CVS HEAD. It will be a while before Drupal.org moves to anything other than CVS. Until then, we can foster decentralized development quite effectively using something like the Four Kitchens repository.

8 11