July 2006 - Development - lists.drupal.org

internal link filter & master filter list
by Ray Zimmerman 12 Aug '06

12 Aug '06

I'm considering writing a simple input filter module to handle internal links [1]. It would take paths like node/99 and prefix them with the appropriate base_path. I have two questions: 1. Is there an official master list of input filter syntax somewhere that I can consult to make sure I don't use syntax that tromps on somebody else's existing filters? I was thinking of using something like [ilink:<internal_path>] (for internal link). 2. Can anyone suggest an alternate solution to the problem I'm trying to solve [1]? On a related note, I believe ideally, the Links package [2] should handle internal links as well as external ... not sure if that's the intention ... Scott? Thanks, Ray [1] There seems to be no supported solution for including robust internal links in your content (please educate me if I'm wrong here). The problem is to find a way to create an internal link in my content that will continue to work correctly without modification (e.g. like menu paths do) when I move the site to a new path. See this thread on the support list for a bit more background: http://lists.drupal.org/ archives/support/2006-07/msg00058.html [2] http://drupal.org/node/72459

13 33

archive module for core or not
by Gabor Hojtsy 08 Aug '06

08 Aug '06

Hi, As I have indicated, I taken care of updating and fine tuning the contrib archive module (originally by codemonkeyx) to work nicely with node access modules and timezones. Morbus Iff and Kazuo Oishi was of great help. This modules does not have a calendar block, but the date browsing is handled with an easier to use 'multilayer' interface. http://cvs.drupal.org/viewcvs/drupal/contributions/modules/archive/ Since we need to compute the timezone according to site/user settings, we need to deal with the date values of nodes in PHP (or if someone knows a better solution, please speak up). This means that the module is not terribly efficient, using 14 SQL queries to build up the browser interface. We can push this down to 3, but then one of them would select the dates for all nodes in a year, which might be big. We should talk about this, I have no hard data. If core should have an archive module, then this should be reviewed and refined. I have added phpdoc comments, and tried to name every piece in the code sensibly, so that it is understandable. If an archive module is not needed in core, the current one could be removed, since there is a viable working alternative now. The current one, which has timezone and node access problems is not liked much in the development community, and Dries already indicated that it has no future in core. The issue: http://drupal.org/node/29676 Gabor

4 5

Strip out theme functions into a .theme file
by Frando (Franz Heinzmann) 07 Aug '06

07 Aug '06

Now that we have modules in their own directories, I think we could move forward to ease pain for designers by stripping out theme functions out of the .module file into a .theme file. We already did the same for installation, and there's currently a patch in the queue to do the same for help files. Why we should move theme_* functions into a <modulename>.theme file: * ease pain for designers. Currently, they have to look through all the module code, that is not interesting for them at all, to find a theme function they want to overwrite. By having them all together in a <modulename>.theme file, it will save a lot of time and effort for them. And IMO we should take a bit more care of them, especially if it does not hurt at all. * Seperation of code and design has always been a main target. So I think it's only logical to stick to this policy here and move the V part of a module into a different file than the C part (according to the MVC pattern) best regards, Frando

12 23

Administration page patch committed
by Dries Buytaert 06 Aug '06

06 Aug '06

Hello world, I committed Earl's administration page patch! Details at http:// drupal.org/node/72079. Great job, Earl. This is a big change that requires you to update your modules; you'll have to re-categorize your modules' admin pages. Earl promised to provide some guidelines to help you make the right decisions. Keep an eye on the upgrade instructions in the handbook at drupal.org. Chances are that this breaks a number of patches in the patch queue. Please take the time to re-roll them so we can continue to make progress. It's exactly 1 month to the Drupal 4.8/5.0 code freeze. Note that we're well aware that there is room for improvement so feel free to submit patches that build upon Earl's work. It's not perfect, but it is certainly a big step forward. For example, we could use some help making the administration page a tad sexier. Rock on folks! -- Dries Buytaert :: http://www.buytaert.net/

19 34

Drupal Administration survey II -- looking volunteers to do interviews
by Kieran Lal 03 Aug '06

03 Aug '06

Hello, I would like launch a second Drupal Administration Survey this week. Here is the first one: http://www.surveymonkey.com/ DisplaySummary.asp?SID=1425065&U=142506581557 I am looking for some volunteers to help re-design the survey and make sure the questions will lead to effective responses. The survey should help the Drupal development community understand Drupal users and the goal and needs of Drupal administrators. I am asking the Drupal development community to help conduct 10 live interviews to help to refine the survey questions and language A couple of notes about the survey: 1) Surveys are useful but they are not authoritative. They are frequently more useful than any one person's opinion, but not quite absolute truth. 2) Drupal administration involves many activities that are not directly dependent on the Drupal code base, Drupal core features, or the Drupal Administration User Interface. For example, Drupal upgrade documentation, Drupal module categorization, Drupal contributed modules. The survey will run past the Drupal 4.8 code freeze and the results should stand independent of any particular development release or release cycle. 3) The survey will be sent to the major mailing lists, and posted on Drupal.org home page for 45 days (August 5th - September 20th). If you know some user experience professionals who might be able to assist in the design or analysis of the survey and the survey results please contact me. Cheers, Kieran CivicSpace

3 8

LinksDB vs. Links
by Khalid B 02 Aug '06

02 Aug '06

Seems to me like this recent project http://drupal.org/project/linksdb overlaps with this one (which has no 4.7 branch) http://drupal.org/node/24719 Is flibs reading this list?

18 46

OpenID
by Dries Buytaert 01 Aug '06

01 Aug '06

Hello world, take a look at http://iwantmyopenid.org/. "Soon we will be granting $5,000 USD directly to ten open-source projects that successfully implement OpenID." I talked to Scott Kveten (CEO of Janrain) and Corey Shields (OSL) and they would be willing to wire the $5,000 USD directly to OSL so they can buy us an additional machine, something which we might need in the near future. I think this makes for a good opportunity to implement OpenID into Drupal core, and to get rid of our own distributed authentication framework. We talked about this earlier, and I believe there was a consensus about the fact we should adopt a standard. I believe that OpenID is they way to go so even without a bounty it would be of "strategic importance". Thoughts? -- Dries Buytaert :: http://www.buytaert.net/

10 10

Views argument builder
by Sam Tresler 01 Aug '06

01 Aug '06

Hi, My first post to the mailing list here. I'm thinking about starting development on a module that can create forms that in turn create a URL to feed to an existing View. A good example would be a classifieds ad setup where the Content Type is Advertisement with various fields, and the View is Search_Results, referencing those fields as needed. This module would allow an admin to create a form in which he could specify values (via checkboxes or dropdown) that, upon completion by a user, are handled in Views argument handler. So, for example, a Price field, would take the arguments max_price and min_price to return ads in a users price range. As I mentioned, I'm new, so any advice or alternate suggetions are very welcome. Mostly, I want to know if this is something people want? Thanks in advance. --Tresler

2 2

Re: Database queries on drupal.org
by Ken Rickard 01 Aug '06

01 Aug '06

I have rerolled the path_alias lookup patch, this time with a working admin. (I blame last night's failure on free OSCon beer!) This patch allows admins who have enabled the path module to go to admin/path/configure And select paths to allow lookups for from a checkbox list. Any paths not selected will not be invoked during drupal_lookup_path., These requests are intercepted within the url() function. The issue is described here: http://drupal.org/node/75976 Again, this is a proof-of-concept patch, designed to see if it buys us any performance gains. I do need some larger-scale testing, if anyone is willing. - Ken Rickard agentrickard

1 1

message_na() removed from core
by Dries Buytaert 01 Aug '06

01 Aug '06

Hello world, just wanted to let you know that message_na() has been removed from CVS HEAD. * Upgrade instructions: http://drupal.org/node/64279#message-na * Patch: http://drupal.org/node/61893 At least the following modules need to be updated: * cvs.module * evaluation.module * filtercache.module * naggregator.module * subversion.module * theme: civicspace * berkes' node_aggregator * factoryjoe's groundswell theme * killes' "speed drupal" filter.module -- Dries Buytaert :: http://www.buytaert.net/

2 1