October 2006 - Development - lists.drupal.org

RFC: version numbers for core translations?
by Derek Wright 18 Oct '06

18 Oct '06

i've discovered another potentially tricky issue with the new release system and version numbering schemes for contrib: what should we do about version numbers for core translation releases? request for comments (RFC): http://drupal.org/node/89969 thanks, -derek

1 0

module upgrade from 4.6 to 4.7?
by Chad Phillips 18 Oct '06

18 Oct '06

Hi, I am new to drupal. I need to upgrade a module from 4.6 to 4.7. It looks like a number of API changes where made. Is there a document that list the functions that were removed and what their replacements are? I looked at the document titled 'Converting 4.6.x modules to 4.7.x' http://drupal.org/node/22218, but it doesn't seem to have a complete list of removed functions. Some of the functions this module used in 4.6 are: form_item, form_button, form_submit,form_weight, etc.. All of these are listed in the 4.6 API documentation, but not in the 4.7 documentation. Is there a way to find out if they were replaced or just dropped? thanks chad

2 1

Drupal 5.0 beta 1: status update
by Dries Buytaert 18 Oct '06

18 Oct '06

Hello world, the current plan is to release a first Drupal 5.0 beta early next week. In order to succeed, we need you to help out in the issue queue as much as possible. We've quite a few bugs to tackle, some of which are critical [1]. So, if you could all review (at least) one or two bugs a day, we'd be able to get a ton of work done. Your help is appreciated. I'll be traveling next week, but Steven Wittens will coordinate the first Drupal 5.0 beta release. [1] http://drupal.org/project/issues? projects=3060&versions=10195,9902,9842,9753,9728,6487&categories=bug&pri orities=1&states=1,8,13,14 Thanks, -- Dries Buytaert :: http://www.buytaert.net/

3 2

Delicioius module maintainership
by Earl Miles 17 Oct '06

17 Oct '06

As a reminder, while I quickly found someone willing to take paging and masquerade, I'm still looking for someone who might be interested in taking over (and maybe even expanding) the delicious module. There's quite a bit of room for improvement there, so for a newish developer it could be an adventure. Although all it really NEEDS is for someone to fix bugs, make sure the 4.7 port really works, and bring it forward to 5.0 at some point. I know that there's a bug in the queue that the delicious API has changed and it needs to be updated for that.

1 0

Re: [development] Please suggest user experience improvement patches for: managing large list of items, and discovering Drupal administration settings
by Michelle Cox 17 Oct '06

17 Oct '06

On 10/17/2006 1:51:34 AM, Dries Buytaert (dries.buytaert(a)gmail.com) wrote: > 2. The watchdog is a really large list of events that is hard to > consume. I haven't used this module, so I can't vouch for it at all. I just remembered seeing it while looking at the modules: Log Search incidentist(a)civicspacelabs.org http://drupal.org/node/23883 I thought maybe it could be used as a head start on getting something in core if it's any good. Michelle

1 0

Please suggest user experience improvement patches for: managing large list of items, and discovering Drupal administration settings
by Kieran Lal 17 Oct '06

17 Oct '06

Hello, there are hundreds, possibly thousands of available patches in the queue for head. If there are patches available that address managing large lists of items (users, nodes, comments, groups, blocks, menus) then please help identify them. Also, if there are patches that help in the discovery of Drupal settings for administrators please help to identify those patches as well. These are not requests for new features to be added to Drupal 5.0. It is a request to help identify proposed solutions to user experience problems that have been identified in the Drupal administration survey. We would like to include these proposed solutions as part of the user experience survey report. Cheers, Kieran

7 9

Re: [development] Please suggest user experience improvementpatches for: managing large list of items, and discovering Drupal administration settings
by Nathaniel Catchpole 17 Oct '06

17 Oct '06

Just quickly. It'd be great if search (or filtering, or autocomplete) could be added to the url alias admin, it'd also be great if it could be in some way separate from the main drupal search function. We've got a 300mb database and have drupal search disabled due to the extra db weight, I'd imagine other medium to large sites do the same thing sometimes, and are also likely to be the ones with the longest lists... Nathaniel Catchpole On 14 Oct 2006, at 18:33, Kieran Lal wrote: > If there are patches available that address managing large lists of > items (users, nodes, comments, groups, blocks, menus) then please > help identify them. > Also, if there are patches that help in the discovery of Drupal > settings for administrators please help to identify those patches > as well. 1. I'm not sure there is a patch for it, but managing URL aliases can be a bit of a pain (eg. URL aliases for taxonomy terms -- and folksonomies in particular). 2. The watchdog is a really large list of events that is hard to consume. Really large lists of items need a search functionality: users, nodes and comments have a search functionality, but there is no such thing for path aliases or watchdog events. Hope that helps, but chances are this was rather obvious. ;-) -- Dries Buytaert :: http://www.buytaert.net/ -- Confidentiality: This email and its attachments are intended for the addressee only and may be confidential or the subject of legal privilege. If this email and its attachments have come to you in error you must take no action based on them, nor must you copy them, distribute them or show them to anyone. Please contact the sender to notify them of the error. Security: Security Warning: Please note that this e-mail has been created in the knowledge that e-mail is not a 100% secure communications medium. We advise that you understand and observe this lack of security when e-mailing us. Viruses: This email and any attached files have been scanned for the presence of computer viruses. However, you are advised that you open any attachments at your own risk. Please note that electronic mail may be monitored in accordance with the Telecommunications (Lawful Business Practices) (Interception of Communications) Regulations 2000. Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of B6 Sixth Form unless explicitly stated otherwise ----------------------------------------------------------------------- This message has been inspected by DynaComm i:mail -----------------------------------------------------------------------

1 0

new release system: patches needs review
by Derek Wright 16 Oct '06

16 Oct '06

i'm pleased to announce that v0.1 of the new release system is Done Enough(tm). of course, the system isn't completely done, in the sense that no further improvements could be made. ;) i just think it's at a point of functionality and usability that we could install it, start using it, and make incremental improvements going forward. therefore, the 2 main issues now need review: "make releases real nodes" http://drupal.org/node/83339#comment-145779 http://drupal.org/files/issues/release_as_node.patch_27.txt "port cvs.module to releases-as-nodes" http://drupal.org/node/84706#comment-146000 http://drupal.org/files/issues/cvs_release_node.patch_17.txt these apply against DRUPAL-4-7 of project, project_issue and cvslog. [1] i don't expect everyone to review every line of code (or even understand all of it -- i had to do some fairly nasty FAPI tricks to make the UI as smooth as i could for adding new releases). however, all of this is going to run on d.o and so we need to make sure it's all secure, the performance isn't going to be a problem, and that it all works how we want. so, any reviews would be most appreciated (and obviously essential before the whole system can go to go live). if you're not a heavy-weight drupal coder and don't feel up to the task of reviewing this stuff, you can still help by playing with the new system on a test site i've setup: http://drupal-release.dwwright.net/ this is running a modified copy of a DB snapshot from drupal.org as of about 2 months ago. all the email addresses have been stripped out (so trying to reset your password won't work!), and a few of the modules have been disabled (namely all the forums and aggregator/blog stuff). new account creation is disabled, but everyone with accounts on d.o can log in with their d.o username/password circa 2 months ago. projects and issues are of course still enabled. there's a scratch copy of the contrib cvs repository, too. this is just a shared hosting box, so the performance is pretty terrible. ;) don't let that scare you (and please be gentle on the site). ;) the main thing i need are people who maintain projects (modules, themes or translations) to login to the site, go to your project page, and try adding some new release nodes. i haven't yet written the handbook pages, so i'll just briefly document the process for adding a release here: 1) create a cvs tag for your release 2) navigate to your project node 3) click on the "add new release" link 4) fill out the N-page form (which involves specifying the tag you want to use) 5) wait for the cron job to package your release based on the tag [2] since it's going to be too much of a pain in the ass to give y'all access to this test site's cvs repository, i just created some tags across the entire contrib repo for your testing enjoyment. there are a few release tags and a few branches for each project. if anyone wants additional tags created you can let me know (preferably when i'm on IRC, or else via email). if you add a release node and point it to a branch, that means you want nightly development snapshots created from that branch. the conversion script that i ran (and which will run on d.o) automatically creates these release nodes for you for any existing releases (which are all snapshot releases from branches). however, to give y'all a sense of how things will work in the long term, i removed all the HEAD-specific releases for all the projects, so folks can see what's it's like to add a release node for both the HEAD (which is a special case for various reasons you'll see when you fill out the form) and for a regular branch (DRUPAL-5). my goal is that the UI makes enough sense that i don't have to say anything else. however, i'm sure some of you will be confused in the absence of any documentation, since i admit that some of it is pretty complicated. ;) in addition to adding releases, you can poke around with how releases interact with the issue queue, the project browsing pages, and the project nodes themselves. the last 2 in particular are areas of future work, but you can help verify that what's there isn't any worse than what we already have. ;) thanks for any testing, feedback, and most importantly, code reviews! i can't wait to get this all committed and installed on d.o!!! -derek p.s.: there are a *ton* of ideas i have about new features we can build on top of this. at this point, i'm not very interested in that -- i just want to get the basic system commited to cvs and install it on d.o. please file other feature requests and ideas as separate issues, instead of posting replies here, or following up to the 2 issues i linked to above. notes: [1] for convenience, a tarball of the latest code from those 3 directories, with the 2 patches already applied: http://drupal- release.dwwright.net/files/new-release-2005-10-15.tar.gz [2] the cron job packages releases from tags every 5 minutes, and does the snapshots from branches every 8 hours. for the interested reader, the packaging script itself is a separate issue: http:// drupal.org/node/88056

3 2

parameters for diff
by Peter Wolanin 16 Oct '06

16 Oct '06

As far as I can tell, the commands: "diff -u -F^f" and "diff -u -p" produce the same output. However, the former seems to be preferred in the handbook documentation. Is there some reason to prefer it? thanks -Peter

3 2

Re: [development] Usability: module idea
by Nathaniel Catchpole 16 Oct '06

16 Oct '06

The drupal module already carries an option for sending module install (and other?) information to drupal.org, and is disabled by default - could it be associated with that? Nat >If a module like this makes it into core for 5.0 beta, then my number >one concern is that it be disabled by default. Users can enable it if >they wish to, and they should be encouraged to do so (e.g. through an >announcement on the front page of drupal.org) By forcing users to >choose to enable the module, we will receive a much higher proportion >of real feedback (as opposed to blind-dumb-deaf feedback, or even >automated spam feedback). We will also be upholding Drupal's >reputation as an app that respects the privacy of its users, and that >doesn't try and force them to disclose information. -- Confidentiality: This email and its attachments are intended for the addressee only and may be confidential or the subject of legal privilege. If this email and its attachments have come to you in error you must take no action based on them, nor must you copy them, distribute them or show them to anyone. Please contact the sender to notify them of the error. Security: Security Warning: Please note that this e-mail has been created in the knowledge that e-mail is not a 100% secure communications medium. We advise that you understand and observe this lack of security when e-mailing us. Viruses: This email and any attached files have been scanned for the presence of computer viruses. However, you are advised that you open any attachments at your own risk. Please note that electronic mail may be monitored in accordance with the Telecommunications (Lawful Business Practices) (Interception of Communications) Regulations 2000. Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of B6 Sixth Form unless explicitly stated otherwise ----------------------------------------------------------------------- This message has been inspected by DynaComm i:mail -----------------------------------------------------------------------

1 0