December 2006 - Development - lists.drupal.org

Seems I need to take sandbox in my own hands
by Karoly Negyesi 18 Dec '06

18 Dec '06

Hi, If this sandbox rule is not changed really soon then I will simply open a Project Team account at cvsdude.com and pay the monthly thirty two dollars out of my own pockets if need to be. This account has 5 Gigs of disk space and Unlimited Authorized accounts and Unlimited Monthly transfer -- it's aplenty for our purposes. Interested parties, please contact me. 329 dollars is the yearly fee, cheaper and once paid, we have a full year regardless of what happens. I hope I will get at least the permission to include our link in the handbook here and there. Regards NK

21 44

sandbox, project nodes, release nodes, and drupal.org's contrib CVS repo
by Derek Wright 18 Dec '06

18 Dec '06

wow, go offline for a few days and behold the mayhem that can break out on this list. ;) personally, i wasn't in favor of disabling the sandbox in the first place, and am happy to see the change reverted. that said, after reading all the related threads, i've noticed a few important misconceptions about how project nodes, release nodes, and our CVS repository interact with each other. i'll grant that all of this has been in flux (hopefully for the better) for the last year, but i think it's essential to clear these up as this discussion of the sandboxes evolves: - you do *not* need a project node before you can add a directory to the contributions/modules or themes directories. in fact, it's the other way around... the directory must exist in CVS before you can add the project node that points to it. - you *must* have a valid CVS account before you can add a project node. - before, project nodes were unpublished until there was a tarball generated for that project. this was (IMHO) a hack to get around the problem that we didn't want to maintain both a list of users with CVS accounts and a corresponding drupal role. so, anyone with an account on d.o used to be able to create a project node for something, but only once their CVS account was approved, and they committed code, and the packaging script ran, was a tarball generated and their project node published. now, only people w/ CVS accounts can make the project nodes, so they get published right away, and the existence or not of a release associated with the project has no bearing on if the project node is published, (and therefore, if the issue queue works, etc). - you *need* to have a valid *release* node for a project for it to appear in the project browsing pages (the "Downloads" tab on d.o, a.k.a http://drupal.org/project/Modules etc). those pages basically say "show me all the projects that have a release that matches the version i'm looking for". no release means you don't show up there. - our CVS access control (the "CVS access" tab on projects) only kicks in once there's an actual project node for a given directory in the repository. - creating a DRUPAL-4-7 branch for your project no longer automatically creates releases for it. so, you can even branch/merge your code before it's ever got releases (and therefore, visibility in the project browsing pages). here's an imaginary story for how all of this works together to give us some better alternatives than the sandbox for code in various states of not-yet-ready-for-end-users: a few folks want to collaborate on a new contrib module. no one is sure if it'll work, or who's going to maintain it, but they want to start hacking now. they add it as a new directory in contributions/ modules but DO NOT create a project node yet. anyone w/ a CVS account can collaborate in there, but it's basically invisible to end users[1]. later, they decide they want to start using an issue queue to coordinate bug fixes/features/tasks, so they create the project node and enable the issue tracker, but they still don't make any release nodes. the project is still basically invisible to end users on d.o since it's not in the usual project browsing pages. end users would only find it if they happened to search for the right term, or stumbled upon the project by noticing it in the enormous dropdown box when selecting a project when adding another issue or something. and, assuming our imaginary team of drupal ninjas were being responsible, the description on the project node (and the README.txt in CVS) would be full of bold, flashing warnings that "THIS CODE IS ALPHA -- BEWARE". but, people-in-the-know would now have a) an issue tracker, b) CVS access tab, c) all the cool CVS integration project + cvs.module provide (the "Developers" page, commit messages, etc). perhaps the story ends there, they give up, move on/abandon the project, whatever. maybe someone else comes along 9 months later and wants to pick up the torch again (and the infra team just hands over ownership of the project node to the new victim). instead, maybe their experiment works and they want to release their code. they just have to start adding tags and release nodes and poof, the project now shows up on the end-user-visible project browsing pages. so, while i'm happy to see the sandbox remain for cases where that's useful, i'd like to offer the above scenario as a good alternative for "pre-alpha" modules or themes. i think it's better because: a) it's more structured b) you can use an issue queue c) if it ever goes "live", early development issues are still there for reference, CVS commit messages (and therefore "cvs blame") can point to issue nids, etc. d) you can use the CVS access tab to ensure only the people you mean to be are hacking on your code e) you get a project node to use for description, news, etc. f) you can classify the module as appropriate so people looking at the project node don't just know it's a module, but what kind of module it is g) it forces you to pick a name for your thing, which will help prevent you from *exact* duplication of another existing project with the same name ... cheers, -derek (dww) [1] people who just do "cvs checkout contributions/modules" and then complain about how much crap is in there don't count in my book. ;) if you're getting drupal source directly via CVS you're already over a fairly high bar and i don't consider you the target audience we need to protect from yourselves. it's clear that we already have no guarantee of quality for what's in there now (even projects with releases), so the idea that "it's in contributions/modules, it must *sort* of work" is inherently flawed. if there are official releases (not dev snapshots) with clear, useful release notes, you can probably assume it works (even then, review it yourself or pay someone on the security team to audit it for you before you really trust it). if not, you're on your own...

3 2

sandbox, project nodes, release nodes, and drupal.org's contrib CVS repo
by Chad Phillips -- Apartment Lines 18 Dec '06

18 Dec '06

derek, i couldn't agree more with everything you've laid out -- this makes a lot of sense. the only thing i would add (and i think you kind of already covered this) is: no matter how much structure you build, there are exceptions, and chaos. so let's get a more clear policy in place that encompasses all the new tools we have (so that development that would benefit from the model you laid out can take place in a more informed manner) and also have a community place to put 'other stuff'! :)

1 0

Release critical bugs for December 17, 2006
by drupal-devel＠drupal.org 17 Dec '06

17 Dec '06

Article / bug reports 4.7 Beta/ CVS Errors assigned: msameer age: 38 weeks 2 days url: http://drupal.org/node/55533 CVS management/tracker / feature requests provide admin UI to set a release node's CVS tag to '' age: 2 days 5 hours url: http://drupal.org/node/103427 enforce sequential release tags in xcvs-taginfo assigned: dww age: 7 weeks 5 days url: http://drupal.org/node/90968 Event / bug reports Multiple-day event does not show in block after start date age: 4 weeks 2 days url: http://drupal.org/node/98119 [php5, clone] end-start-ongoing attribute does not ripple through age: 11 weeks 5 days url: http://drupal.org/node/85972 Major timezone bug in event module age: 17 weeks 6 days url: http://drupal.org/node/78572 event_start not being set age: 29 weeks 2 days url: http://drupal.org/node/65609 Fatal Error After activating "Browse Scheduled Events" in modules age: 32 weeks 2 days url: http://drupal.org/node/61920 INSTALL.txt incorrect age: 34 weeks 6 days url: http://drupal.org/node/59019 event calendars off by day/not respecting timezones - fix? age: 37 weeks 5 days url: http://drupal.org/node/56189 Flexinode generates an error age: 38 weeks 4 days url: http://drupal.org/node/55135 Calendar subscribing not working age: 39 weeks 4 days url: http://drupal.org/node/54036 Problem Selecting Event by Type age: 40 weeks 4 days url: http://drupal.org/node/52883 Event start and end times not getting saved in database age: 1 year 1 day url: http://drupal.org/node/41300 Issues with list view for events age: 1 year 1 week url: http://drupal.org/node/39943 Database error keeps popping up age: 1 year 2 weeks url: http://drupal.org/node/39396 Date problem on calendar, off by GMT offset age: 1 year 2 weeks url: http://drupal.org/node/39193 Events module bugs adding and changeing events age: 1 year 2 weeks url: http://drupal.org/node/39016 gmdate() warnings on windows install assigned: Omar Abdel-Wahab age: 1 year 24 weeks url: http://drupal.org/node/26140 Event / support requests Blank Page After Submit age: 35 weeks 19 hours url: http://drupal.org/node/58918 Can't Administer Event Module age: 49 weeks 2 days url: http://drupal.org/node/43509 displaying event start info in flexinode tabular view? age: 1 year 10 weeks url: http://drupal.org/node/33019 Event block missing content of many fields age: 1 year 12 weeks url: http://drupal.org/node/31532 Filebrowser / bug reports ArrayMerge Errors with PHP5 age: 42 weeks 1 day url: http://drupal.org/node/51174 Filebrowser / support requests File paths generated by new filebrowser are not leading to the file age: 16 weeks 10 hours url: http://drupal.org/node/80903 Gallery / bug reports IE error using embed not error with none-embed... when navigation block on right age: 32 weeks 1 day url: http://drupal.org/node/62119 Gallery / support requests import existing gallery2 user account age: 1 year 6 weeks url: http://drupal.org/node/35920 Glossary / feature requests po files and other language support age: 46 weeks 4 days url: http://drupal.org/node/46313 Goofy / feature requests Goofy Forum UI age: 1 year 11 weeks url: http://drupal.org/node/32294 Htmlarea / bug reports if Clean URLs is Enabled, upload_image in htmlarea not working age: 21 weeks 6 days url: http://drupal.org/node/74119 htmlArea/xinha firefox freezes (multiple textareas) age: 28 weeks 2 days url: http://drupal.org/node/66746 Layout is quirky age: 40 weeks 5 days url: http://drupal.org/node/52741 Toolbar won't display correct in IE 6 with Pushbutton Theme age: 1 year 14 weeks url: http://drupal.org/node/30696 Htmlarea / support requests Problem with size of button assigned: khayman age: 33 weeks 5 days url: http://drupal.org/node/60255 Listhandler / bug reports user lookup on name only assigned: zeroj age: 37 weeks 6 hours url: http://drupal.org/node/56936 Link to mailhandler does not use l() function age: 48 weeks 1 day url: http://drupal.org/node/44599 Listhandler caused error in "comment.module on line 996" ? age: 1 year 6 weeks url: http://drupal.org/node/36244 Listhandler 4.6.0 fails to send emails at all age: 1 year 21 weeks url: http://drupal.org/node/27095 Listhandler / tasks Correct/Complete Documentation age: 1 year 7 weeks url: http://drupal.org/node/34909 Mailhandler / support requests Creating a page using mailhandler age: 26 weeks 4 days url: http://drupal.org/node/68947 Mail Body not downloaded age: 49 weeks 3 days url: http://drupal.org/node/43374 Members / bug reports Update: beta5 and possible problem with php 4 age: 41 weeks 3 days url: http://drupal.org/node/52004 Patch for member.module to bring it up to 4.7 age: 45 weeks 1 day url: http://drupal.org/node/47829 foreach() assigned: neablo age: 50 weeks 6 days url: http://drupal.org/node/42350 Node (key)words / bug reports Nodewords and Comments conflict age: 2 days 9 hours url: http://drupal.org/node/103399 Error on delete node age: 16 weeks 2 days url: http://drupal.org/node/80505 can't use php functions in body of nodes assigned: Robrecht Jacques age: 17 weeks 2 days url: http://drupal.org/node/79315 Node (key)words / feature requests Can't Put Keywords in Categories age: 8 weeks 2 days url: http://drupal.org/node/90199 Enable nodewords for node type? age: 44 weeks 1 day url: http://drupal.org/node/48869 Node Aggregator / bug reports nodes are being created with no body age: 1 year 1 week url: http://drupal.org/node/40373 missing promote column assigned: Bèr Kessels age: 1 year 3 weeks url: http://drupal.org/node/38836 Naming issues with files and DB tables age: 1 year 8 weeks url: http://drupal.org/node/34298 RSS "no element found at line 1" age: 1 year 24 weeks url: http://drupal.org/node/26185 Outdated help texts age: 2 years 19 weeks url: http://drupal.org/node/9692 Import doesn't like XML/RSS feeds with no Title element age: 2 years 28 weeks url: http://drupal.org/node/8128 Node Aggregator / tasks move XML-parser into an inclde file. age: 1 year 25 weeks url: http://drupal.org/node/25439 Notify / bug reports Only first 50 or so users processed successfully age: 5 weeks 4 days url: http://drupal.org/node/93616 Path / bug reports Login as an alias gets cached age: 1 year 12 weeks url: http://drupal.org/node/31699 Poormanscron / support requests Poormanscron not doing what it says on the tin age: 14 weeks 1 day url: http://drupal.org/node/83252 Privatemsg / bug reports contacts not found age: 2 weeks 6 days url: http://drupal.org/node/99789 When enableing the module, Drupal tries to update instead of install age: 11 weeks 19 hours url: http://drupal.org/node/86830 privatemsg module: - database error - incompatibility with relationship module age: 44 weeks 1 day url: http://drupal.org/node/48866 Remindme / bug reports Argument #1 is not an array age: 26 weeks 2 days url: http://drupal.org/node/69286 Cron job creates SQL error age: 28 weeks 5 days url: http://drupal.org/node/66202 Subscriptions / bug reports Getting 'There are no active categories.' message even when vocabularies and the terms are present age: 5 weeks 6 days url: http://drupal.org/node/93228 Creating nodes resets OG e-mail subscription settings age: 8 weeks 5 days url: http://drupal.org/node/89506 Subscriptions remain active when access control maintain subscriptions is disabled age: 10 weeks 3 days url: http://drupal.org/node/87625 Taxonomy dhtml / bug reports IE 7 javascript errors on the page that display the categories age: 2 weeks 45 min url: http://drupal.org/node/101100 Disabling Teasers (Trimmed Posts) Not working when set to Unlimited assigned: samdeskin age: 7 weeks 3 days url: http://drupal.org/node/91299 doesn't work with taxonomy_access? age: 12 weeks 2 days url: http://drupal.org/node/85355 Error on Page with Internet Explorer 6 age: 26 weeks 4 days url: http://drupal.org/node/68906 Taxonomy DHTML's cache ignores user privileges age: 30 weeks 1 day url: http://drupal.org/node/64532 Does not work correctly in Internet Explorer age: 1 year 10 weeks url: http://drupal.org/node/33354 javascrip downloads square.gif for every category age: 1 year 43 weeks url: http://drupal.org/node/17366 Taxonomy dhtml / feature requests A unique page for each category group? age: 1 year 8 weeks url: http://drupal.org/node/34610 Taxonomy navigation / bug reports Taxonomy links only work for the first line of links assigned: PierreFWalter age: 42 weeks 2 days url: http://drupal.org/node/51149 Taxonomy navigation / support requests Taxonomy has dissapeared age: 1 year 10 weeks url: http://drupal.org/node/33061 TrackBack / bug reports install script does not put curly braces around table name age: 2 weeks 2 days url: http://drupal.org/node/100634 Sends trackbacks for unpublished nodes assigned: ankur age: 1 year 46 weeks url: http://drupal.org/node/16239 TrackBack / feature requests Use AKISMET to filter the spam, spam.module doesn't do the job age: 16 weeks 2 days url: http://drupal.org/node/80558 User experience / bug reports Verification Active assigned: maverickvarun age: 1 week 5 days url: http://drupal.org/node/101384 mail() has been disabled for security reasons assigned: pilotos age: 11 weeks 23 hours url: http://drupal.org/node/86798 Webserver Auth / bug reports Logging out error age: 37 weeks 2 days url: http://drupal.org/node/56663 Wiki / bug reports the wiki module can't work with HTML age: 45 weeks 5 days url: http://drupal.org/node/47124

1 0

CVS contribtions/sandbox changes
by Kjartan Mannes 17 Dec '06

17 Dec '06

Greetings, Originally the Sandbox was created as a place to put core patches that were pending review, as we did not have any issue tracker back then. Since then the project module has grown and can now cover most of the original purpose of the sandboxes. Since then sandboxes have been used for many original uses, some that are good and some that aren't so good. The good stuff are what the sandboxes were originally intended for, large or very experimental Core changes that weren't ready for a proper issue. The bad stuff is people using it as a place to store modules and themes, this has always been a bad idea as you loose out the option of using issues tracker, versions, and they are rarely included in searches for any new wide spread security vulnerabilities. Since sandboxes still have some limited use we aren't completely getting rid of it, but it will be cleaned up. To make this happen we have made the current sandbox directory read-only, and only approved people can commit new files and changes. All the current data in the sandboxes will remain there until January 15, 2007. Sandboxes who have had people request write access, and had this granted will remain and all the rest will be archived and moved out of the repository. To request access file an issue against the infrastructure tracker (http://drupal.org/node/add/project_issue/drupal_org_maintenance) it will then be handled. I'm pretty sure the CVS administrators will be lenient with regards to what is considered core patches and experimental stuff, but I doubt we will approve people using the sandboxes as a place to host mp3 collections, non-Drupal projects or even whole websites. Modules and themes that are in active use and/or development will be moved to the proper location upon request, this will preserve the CVS history whereas re-committing them to the right place will loose the history. Please file an issue on the infrastructure tracker for this: http://drupal.org/node/add/project_issue/drupal_org_maintenance. I know some people will be unhappy with these changes, but having thousands of files randomly stored in the CVS repos doesn't add value most of the time. We definitely want to help provide the tools for cool Drupal developments, but it will happen under slightly more orderly rules than the current wild mess. -- Kjartan

12 12

check out nodestack
by Karoly Negyesi 17 Dec '06

17 Dec '06

Hi, Konstantin created a fantastic implementation of my idea about dragging nodes into a block. I would like to see this in Drupal 6 as a generic node select interface. I first though of an API too, but not much an API need with this implementation, just check $_SESSION['nodestack'] . This can be good to select nodes for: -- spam removal -- promoting cool stuff -- node refences and likely a ton of other stuff I can't even imagine but you guys being so cool Drupal developers as you are will do with it. Thanks Konstantin!

4 4

changes to contrib repository?
by Peter Wolanin 17 Dec '06

17 Dec '06

Has there been some change to the contributions repository? I tried to commit some changes to a module iIm developing and I got the following error message: ** Access denied: pwolanin does not have permission to commit files in: ** contributions/sandbox/pwolanin/chemical ** Please contact the owner of this project and request to be added ** as a CVS maintainer, see http://drupal.org/node/63634. running "cvs login" and supplying my password again made no difference., nor di checkout out a new copy. -Peter

6 9

[User experience feature] Variable overrides in settings.php
by drlingo 17 Dec '06

17 Dec '06

Issue status update for http://drupal.org/node/38713 Post a follow up: http://drupal.org/project/comments/add/38713 Project: User experience Version: <none> Component: usability Category: feature requests Priority: normal Assigned to: Zen Reported by: Zen Updated by: drlingo Status: patch (code needs review) I have tried to use your patch however, I receive a blank screen when I installed the patch. What must I do to make this work? This problem with the online, offline function needs to be resolved I know I can't be the only one. drlingo Previous comments: ------------------------------------------------------------------------ Thu, 24 Nov 2005 05:56:03 +0000 : Zen Hi, When a user moves/duplicates a site with clean_urls on, caching etc. he is very frequently locked out if he can't get mod_rewrite etc. working. Similarly, with the new Site Offline/Online feature, there doesn't seem to be any option for the admin to turn it off or log back in if he accidentally logs out.. The site/default/settings.php file has a section that allows overriding these DB variables. If the above mentioned variables can be added (and commented out), it might make things a lot easier to rescue the site without having to mess around with serialized variables in the variables table.. <?php $conf = array( 'site_name' => 'My Drupal site', 'clean_url' => 0, 'clean_url_ok' => 0, 'cache' => 0, 'site_offline' => '0', ); ?> (I'm not entirely sure what clean_url_ok does, but I've added it in anyways..) If and when all the variables to be added are decided, I'll attach a patch file. Cheers Karthik. P.S User Experience/usability seemed like the best place to put this.. ------------------------------------------------------------------------ Thu, 24 Nov 2005 19:54:08 +0000 : Geary This is an outstanding idea! I have been in this fix myself, and naturally looked in settings.php to see if there was an override. Having these "safe mode" settings visible and commented out would save a lot of people a lot of headache. ------------------------------------------------------------------------ Thu, 24 Nov 2005 23:15:21 +0000 : lekei In my settings.php I have the ability to launch the site in safe mode: /* * Safe mode -- launch site with safe settings */ if ($ALLOW_SAFE_SETTINGS && isset($_GET['SAFE_SETTINGS'])) { $conf = array_merge( $conf,array( 'site_name' => trim($_SERVER['HTTP_HOST'],"/").' (SAFE MODE)', 'theme_default' => 'pushbutton', 'clean_url' => 0, 'cache' => 0, 'site_offline' => '0' )); } at the beginning of settings.php there is a line allowing disabling safe mode: // Permits launching the site in "safe mode" by acccesing it with: // http://yourdomain?SAFE_SETTINGS $ALLOW_SAFE_SETTINGS = TRUE; ------------------------------------------------------------------------ Fri, 25 Nov 2005 03:37:25 +0000 : Zen @lekei: ah, that's a lot cleaner. But I assume that you're either using Civic or have added this in yourself? It isn't present in standard installations. I'm not sure the _GET is really required though. Either way, you should make that into a patch and submit it. Cheers Karthik. ------------------------------------------------------------------------ Sat, 14 Jan 2006 22:56:33 +0000 : Zen Attachment: http://drupal.org/files/issues/settings_5.patch (579 bytes) Patch attached. -K

1 0

(no subject)
by Chad Phillips -- Apartment Lines 16 Dec '06

16 Dec '06

snip from Kjartan's post... "Originally the Sandbox was created as a place to put core patches that were pending review, as we did not have any issue tracker back then. Since then the project module has grown and can now cover most of the original purpose of the sandboxes" snip from Gerhard's post... "The rules haven't changed, they are only enforced." is there some reason we need to shoot ourselves in the foot by blindly applying an existing policy? let's look at a few things here: 1. The sandbox had an original purpose, and the sandbox resource was created 2. The original purpose is outdated 3. People have found other good uses for the resource so the policy for the sandbox is outdated, right? how about we take a little time to update the policy by discussing it here?? it's clear to me that in the intervening time, the community has used it's resourcefullness to find other good uses for the resource -- i think we should try to benefit from that. i see no reason to limit the sandbox to only giant core patches. the resource has obviously proven useful as a place to store pre-alpha contrib work -- there are already people who have spoken out on that. based on the statistics that Frando published, we're certainly not experiencing a resource problem. i'm in favor of a rule more like Karoly suggested: "sandboxes are to be used for code that benefits the Drupal community". can we give a shot at turning that into an updated policy?? hunmonk

1 0

Could be interesting ...
by Dries Buytaert 15 Dec '06

15 Dec '06

Could be interesting ... http://www.alledia.com/blog/seo_competition/ joomla_v._wordpress_v._drupal/ ... and maybe a good time to double check the SEO-ity of Drupal 5. ;) -- Dries Buytaert :: http://www.buytaert.net/

8 7