January 2006 - Development - lists.drupal.org

using #downloads for quality of modules
by ae2005 21 Feb '06

21 Feb '06

one quick proxy for measuring quality of modules could be number of downloads, like the list kieran posted. presumably the most downloaded ones are relatively stable, due to research and filtering done by individuals first. i do think it'd be great to keep a list of top downloads in a very easy to find place on the site. ae

16 28

RE: [development] Issue status
by Steven Peck 08 Feb '06

08 Feb '06

It's automated.... after being fixed for a few days, it is closed. This lets poeple find them and see what happened while it's fresh and get it out of the way when it's closed. ________________________________ From: development-bounces(a)drupal.org on behalf of Karthik Sent: Fri 1/20/2006 12:39 AM To: development(a)drupal.org Subject: [development] Issue status I've noticed that a number of issues are being changed from "fixed" status to "closed" status by (an) Anonymous User(s). E.g. http://drupal.org/node/43498 Is this automated? Recommended procedure? or something else? Cheers -K

3 2

why locale import is slow and a memory eater?
by Gabor Hojtsy 02 Feb '06

02 Feb '06

Hi, Dries asked me to look into this for 4.7.0, since those with low memory settings or slow servers experience problems importing PO files. The issue is quite simple: - the import script loads in the complete file into a string (in an uberly complicated way :) - then it splits the string into $lines (into another variable) on which it does the processing - while processing the file, it builds up a $strings array which contains all the parsed information from the $lines array @ at this point, there are three copies of the po file in memory, taking up increasly more space: single string < line-by-line array < parsed array - all the above is done in a function, so when the function returns, the three copies of the file reduces to one (the returned $strings array), which is then processed element by element, and the database is modified accordingly It would be really straightforward to read the file line by line, which should get off a lot of burden from PHP (at least a megabyte of text, plus the overhead of the $lines array structure). That eliminates the first two steps. But then the best would be to directly process the PO tokens as parsed (ie. hand over information to the database as soon as possible, and do not keep a big array of this data in memory). And here comes the question. Now, if a PO file is broken for any reason, the real SQL import process is skipped. But whether the file is broken at some point is only possible to tell, if we parse the file up to that point. If the SQL changes are made incrementally, then the PO file would end up half-imported. Question is if it is a problem or not. I think this is a minor problem, since you are supposed to upload a translation which you are about to use, so if your po file is broken it is not a problem that it is half imported, you should fix and try again. I cannot provide an estimate on when will I have the time to work on this, but the file reading methods seem to be perfect low hanging fruit, even if the more direct SQL import is a bit more time to do. Let us clear up first that the incremental SQL import is sufficient. BTW first to upload files on a hosted environment, this open_basedir compatibility patch needs to get it: http://drupal.org/node/5961 Happy New Year everybody, Gabor

3 4

freetagging: let's users select a parent category
by Fabio Varesano 01 Feb '06

01 Feb '06

Hi everybody, I'm currently playing with the new free tagging feature of drupal 4.7 . A feature I would like to have is permits users to select a parent category while adding a free tag. What do you guys think about this? Fabio

5 5

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

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