- Development - lists.drupal.org

Schema API documentation updated
by Barry Jaspan 19 Jul '07

19 Jul '07

I have updated and reorganized the Schema API documentation, including much that I learned/clarified while making update.php work for D6. Comments, questions, and suggestions are welcome. http://drupal.org/node/146843 Thanks, Barry

2 3

Core feed publishing
by Ken Rickard 19 Jul '07

19 Jul '07

Chris- There are a number of people already working in the direction you propose, and we'd love to have you join in. Core aggregator is totally separate from the node system, so I don't understand where you are coming from. I'd encourage you to join http://groups.drupal.org/rss-aggregation if you are not already a member. We are trying to coordinate efforts in this corner of Drupal. We especially need reviewers for Aron Novak's Summer of Code work. http://groups.drupal.org/node/4624 and related. Aron's work is targeted as contrib for Drupal 5 & 6, with application for core in Drupal 7. In particular, take a look at the proposed API, which has been in the works since the last DrupalCon. http://groups.drupal.org/node/3528 and is foundational to Aron's work. - Ken Rickard agentrickard Message: 10 Date: Mon, 2 Jul 2007 23:02:14 -0400 From: beerfan <beerfan(a)gmail.com> Subject: [development] Core feed publishing To: drupal-devel(a)drupal.org Message-ID: <8de7f7140707022002ya99539fg711d32e052f63cb5(a)mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Feed publishing, and the RSS format in particular, is currently tightly coupled with the node module. Because of this supporting Atom or extending feed functionality with custom modules isn't as clean as it should be. For example, adding a name-space to a node feed requires replacing default feeds with custom feeds instead of simply "theming" the output of feeds as you would do with every other form of content display. Publishing only Atom feeds (and disabling RSS) is impossible. I would like to see feed publishing become more generic and more extensible in the core and I believe there has been discussion around this in the past. Ideally, feed publishing would be a generic module or api which would support the following needs. 1. Multiple arbitrary feed formats (RSS, Atom) with a default 2. Custom name-spaces and elements (possibly via themes or hooks) 3. Publish comment feeds or any other arbitrary content (watchdog events, users, etc.) 4. The ability to provide a feed of any arbitrary set of content (e.g., view, node-queue) 5. Optimize publishing for very high traffic feeds (e.g., caching or saving as static xml file) 6. The ability to disable feeds It is currently possibly to cobble together most of the above functionality with views.module, commentrss.module, and atom.module but the solution is sub-optimal for many reasons. I recently started creating a feed.module against HEAD with the hope that it could turn into a core module which would make feed publishing more flexible and collect all feed formatting and publishing code and eliminate the RSS publishing functionality in node.module. However, since 6.x was just frozen there's probably no hope of introducing this now but I'd still like to re-float the idea and get some feedback. In particular, I'm curious if anyone else is already working on such a project, if there are any side-effects of separating feed publishing from node.module that I haven't considered, or if this problem might be better approached using views as the complete solution (not really viable since views is not a core module). Please ignore the fact that this can't be implemented for 6.x. As an example of an issue I have faced, feedburner.com adds a "number of comments for this entry" if the feed includes the "wfw:commentsRss" element pointing to the comment feed for the entry. I have modified the commentrss.module to add the element to the node feed but there is no way to add the "wfw" name-space to the node feed without replacing it with a custom feed so I had to add the name-space to each instance of the "commentRss" element. Cheers, Chris Cook

4 3

req: role-specific content in pages
by David McNab 19 Jul '07

19 Jul '07

Hi Drupal devs, In case there's anyone with a bit of spare time coming up, and open to ideas, I've had a thought for what could be (for some) a very useful module. The idea is to have parts of a node marked-up to be visible only to certain roles. This could be achieved with certain SGML-like markups in the node body. For a silly example: <h3>Sale! All boots 35% off!</h3> <restrict role="retailer"> <p>We've picked up a big consignment of factory seconds from China. Faults are very minor, but we can't exactly charge full price for them. Otherwise, they're nice lines, and you should turn them over no problem. When you order stocks, please quote discount code #CNS4414</p> </restrict> <restrict role="admin"> <p>FFS Ian! Get off your butt and fix up those order screens!</p> </restrict> <restrict role="manager"> <p>Sleep easy, Caitlin, we'll get 'em off your hands. You could even come out a bit ahead.</p> </restrict> Grab them while they last from your nearest retail outlet, or <a href="order">order them online here</a>. Thoughts? Cheers David PS - My PHP is way rusty (switched to Python 5 years ago), and I'm just starting to learn the Drupal API. Otherwise I'd have a go at it myself.

5 7

use drupal as a backend?
by bryan rasmussen 18 Jul '07

18 Jul '07

Hi, Not sure if this is the right group to ask this in, but it seemed like the other drupal groups were even less relevant: a friend of mine recently wanted me to help him do some stuff for his new website. Basically it was clear what he needed was a blogging tool (he has the content managing needs of a normal blogger and the Website desires of a Fortune 500 CEO) one of the things he wants are very specific design requirements that I do not think is implementable in any blogging tool currently. The display requirements are as follows: The first page of the site is a single column menu, pages aside from the initial single column start page can have up to four columns: Column types are: 1 - always menu 2 - documents of a particular type or a submenu 3 - documents of a particular type or a submenu 4. documents of a particular type so one scenario could be that there are four columns on a single page consisting of | menu | submenu1 | submenu2 | document considered to be under submenu2 another scenario could be |menu| submenu1| document or |menu | document| The content handling requirements are as follows: 1. calendar manipulation - add, delete, read events 2. Forms to send contact email 3. serving of various streaming media 4. easy to maintain without needing to be technical after quite a bit of work got the display working in xhtml / css but now need a way to maintain this. I have the idea that the data of the documents in the non-menu columns could be gotten just by reading in data from some blog installation on the server. I think the best solution would involve a blogging tool that could output content as just XML and that I could then read to build up the exact display he wants. I figure, given his server restrictions (php, MySQL), that drupal is probably the most likely solution to this. Any suggestions on things to look at with Drupal to maybe do this? If not drupal other tools suggested in the blogging world?

6 6

Add image node with PHP Curl?
by James Tunick 17 Jul '07

17 Jul '07

I have read a lot about about the topic. But I'm still a newbie and I'm having serious trouble. After using PHP/Curl to login, I move to the node/add/image page and get the token no problem. But I'm having trouble posting a new image node. I can get everything working when posting a new page node with Curl. It's just posting a new image node that's giving me trouble. Here is the code that should add the new image node. Curl fills out most of the image form fields such as title, body etc. All fields are populated by Curl *EXCEPT* the image file upload. And this seems to be what's stopping curl from creating the new image node. What am I doing wrong? How can I get Curl to fill in the file upload field? Any suggestions much appreciated! $ch = curl_init(); curl_setopt($ch, CURLOPT_HEADER, 1); curl_setopt($ch, CURLOPT_RETURNTRANSFER,1); curl_setopt($ch, CURLOPT_COOKIEFILE, "cookie.txt"); curl_setopt($ch, CURLOPT_URL,"http://www.example.com/?q=node/add/image/"); curl_setopt($ch, CURLOPT_POST, 1); $postarray = array( 'files[image]' =>'@$file', 'taxonomy[3]'=>'2', 'title' => $file, 'body' => 'xxxx', 'status' => '1', 'revision' => '1', 'comment' => '2', 'name' => 'mov', 'moderate' => '0', 'form_id' => 'image_node_form', 'form_token' => $token, 'op' => 'Submit' ); curl_setopt($ch, CURLOPT_POSTFIELDS, $postarray); $buf2 = curl_exec ($ch); curl_close ($ch); I have reviewed the tutorials and snippets on the Drupal site (http://drupal.org/node/87711) and on other sites (http://www.voidberg.org/blog/using_php_and_curl_to_automate_drupal_tasks_su…)

3 2

how to right AJAX enabled module?
by Ahmad Al-Obaidy 16 Jul '07

16 Jul '07

Hi, I need to display a value given in the database.... the value is modified regularly by other programs.... the value should be refreshed regularly .... but not the entire page... I tried JSON ... but didnt find a useful docs.. from where should i start?

2 4

seen Druplicon?
by Augustin (Beginner) 16 Jul '07

16 Jul '07

Where is the appropriate place to report funny bugs like this: [18:15:31] <beginner2005> seen killes? [18:15:32] <Druplicon> killes was last seen in #drupal 2 days 17 hours ago saying 'you should even be able to only enable it for specific domains.'. [18:16:23] <beginner2005> seen Druplicon? [18:16:23] <Druplicon> I'm right here! [18:16:24] <Druplicon> Sorry, I haven't seen Druplicon. [18:16:36] <beginner2005> :) which one is it, then? augustin. -- http://www.wechange.org/ Because we and the world need to change. http://www.reuniting.info/ Intimate Relationships, peace and harmony in the couple.

3 2

ANN: module 'PyBridge'
by David McNab 15 Jul '07

15 Jul '07

Hi Drupal hackers, As someone who loves, admires and respects the fine framework that Drupal is, yet much prefers Python over PHP as a programming language, I suspect I may not be alone. So as an experiment, I've created a module called 'PyBridge', which allows simple Drupal page modules to be written in Python. Module and doco are available from: http://www.freenet.org.nz/pybridge The basic idea is that after installing the module, you can place python modules (say, 'hdlr_fred.py') in a directory, and these will be available via the path 'pybridge/fred'. Within the python module, you can access nearly all the drupal API and globals; I've exploited some Python OO voodoo to make this easy and transparent. The Python module gets spawned via popen, and function calls, variable gets/sets etc are done as a flow of serialised command packets to/from the python process' stdio. You can: - get/set PHP locals/globals - arrays, numbers, strings - call PHP functions - PHP builtins and Drupal API funcs - execute arbitrary PHP expressions and code (and yes, folks, I've included a whole section of security precautions to help people mitigate the risks of this) - return a string, which will be taken as the page content You can't: - retrieve PHP objects - but you can retrieve their attributes and invoke their methods Performance penalty is moderate but not over the top. URL aliases can be used to render the ugly 'pybridge/fred' URIs into something nicer. If this interests anyone, I'd love to hear from you. For someone with good PHP and Drupal API knowledge, this could be spruced up into something quite nice. For example, adding configuration options. Cheers David

2 1

GoPHP5.org - Drupal 7 and PHP 5.2
by Robert Douglass 15 Jul '07

15 Jul '07

Hi all, after coordinating with Dries I am happy to announce that Drupal 7 will be able to accept PHP 5.2 features into core! To celebrate Larry Garfield, Ken Rickard and myself have launched http://gophp5.org. Please check it out and spread the word. <begin rejoicing> -Robert

17 25

Documentation proposal: Forms
by Earl Miles 14 Jul '07

14 Jul '07

I would like propose that Drupal 6 (and forward) adopts the following documentation standard: For all functions that are meant to be used in as an argument for drupal_get_form, we document them with @ingroup forms (note that actual form code is documented via @ingroup form) and we put a description of what the form is meant to be used for. That will make it a little easier to for users to discover what forms are available and find their way to the code that generates the forms. (Could also use volunteers to help apply documentation patches to get this done).

4 5