December 2006 - Development - lists.drupal.org

Temporary tables in search.module
by Ken Rickard 08 Dec '06

08 Dec '06

I am writing a search plugin for the MySite module, which displays content in MyYahoo! style link clusters. The requirement is that user be able to save searches to their MySite page. This requirement means that multiple searches might be requested when loading a MySite page. The core search function do_search() creates temporary tables to store data and assumes that only one search will be run per page load. As a result, trying to execute do_search() more than once per page view throws SQL errors. I have described the issue in greater detail here: http://drupal.org/node/102219 I am definitely not suggesting that temporary tables be removed from core. I am simply looking for a good solution to my issue. I would appreciate feedback on the issue, rather than the list. Thanks, Ken Rickard agentrickard

1 0

release schedule Re: [support] Access denied: You are not authorized to access this page- problem.
by Greg Knaddison - GVS 08 Dec '06

08 Dec '06

On 12/7/06, Cog Rusty <cog.rusty(a)gmail.com> wrote: > I wonder... Since the PHP 5.2 problem comes up very often recently, esp with > people with local AMP installations, isn't it time for an official 4.7.5 > release? > My apologies for bringing up a different topic when Drupal5 is down to just 3 issues in the Critical Issue list: http://drupal.org/project/issues?projects=3060&versions=94737,94702,96923,1… However, Cog raises a good point - when should we release a 4.7.5 version? I just wanted to redirect the conversation to a place that makes more sense to discuss the idea. Greg

4 3

old bug in issue email behavior finally fixed - might start getting emails for a change
by Derek Wright 08 Dec '06

08 Dec '06

hi folks, i finally fixed an old bug in how project issue emails are handled: http://drupal.org/node/61453 basically, if you ever used the "Issues e-mail address:" setting on your project node's edit tab (now on the "issues" subtab, of course), chances are you never got any emails because of it. for no good reason, you had to have "Administer projects" permissions to be able to set the filters for what categories and states you wanted to see the emails for. furthermore, the code didn't match the UI description. the UI claimed "If none is checked all categories will be posted" yet the code only emailed anything if you defined filters and they matched the issue in question. now: 1) everyone sees these filter checkboxes 2) the code matches the UI -- if you select no filters, all issues are emailed. SO... it's entirely possible that many of you have used this setting, but never got any emails for new issues or followups. perhaps you gave up on that and just subscribed to the issue queue(s) instead. if so, you'll now get duplicate emails until you either disable the "Issues e-mail address:" setting or unsubscribe yourself using: http://drupal.org/project/issues/subscribe/[project_name] sorry for any inconvenience this might cause, but the bug has been bothering me for a long time, and i finally had a chance to fix it. ;) furthermore, this "Issues e-mail address" setting has the benefit of actually *allowing* these filters, which the regular issue subscription interface does not, so you've got more functionality now than before. cheers, -derek

1 0

Historic Monument Module
by Chris McGinlay 07 Dec '06

07 Dec '06

Hi, I am currently developing a module aimed at custom display of images associated with historic monuments. I have a problem with the way I have extended the image.module using hook_form_alter() The module is here: http://drupal.org/project/monument Can someone advise me on this question: Using hook_form_alter in monument_image.module means that in effect every image becomes a monument_image. I need to find a way of extending the image module without forcing each image to have this extra data. Thanks Chris

2 2

Re: [development] getting the full $form in 5.x
by Peter Wolanin 07 Dec '06

07 Dec '06

Karoly, I'm asking in the context of this issue: http://drupal.org/node/88633 I'd like to be able to collect the array keys for all the form values that come about as a result of hook_form_alter. This way when a node type is deleted, the corresponding variables could be automatically deleted, rather than requiring modules to implement hook_node_type for this one simple case. In other words, I'd like to maybe separate out or duplicate the code in node_type_form_submit that saves/updates items in the variable table. -Peter Date: Thu, 07 Dec 2006 05:36:57 +0100 (CET) From: "Karoly Negyesi" <karoly(a)negyesi.net> Subject: Re: [development] getting the full $form in 5.x To: development(a)drupal.org Message-ID: <E1GsB0D-0002Jn-QZ(a)fenris.runbox.com> Content-Type: text/plain; charset="iso-8859-1" > Drupal 5.x to get the full form corresponding to a particular form ID? > Specifically, I want to have the $form with all the elements added > via hook_form_alter, but without rendering the $form. If this is what you want then indeed you need two steps. As you have not outlined what do you want to do with the form, I can't really guess a better way. Maybe you want to do $form = drupal_retrieve_form($form_id); drupal_prepare_form($form_id, $form); or even drupal_process_form($form_id, $form); Eaton did a very good job in slicing up the form workflow steps into separate functions -- but if you want half of a step, then you indeed need do it for yourself.

1 0

getting the full $form in 5.x
by Peter Wolanin 07 Dec '06

07 Dec '06

Maybe I'm missing something obvious, but is there a simple way in Drupal 5.x to get the full form corresponding to a particular form ID? Specifically, I want to have the $form with all the elements added via hook_form_alter, but without rendering the $form. Looks like I might have to do it in 2 steps: $form = drupal_retrieve_form('myformid') foreach (module_implements('form_alter') as $module) { $function = $module .'_form_alter'; $function('myformid', $form); } Thanks, Peter

2 1

General token parser (API), does it exist?
by Bèr Kessels 06 Dec '06

06 Dec '06

Hi, new-user-emails, welcome-mails, pathauto, newsletters, themes, auto_nodetitles and so on. Just a few random examples of token-replacement. Drupal has nothing in this regards, every module on its own, resulting in a lot of code-overhead, inconsistency and all the other downsides of not having a central/modular design. Are there any projects on this? Any APIs, libraries, or exsisting modules that do what I need: centralise token replacement? Or even an existing patch or issue that I missed? What need, more specific, is: * Present the user/admin with a list of available tokens (%username, %site etc) in a help message. * Parse these by replacing tokens with the value of a variable. What I don't need, is: * A new templating engine. * complex if-while etc structures. -- Drupal, Ruby on Rails and Joomla! development: webschuur.com | Drupal hosting: sympal.nl

7 7

Link Rel Next/Previous and First/Index and Home
by Gildas Cotomale 06 Dec '06

06 Dec '06

I often use Lynx to browse my Drupal site and i think that we should use "REL" and "REV" other than "stylesheet" in LINK for a higher accessibility, specially for books navigation... For those who are not familiar with that stuff, here are some nice links : <http://www.w3.org/MarkUp/HTMLPlus/htmlplus_55.html> <http://diveintoaccessibility.org/day_9_providing_additional_navigation_aids…> <http://wordpress.org/support/topic/39661> Now, here is my question. Does Drupal core (specially book.module, or is it a theme specific trick?) provide native support for that? If yes, how to use it? If no, any one has idea how to add this? Thanks

2 2

New docs for multipage forms in drupal.org handbook
by Jeff Eaton 06 Dec '06

06 Dec '06

A few months ago during the crazy dash to rewrite FormAPI, I wrote up a guide to making multistep forms and posted it to my blog. It's now been moved to the Drupal.org handbook at http://drupal.org/node/101707 where it can do more good. It's a bit wordy, and it includes some historical background for 4.7 that's probably unnecessary now, but to the best of my knowledge it's the only place that the nature of the #multistep flag is documented. :-) In the future I'd like to update the multistep example module in contrib to match this article, too. --Jeff Eaton

2 1

Re: [development] General token parser (API), does it exist?
by Nathaniel Catchpole 06 Dec '06

06 Dec '06

The thing with this though - I'm not a coder, although I try to do things properly as much as possible (hence why I lurk and occasionally interlope on this list). My first point of call would be the pathauto module for this functionality - on my site that'd give me 11,000 url aliases for something that "can be done with very little bit of custom code, in a custom_url_rewrite function." Presumably it's exactly the same for my c. 4-5,000 taxonomy/term url aliases. If there is (or can be) a cleaner way of doing it that'd be amazing. Nat -----Original Message----- From: adrian rossouw [mailto:adrian@bryght.com] Sent: 06 December 2006 15:11 To: development(a)drupal.org Subject: Re: [development] General token parser (API), does it exist? On 06 Dec 2006, at 4:05 PM, Nathaniel Catchpole wrote: I guess a similar thing would be something like an option to change what's used for /node/ from core (say to /article/[nid] or /story/[nid]) rather than aliasing. If that's the same thing that Bèr mentioned I could see it being really useful. this can be done with very little bit of custom code, in a custom_url_rewrite function. -- 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