- Development - lists.drupal.org

Re: [development] Being noisy on installation...
by Chad Phillips -- Apartment Lines 11 Apr '08

11 Apr '08

On Apr 11, 2008, at 1:37 AM, Earl Miles wrote: > I'm not sure Views originated this technique; but then again, I'm > not sure it didn't. i'm pretty sure i was the first person to do this. which either makes me a visionary or a bastard depending on how you look at it... ;) my personal opinion is that core should be more informative about what happens for something as important as a module installation. without the messages i currently hack into my own modules, the only way a user knows anything happened at all is by scrolling down the mile long list of checkboxes, and making sure that their module is now marked as enabled -- lame.

11 14

Re: [development] Being noisy on installation...
by Chad Phillips -- Apartment Lines 11 Apr '08

11 Apr '08

On Apr 11, 2008, at 11:52 AM, Morbus wrote: > Erm. What about the "The configuration options have been saved." msg? you're right. that's something. but it's still lame. my sentence probably should have read "the only way a user knows anything happened at all _regarding my module_ is by scrolling down..."

1 0

Being noisy on installation...
by Morbus Iff 11 Apr '08

11 Apr '08

So, I was reading over: http://drupal.org/node/161085 and saw one of my personal pet peeves jump out: "Even if your module doesn't have need of a hook_install function, it's nice to Display a note confiriming that the module is installed and ready for action." Core doesn't do it at all and, as far as I can tell, it originated with Views (which most folks take as an admonition that It's Right). Thoughts from the peanut gallery? At first blush, I'm horrifically opposed to it, because I think we have enough to worry about then reading /successful/ messages - I'd much rather Drupal interrupt me when something /bad/ has happened, not when something I /expect/ to happen actually happened. But, playing my own devil's advocate, I could say that "well, there's precedence already - we always inform the user when something has been created, updated, or deleted successfully". Whatever we decide, I care about consistency. If we're going to recommend this in our style guides, then /core should do the same thing/. -- Morbus Iff .sig on the other machine

16 25

DrupalToughLove.com launches (from chx and Morbus, gasp!)
by Morbus Iff 10 Apr '08

10 Apr '08

From the mission statement: "We all make mistakes; that's how we learn. Sometimes, though, we need someone to point out our mistakes, to sift through the chaos that is Drupal's contributions repository. Inspired by a comment on Morbus's code quality entry, chx and Morbus have taken up the task of giving some tough love to Drupal's greatest strength: the army of developers using its APIs. Want your own code publicly reviewed? Let us know!" http://www.drupaltoughlove.com/ -- Morbus Iff ( est quaedam flere voluptas ) Technical: http://www.oreillynet.com/pub/au/779 Enjoy: http://www.disobey.com/ and http://www.videounderbelly.com/ aim: akaMorbus / skype: morbusiff / icq: 2927491 / jabber.org: morbus

9 14

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