April 2008 - Development - lists.drupal.org

Drupal 6.2, secholes and the lack of reviews
by Karoly Negyesi 10 Apr '08

10 Apr '08

Hi, First of all, I feel devastated over this. I tried to work out a working access inheritance model but I failed. Second I am furious. I was begging people to review the system. To port their modules during the beta period so problems can surface. Two people approached me with problems -- both of them had their issue fixed subsequently and we got very nice additions to the system (%map and %index). Two. The number of reviewers won't change overnight. So what we can do? Automate what we can and free up as much as we can so those few who do reviews can do quality reviews. We are working on that, of course. Please see http://drupal.org/testing-sprint esp. the bottom of the page, first two entries in the Next Steps section. Regards Karoly Negyesi

1 0

Drupal's approach
by luis almeida 09 Apr '08

09 Apr '08

Because Drupal is an open-source and collaborative CMS, I think it is very interesting if schools start adopting it. For my school's project I've chosen to work with Drupal and I was hoping to learn from it, giving my time in return. So I leave here my (so far) experience with Drupal use. This is my school project and this is the way it was planned to be carried out. ==DRUPAL'S APPROACH 1 - DRUPAL| INTRODUCTION: First steps Reading / viewing tutorials and handbooks.. >Studying Drupal's API >… Installing different Drupal versions >Requirements >5 and 6 Install different modules >Download >Activate >Use Create new simple modules >New content types >… 2 - DRUPAL| COMMUNITY: Interaction with drupal members Enter Drupal community: >Create a user account >Install development versions: 5.x, 6.x and 7.x >Entering Forum: >>Make some simple forum maintenance: Close old issues Critera:version: x.y.z >active/patch/task >>>Read all active issues of x.y.z version >>>Bump all feature requests (x.y.z), why? >This version is no longer maintained >Feature requests are placed against the most current dev version. >Give these feature requests one last chance of being reviewed >Clean up old issues that are no longer useful >Understand which of these feature requests have been implemented in more recent versions >>>Review all bumped issues and see community response to them >>>Participate on finding solutions to this issues >>>Is this useful? >It's good for learning >x.y.z feature requests become a closed chapter >Some good forgotten ideas can be reconsidered once again >>>Downsides? >Users get spammed with old issues >>>"Bug hunting": >Read/understand >Reproduce >Solve some simple bugs by patching 3 - DRUPAL| DEVELOPMENT: Improve or enhance the software Two possible ways: >Create new contributed modules >Start a new Drupal Site 4 - CONCLUSION My current status is at "bump all feature requests", so I have aprox. 80 x.y.z. issues left. But at this moment, I can't bring this task to an end using my first account (because it's blocked), so I would like to have some community feedback about my Drupal Approach: >Is it worth taking? >Does it bring any value to Drupal community? >What can be done to improve it? Once this is a community I think this as place of debate: ideas / work methodology etc. So it's my understanding that all opinions and different approaches should be respected and discussed. Because of my recent block account experience (which I'm having a difficulty to understand it's reasons) I would also like to know what the general opinion on blocking user accounts is: >Criteria (when does it applies?) >Procedures (how should be the process conducted?) I'll end now, leaving a couple of suggestions concerning the reason that brought me a blocked account: By bump x.y.z feature requests, I "disturbed(chx)" Drupal's users. What if: >We could add a subscribe functionality in issue posts, in order to allow users keeping track of the issues each one was interested in, avoiding to be popped up with old issues or topics they have no interest in. Or >Create a forum maintenance routine that places all feature requests from non-maintained versions against the most current dev version. By doing this I hope to bring to discussion some questions I find important to any person considering using and learning with Drupal. I appreciate the time you took reading this mail and any opinion/suggestion or whatever, I consider it valuable to my Drupal's experience. (Any difficulty understanding my English, just ask me that I'll clarify)

2 1

Menu help
by Nancy Wichmann 09 Apr '08

09 Apr '08

I could use a really good menu expert (chx?) to answer http://drupal.org/node/244496. Nancy E. Wichmann, PMP

1 0

must read: Maintainer News
by Peter Wolanin 09 Apr '08

09 Apr '08

If you have CVS access on drupal.org, you should have gotten the new Maintainer Newsletter. However, due to a technical snafu, about 30% of such accounts did not receive it. Please be sure you have read it - it outlines a minor API change that will be forthcoming in Drupal 6.2 which may require an update of your contributed modules: http://drupal.org/node/243389 The URL for this newsletter (for RSS, etc) is: http://drupal.org/maintainer-news Note, for those who do not have CVS access, you may subscribe to this newsletter via your user profile page on drupal.org -Peter

1 0

User not allowed to access node using node_access
by Steve Edwards 08 Apr '08

08 Apr '08

I wrote a module called Project Permissions that allows access to be controlled to Project and Issue nodes by user (using uid as gid in node_access). I installed it on a site, and specified access to a certain project node for a certain user, and the record was written as was expected to node_access. The role the user belongs to does not have the 'access project' or 'access project issues' permissions enabled. The problem is, the user can't even access the project that she should have permissions to access according to the record in node_access. The nid for the node is 9, and the user_id is 9, so the data in node_access is: nid - 9 gid - 9 realm - project_permissions grant_view - 1 grant_update - 1 grant_delete - 0 Here's my hook_node_grants: function project_permissions_node_grants($user, $op) { $grants['project_permissions'] = array($user->uid); return $grants; } I have the devel_node_access block enabled, and I can see that this record is the only one being returned from node_access. I've had this working on another site, so I'm not sure what else I could be missing. Can anyone explain why my user wouldn't be able to access the node? Thanks. Steve

3 5

change a module from dev to normal release
by Roman Chyla 08 Apr '08

08 Apr '08

hello, how am I supposed to get rid of the 'dev' from the 5.x release? I can't find it When I go to the add new release, Drupal does offer me only 6.x (which is not ready) and -1.x (which is nonsense) When editing the development snapshot, it says extra identifier 'dev', but in grey, no edits possible thanx roman

2 1

Updated closed issues
by Fernando Silva 07 Apr '08

07 Apr '08

Hi, I want to ask Drupal.org maintainers to update closed bugs (closed, duplicate, wont fix, etc) which have version "x.y.z" to another version. Ideally, it should be moved according to the issue last update, but to simplify things it can just be updated to 6.x-dev. Thanks, Fernando PS: "x.y.z" issues has only 6 pages, meaning that it can be removed very soon from the version option list.

2 1

blank screen at line 1
by Lluís 07 Apr '08

07 Apr '08

while developing a module, I have just started to recieve white screen every time I submit a form (besides form gets submited). In some cases I have been able to see this error: warning: Cannot modify header information - headers already sent by (output started at /var/www/ccc/sites/all/modules/comptacau/comptacau.module:1) in /var/www/ccc/includes/common.inc on line 141. but I file comptacau.module have no white spaces at start. Any hint of how to track this problem? thanks PS: memory limit is set to 256 just in case it was a memory problem, but apache reports no problem with memory. -- *Envellim quan els records superen les esperances. *Als llocs desconeguts només s'hi arriba per camins desconeguts.

4 5

Developer links block on drupal.org
by catch 06 Apr '08

06 Apr '08

In case anyone missed it, some of the development related links in "contributor links" have been moved to a new block. Same for documentation. So if you're missing the link to cvs commit messages etc., it's now there - just go you "My account" and enable the block(s) there. I can't take any credit for any of the work on it, but IMO it's a big improvement having them in different blocks. Original issue (still being worked on) is here for reference: http://drupal.org/node/225202

1 0

module duplication in Drupal contrib
by Greg Knaddison - GVS 06 Apr '08

06 Apr '08

Hi, "Modules that duplicate functionality available from an existing module are damaging to the Drupal project." Please support or refute that statement and propose strategies for managing CVS applications and/or projects on Drupal.org in a way that will best help the Drupal project. I'm using "Drupal project" in a very loose sense so you should infer that it includes lots of groups of people like new users, site builders, contributors, drupal.org admins, the security team, etc. Thanks, Greg -- Greg Knaddison Denver, CO | http://knaddison.com World Spanish Tour | http://wanderlusting.org/user/greg

25 34