September 2006 - Development - lists.drupal.org

Chance to get money for Drupal-related development
by Benjamin Melançon 27 Sep '06

27 Sep '06

(I don't know if this is off-topic, especially in the middle of getting to 5.0, but I wanted to bring it up the opportunity among Drupal developers. Full note posted at http://drupal.org/node/86325 ) The Knight Brothers 21st Century News Challenge hopes to recognize transformative ideas, pilot projects, leadership initiatives and investment opportunities that will help improve the flow of journalism, information and news in the public interest." (with a total of $5M given out in 2007, application deadline the end of November.) Here's the link to the guidelines and simple application: http://newschallenge.org/ My own agenda is working with others to create various parts of a universal, democratic communications network (neither unmoderated nor moderated, but with prominence decided by random juries of people in the network). ... Mostly I hope people put in really strong applications to this foundation for any kind of Drupal project, as anything that benefits Drupal benefits all of us, and quite honestly benefits the goals of the Knight Brothers foundation too. ....there's people giving away money for a good cause (with a leaning toward open source) that could absolutely benefit Drupal, the application is fairly easy, and I'd love to collaborate with people to get more money to do better things for more projects! You can reach me through my contact form or at my cell phone, 508 737 0582. Thanks! More, including a link to proposal I made to fund the creation of a Related Items module, at http://drupal.org/node/86325

1 0

node_db_rewrite_sql implementation breaks on pgsql
by Sammy Spets 27 Sep '06

27 Sep '06

Hi everyone, It appears there is a _very_ serious implementation flaw with node_db_rewrite_sql() in that it fails (very) miserably on pgsql. It occurs when fields in ORDER BY clauses aren't placed in the list of selected fields. There is a patch available (posted by @smsimms - thanks!) to repair this problem. It uses a subquery to solve the problem cleanly. We need some input on the solution and some testing done on mysql. See: http://drupal.org/node/76819 Cheers, -- Sammy Spets Synerger Pty Ltd http://synerger.com

1 0

Re: [development] 5.0 Core Theme Update
by Trae McCombs 27 Sep '06

27 Sep '06

I think a happy medium (since this is a theme by committee) is a "Powered by Drupal" button/icon/something above the fold. This would probably be something most people will want to leave in place to show their support for Drupal. And not hinder them putting content in other places. The first thing people do with Bluemarine, I'm guessing, is to strip (somewhat difficultly for newbies) the Drupal logo at the top. If there is a "powered by" button, above the fold, and NOT the big giant Drupal logo, then people are going to be more likely to leave it in place even when they customize the theme. Someone with a better grasp of the english language can probably help me explain what I'm trying to say. :) [I know redneck(though I am NOT one), as I wuz born in Georgia!] Trae On 9/25/06, Richard Archer <drupal.org(a)juggernaut.com.au> wrote: > > At 6:34 PM +0200 25/9/06, Gerhard Killesreiter wrote: > > >> I think that is okay to not have as a hard requirement. I think a > better > >> statement on branding would be "It should look recognizable as Drupal, > >> once deployed on a bunch of new sites, for the sorts of people who > >> notice such things." > > > >Sorry, but I disagree. Branding needs to be more obvious. > > I agree. As this is the default theme for new installs, the > DrupalIcon and drupal brand should be very prominent in the > header. The user can then tweak this branding to suit > their requirements. > > There could also be a "Powered by Drupal" icon in the footer > which the user may choose to leave alone, even after replacing > the Drupal branding in the header. > > ...R. > -- Trae McCombs || http://occy.net/ Founder - Themes.org // Linux.com

6 7

Awaiting test feedback for the new patch of import_export.module
by Turhan Ercil 27 Sep '06

27 Sep '06

How to export from Import_export.module (Drupal 4.6) to import with Node_import.module (Drupal 4.7): You can now export nodes from Drupal 4.6 with import_export.module from different types of nodes to Drupal 4.7 using node_import.module, especially tested from Flexinode in Drupal 4.6 to CCK in Drupal 4.7. To be able to export properly you can choose the default values of delimiters after this patch, in the second page of the CSV export wizard. Select only the fields which already exists in your updated Drupal 4.7 For: "Output format of the Taxonomy terms": Select: "Term names" (as default) For: "Multiple-term delimiter": Choose: Pipe delimiter (|) (as default) For: "Field Delimiter": Choose: Comma (,) (as default) For: "Text delimiter": Choose: Quote (") (as default) Leave Max. Field length empty if you really don't need it. (It trims the field size to the number of character) Do a "Friendly Export" for a file export after you have tested the screen output with the "Export" button. For details and the patch: http://drupal.org/node/83799 Any feedback will be helpful for further development. Thanks

1 0

Anonymous users see "Edit Primary Links" on private sites
by Darren Oh 27 Sep '06

27 Sep '06

This issue has been open for almost a year now, and a good patch is available: http://drupal.org/node/42826 To summarize the problem, if anonymous users do not have access to content in the primary links menu, they see "edit primary links". Without the patch, preventing this requires either disabling the primary links menu for all users or adding a link to which anonymous have access. I cannot see how this limitation in site design would benefit anyone.

1 0

Bugfix mode
by Dries Buytaert 26 Sep '06

26 Sep '06

Hello world, now we're all back from DrupalCon Brussels, it is time to get back into "bugfix mode", as well as "module upgrade mode". The general feeling is that the trunk is fairly stable. In practice, however, there are hundreds of bugs that need fixing and hundreds of modules that need to be ported. It is almost a month since we froze the trunk and we have still a _lot_ of work to do. We'll have to increase the rate at which bugs get fixed or we won't be able to release Drupal 5.0 anytime soon ... The only way to get there is by forcing our collective brain to get into "bugfix mode". Let's start fixing more bugs. -- Dries Buytaert :: http://www.buytaert.net/

1 0

5.0 Core Theme Update
by Farsheed 26 Sep '06

26 Sep '06

Hi, Just an update about the Delicious Zen theme. I have made some changes after the last round of emails/comments. At this point I would like to ask for feedback regarding compatibility of the theme. Please, no more comments at this time about design such as color, font sizes, etc...what we need to do is iron out problems like browser compatibility and accessibility. Particularly discrepancies in alignment and white space. The theme should work perfectly in FireFox. There are 3 minor issues with IE that I noted in the issue queue. Another browser cam snapshot would probably help. Demo: http://www.drupalart.org/drupal48 Issue: http://drupal.org/node/81217 Download: http://drupal.org/files/issues/delicious_zen_14.zip __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

23 48

RE: [development] 5.0 Core Theme Update
by Nathaniel Catchpole 26 Sep '06

26 Sep '06

It's possible to do - Moodle uses this. If you're on any page where you have creation/editing permissions you have a button that says "turn editing on" - then you add blocks, content, change the contents of a page or whatever wherever you're working. You can leave it on, or "turn editing off" to view the normal admin interface, then there's a further "student view" which allows you to see things as a student would. The flipside of this is there's no backend for content - no block page, no mass node editing/moderation etc. - it's all contextual apart from admin, admin jobs. So it actually makes things a lot slower for some tasks. I think it's good for academic staff/non-technical administrators to be able to change things without having to know where to look, in terms of Drupal I guess it'd be good for multi-site hosting. I personally really don't like it, and the changes to the drupal admin interface I've seen floated elsewhere would seem to make more sense (i.e. grouping all content administration together - task rather than module based). If I want to administer blocks - I go to block administration, I don't want to go to every page it appears and change the settings there (which is close to how moodle does it, although I've not been using it long). Nat ------------- Hmmm, I just had an interesting idea... I'll get flamed for it I'm sure as I have no way to implement it, or even if it's possible. But what seems like it would be cool is, to provide a "Lock/Unlock" Theme switch that an admin could even hide. So somewhere, on the default theme, Perhaps above the Login area, or somewhere on the actual Primary Links, you have something like: Theme Details: Change / Hide This [?] Perhaps we use AJAX goodness, and if you click the "Change" button, then the logo, mission statement, other items right there on the front page immediately become editable via some form or some thing. Next to the Drupal Logo would now be the words: "Click to change this image". with AJAX browse for new logo and upload all rolled into one easy thingy. If they click the [?] it tells them what that stuff is all for. If they click Hide, it prompts "Are you sure you want to hide this, it will make it more difficult for you to change your theme elements in the future?" -- 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

display table in user_edit form
by Dave Cohen 26 Sep '06

26 Sep '06

Question about displaying form fields in a table. I've read some documentation <http://drupal.org/node/47582>. The solution described there involves defining a theme function named after the form_id. In my case, the form is a category in user edit pages. This means I don't have control over the form_id. It's 'user_edit', and the same form_id is used for all categories on the user edit pages. So, while I could define theme_user_edit() to render my form as a table, I don't think that's the right way. Because while my module could do it, it would be incompatible with any other modules or themes that also define theme_user_edit(). Can anyone recommend a workaround or other way to render a table on the user edit pages? Thanks, -Dave

2 1

RFC: new version numbers for core
by Derek Wright 25 Sep '06

25 Sep '06

as promised, we spoke about core version numbering schemes and code names at drupalcon. i wrote up a 1-page hand-out summarizing the 2 big threads we already had on this list and gave it out to folks for consideration. yesterday evening, dries and i finally had a chance to sit down and talk through the hand-out, why it's important, and what we should do. briefly: he's opposed to code names, leaning towards the 2-digit solution, but wants to gather some more feedback before he makes his final decision. he asked me to put the text from the handout into a forum post, along with a table summarizing the pros and cons of the 2 viable proposals. this way, people can clearly see what the options are and don't have to reiterate or get fixated on 1 pro or con and lose sight of the big picture. request for comments (RFC): http://drupal.org/node/85943 thanks, -derek (dww) p.s. please don't reply to this email, just comment in the forum post. that way, people who truly don't care won't get spammed by your email, and those who do can read your thoughts online.

1 0