- Development - lists.drupal.org

Hello from another developer/Want to add some features
by Sammy Spets 01 Feb '06

01 Feb '06

Hi everyone, My maiden post to the list so please be kind. ;) First of all, congrats to you all for the great product so far. Big kudos for implementing a proper form api as well! Would love to chat to someone that designed/implemented it to get some idea of the design. I'll be happy to draw an image to represent it if I do get that chat. I've been maintaining a couple drupal run sites for two years and am now tasked with updating stuff from 4.4 to 4.7. Following is the list of things i've built into the 4.4 core that i'd like to port into 4.7. As you can imagine, security holes are very hard to close if you don't keep the core pure. Once a feature i'm proposing to implement has been accepted for inclusion in the core, i'll be happy to submit the patches. If these things are in the core already, a pointer towards some examples of it's use in modules would be much appreciated. Any questions about any of the additions i'm happy to answer. * Support for form fields to be rendered as either editable or view only. This has implications when one of the view-only fields is a key field. Additionally, it would be nice to discuss any ideas you've had implementing a system-wide user-based module field permission mechanism. There might be something in place already so forgive me if i've not rtfm. * Support for datetime and time fields. * Disabling changes to usernames and passwords of administrative users by users having administer users permission. Is anyone currently addressing the date field support in drupal? It could do with some localisation features as well, which i'm happy to add in. How does all this grab you lot? Cheers, -- Sammy Spets Synerger Pty Ltd http://www.synerger.com/

10 23

Theme a 4.7 node form?
by Simon Lindsay 01 Feb '06

01 Feb '06

Hi All, I'm developing some modules which define their own node derived types, and I also want to use actions/workflow and the event modules. However, by default, the actions/workflow field is at the bottom, and the event fields are right at the top. I can manually edit the workflow.module & event.module files, change the weights, and move them around, but shouldn't I be able to "theme" the node edit screen, to override the settings? I can theme the portion of the node I defined with no problems using the '#theme' entry in a fieldset, but that theme function doesn't receive the entire $form array/object. Do I have to write a x_form_alter function, or am I just missing something? This should also enable me to override the default event fields to use a popup calendar? TIA Simon

2 1

Front page module - The way it should be.[tm]
by Trae McCombs 01 Feb '06

01 Feb '06

Hey peeps, Since Gerhard was thinking the module isn't maintained, I thought I'd stick a comment here on the list. Currently, when you install the front page module, you have to go and change: admin > settings > "node" to "front_page" if you want your stuff to show up. To us "dorky end users", this is quite confusing. I would suggest that there is something inside the: admin > settings > front_page area that says: [x] Enable this option site wide. Help text: *** Warning, if you enable this, when people visit: your_drupal_site.com they will see what you have put here on this front page form. To change this action back, simply disable this option. --- This would then actually go set node to be front_page -- ... What do you guys(gals) think? Trae PS. See you guys at DrupalCon! You can beat me up (or attempt to) there! -- Trae McCombs || http://occy.net/ Founder - Themes.org // Linux.com CivicSpaceLabs - http://civicspacelabs.org/

10 15

Remove PHP filter by default
by Karoly Negyesi 31 Jan '06

31 Jan '06

Hi! A good read is http://www.webschuur.com/node/409 . Some points I do not care of, but: 1) As Drupal moves forward, upgrading PHP nodes is cumbersome at best. (blocks are easier to be found) 2) The security aspect. PHP filter is just too powerful. I can debate to death that it's safe now, no matter what -- the mere presence of PHP filter will make baby Rasmus cry :D However, it's true that defining a whole module is more complicated than a php node. Is it? I submitted a patch http://drupal.org/node/46857 which adds an 587 bytes module to core which lets you save a PHP into something.inc and then view it at the path pages/something. It just can't be simpler. Also, defining a block is more difficult than just using a snippet. Is it? No. The necessary module is a lot complicated this time, 690 bytes :) . Kind regards Karoly Negyesi

13 32

Drupal as a group decision making tool
by Steve Dondley 31 Jan '06

31 Jan '06

I wanted to alert Drupal developers to the following ideas found at http://www.blaserco.com/blogs/2006/01/28.html on Bill Blaser's blog. This gentleman has obviously done a lot of thinking about how organizations can use social software for democratic decision making processes. I think his ideas provide a very good foundation for any developers wishing to take Drupal in this direction. His thoughts really resonated with my thoughts lurking much more unconsciously in my head. -- Dondley Communications http://www.dondleycommunications.com Communicate or Die: American Labor Unions and the Internet http://www.communicateordie.com

3 2

authentication module without the @foo
by Bèr Kessels 30 Jan '06

30 Jan '06

Hi, I recently developed mysql_auth module [1]. Its rather silly/small, but still usefull. It allows users to authenticate against any other database, not nessecarily in drupal form, postgre works too, despite the name. I am testing now, but will release as soon as I have this last issue solved :) Right. What I want, is to get the authentication to be performed for any user. Not just user@foo, but if Joe is not fond local, then it should check for Joe in the other table. Drupal has this hardcoded, so the authentication hooks cannot do this. But I was wondering if there is another way to authenticate users? Some user_load trick I am not aware of? Ot maybe a patch that I can +1 to remove the hardcoded @ check? Blèèèèèr [1] http://help.sympal.nl/user/help#mysql_auth PS: I know about the way to share user tables but that is a) only usefull for tables in the form of drupal tables. (you cannot check for MyStrangeAPPusers) b) not perfect, because you need to share a /lot/ of tables, also ones like the {sequences}. it has side effects c) not very safe if you want to allow users from A to log in on B but those from B not on A. -- [ End user Drupal services and hosting | Sympal.nl ]

3 2

help w/ testing our new trashbin feature
by Chad Phillips - Apartment Lines 30 Jan '06

30 Jan '06

i'm not clear on number 3: i tried the exact same sequence you outlined using the test account, and the node recovered just fine. can you be more specific? as to hooks, the trashbin feature works through all the current hook systems, node, user, etc. so anything that was normally deleted outright will now be moved to the trashbin, then recovered when the deleted 'package' is recovered. table dependencies are a bit tricky, but i believe i've got a system in place that will do a fine job of testing any data that's about to be recovered for the relevant data it depends on > > 1) create blog entry: works > 2) delete entry: no confirmation, straight to trash. nice. saves time. > 3) recover from trash via the message box that says it's been deleted: > ACCESS DENIED > 4) Go to trash, then recover: works. > > Questions: are there enough hooks for things like url aliases ? > (delete node = delete alias; recover node = recover alias?) > > -Arnab >

1 0

Assigning user to roles programatically
by Rob Thorne 30 Jan '06

30 Jan '06

I'm looking for some way to assign a user to a role programatically. You'd think this would be easy to do, but it isn't: I tried just about every drupal hook you can think of to hook add this to the "user add" and "user edit" screens, and nothing worked. The problem was that node_save really really really wanted to get in there last, and I never found a way to get around this. I even tried to stamp the fields into the database. No use. node_save just went in at the end of the request and changed it back for me :-( Does anyone know how to coerce Drupal 4.6 into doing this? Or sweet talk it into this? It would be nice if there was an API for this, but AFAIK there isn't. What hook should I use, and which 2x4 do I need to apply? Thanks, Rob Thorne Torenware Networks

7 13

fixed project releases
by Dries Buytaert 30 Jan '06

30 Jan '06

Hello, I spent some time cleaning up various database inconsistencies in the project module tables (fun!). In total, 1665 releases have been deleted and merged (wow!). This might make the project pages a tad faster (woot!) and fixes the duplicate versions in the version selectors (yay!). The downside, however, is that you might want to double check your bookmarks as some URLs might no longer work (sorry!). -- Dries Buytaert :: http://www.buytaert.net/

11 15

Re: [development] Reboot the PHP filter talk
by Kobus Myburgh 30 Jan '06

30 Jan '06

Robert, You have a compelling argument. I withdraw my opinion from earlier ;-) Regards, Kobus >>> rob(a)robshouse.net 1/30/2006 12:16:08 PM >>> Kobus, I think the point is that filters have a clear path of integration through the module system already. A common case is that a module depends on the filter for a part of its functionality, and that the filter cannot simply stand alone. The the GMap module, for example. Without the macro creator to generate the blob of text from a Google map, the filter would be useless. Having it in a separate file would benefit nobody, and having some filters in modules and some filters in .filter files would be very confusing. Furthermore, filters often depend on other module hooks, so separating them from their module roots also doesn't make sense. cheers, Robert Kobus Myburgh wrote: > Hehe.. True, true. But how about .kobusshutup? > > Honestly, I really see the need of something like this - you can't seriously compare .user and .filter here, can you? A 'user' is not something you apply to content. I can also see the use of .menu. Soon .install files will also be wide spread. > > Kobus > > >>>> ber(a)webschuur.com 1/30/2006 12:05:45 PM >>> > Op maandag 30 januari 2006 10:36, schreef Kobus Myburgh: >> If I can butt in here long after talks have calmed down, I believe this is >> a good move, but it could be better if you could have some sort of >> name.filter that is plugged in with the filter.module, don't you think? In >> other words, simply copy the new .filter file in the same folder as the >> module to make it work? > > I oppose to Yet Another Module System. we have the .module. What would be > next .menu? .node? .user? etc. hooks are perfectly fine for this IMO. > >

3 2