- Development - lists.drupal.org

NNTP and Adservers ??
by Dan Horning 31 Aug '06

31 Aug '06

Yea i know those are two very different things - however they have one thing in common - when not made right they can break any website.... I've got some unique needs and it'd like to start some development on those two modules simply defined as follows (both would of course remain fully free and publicly available. if you're interested in helping or know of other development in progress please let me know - i plan on starting the adserver first and then working on the NNTP (currently planned with or w/o the bar.baen site picking this) NNTP/Mailgateway (unpaid project for bar.baen.com - talking about replacing the system they have with drupal) -- allowing for threaded posting of comments and the ability to subscribe to taxonomies and maybe forums also -- this must also have the ability to control access to the nodes just as roles and na_arbitrators do (use their data if mods available) -- more spec needed... Adserver (small but paying project) -- simply put we need to be able to show any ad on a page spot of any size w/o limitations -- basic impressions / clicks data would be nice but not at all req -- would like the logic for displaying the ads built into the page view itself - allowing the end user to place blocks anywhere and within those blocks set simple random rotations of any number of ads. -- the hard part is doing this without repeating any ad show on a particular page (ie.. if there are 5 available ads for an area - an there are 8 spots open in the block setups it will only show the total of five balanced across the available space. it is key that the dimensions are not a factor - call it non-idiot proof but it's a needed option for the targets. - dimensionally controled spots also would be good... ) -- the ability to assign types to the blocks -- Dan Horning - danhorning.com American Digital Services - americandigitalservices.com Where you are only limited by imagination. 1-866-493-4218 (direct) / 1-800-863-3854 (main number)

4 5

is this an attack?
by VJ Rao 30 Aug '06

30 Aug '06

200.3.144.42 - - [30/Aug/2006:10:02:37 -0400] "GET /es/taxonomy_menu/3/100/55/es/taxonomy/term/567/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/feed HTTP/1.0" 200 11989 "-" "Mozilla/4.0 (compatible; Google Desktop)" "PHPSESSID=ac3446852461e364119497993e46a106" -v

5 4

RE: [development] is this an attack?
by Metzler, David 30 Aug '06

30 Aug '06

Maybe, but it looks more to me like a broken rss aggregator is hitting your site, usually the attacks start trying mal-formed urls pretty quickly. I'd look arround the logs and see if I saw hits of a slowly building URL based on the feed. If that's the case it's more likely the broken aggregator, but if you start to see malformed url's, I'd be thinking attacks. Dave ________________________________ From: development-bounces(a)drupal.org [mailto:development-bounces@drupal.org] On Behalf Of VJ Rao Sent: Wednesday, August 30, 2006 7:12 AM To: support(a)drupal.org; development(a)drupal.org Subject: [development] is this an attack? 200.3.144.42 - - [30/Aug/2006:10:02:37 -0400] "GET /es/taxonomy_menu/3/100/55/es/taxonomy/term/567/all/es/taxonomy/term/fee d/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/te rm/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxon omy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es /taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/ all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term /feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonom y/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/t axonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/al l/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/f eed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/ term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/tax onomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/ es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/fee d/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/te rm/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxon omy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es /taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/ all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term /feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonom y/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/t axonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/al l/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/f eed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/ term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/tax onomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/ es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/term/fee d/all/es/taxonomy/term/feed/all/es/taxonomy/term/feed/all/es/taxonomy/te rm/feed/all/feed HTTP/1.0" 200 11989 "-" "Mozilla/4.0 (compatible; Google Desktop)" "PHPSESSID=ac3446852461e364119497993e46a106" -v

1 0

cache API changes
by Dries Buytaert 30 Aug '06

30 Aug '06

Hello world, I committed Gerhard's cache improvements. We split up the giant cache table in smaller cache tables: http://drupal.org/node/72290 As a result, the cache API (cache_get, cache_set, cache_clear_all) changed and contrib modules will have to be updated. -- Dries Buytaert :: http://www.buytaert.net/

2 1

Google Summer of code form builder project to be continued
by Kieran Lal 30 Aug '06

30 Aug '06

Hello, Avi Mehta has agreed to continue working on his Google summer of code project for CivicSpace. The project is going to continue to be mentored by Nedjo with support from Jeff Robbins. The forms API has been a major innovation for the Drupal community, but it is only accessible to a small amount of developers who can speak "hook_form_alter". If you are interested in driving this innovation to next level of administrators and end users please contact me so that we can collaborate and help finish the form builder project. We believe this project could have a significant impact to improve the administrator user experience. http://drupal.org/project/formbuilder If you have time to commit to mentor or collaborate on this project please contact me. If you are interested in funding the completion of this project I am happy to connect you to developers who have expressed interest in doing further development for hire independently. Cheers, Kieran

1 0

Looking for patch love
by Dries Buytaert 30 Aug '06

30 Aug '06

Hello world, there is a patch that attempts to clean up the node submit hooks: http://drupal.org/node/68418 Simarly, check out the profile rendering changes at: http://drupal.org/node/79227 It seems to make for a new API trend so we better take the time to think this through. Personally, I've mixed feelings about it so I figured I'd bring this up on the mailing list. Here is what I think: Advantages: - No disconnect between the regular flow (through forms) and a programatic flow. Less prone to errors, improved APIs to do thing programmatically. Disadvantages: - Improved consistency, but not ultimate consistency. Most things will continue to use the "old style" worfklow (and hook mechanism). - Not always easier to use or easier to theme. Not exactly elegant either -- often very verbose. - Expensive in terms of processing cost. Performance matters a lot and unless we make Drupal faster, we won't see bigger and bigger Drupal site. Let's weight the advantages and disadvantages, and lets figure out some practical use cases. When discussing, stick to the topic at hand and avoid wandering off to Meta Land to discuss the way we do things in general, or how we should do things. This is a _technical_ mailing list, and I'm explicitly asking for a _technical_ discussion on this matter. Don't bother responding unless you spent at least 20 minutes poking at the above patches, or unless you tried an example or two. Take the time to investigate this, be critic, and share your own opinion rather than repeating what others have said (without having looked at the patches yourself). There, I've said it. :) -- Dries Buytaert :: http://www.buytaert.net/

3 6

site listing addition request
by Laura Scott 29 Aug '06

29 Aug '06

I'm writing to request the addition of pingVision on the Drupal services page. Our team includes myself (doc maintainer, patch tester, issue filer, forums participant, email participant), Rich Orris (developer) and Greg Knaddison (developer, patcher, doc maintainer). Since I am a member of the documentation team, I added the page itself. In the recent changes to handbooks permissions, I did not realize the post would be approved automatically, but I see that it has (http://drupal.org/handbook/updates) But I don't want to do an end-run around community protocol, so I'm writing here with a formal request. Thanks! Laura

2 3

multisite
by VJ Rao 29 Aug '06

29 Aug '06

Hi, If I want to share users and data across multiple sites (If there is any need for control, I plan to use TAC) ..which tables should I create as unique for each website (i.e with prefix)? I can think of 'variable' . Does any other table need a prefix? If not, I can just do : $db_prefix = array( 'default' => '', 'variable' => 'site1_' ); in sites/site1/settings.php.. right? Regards, V p.s I dont use left navigation

1 1

node options behaviour on editing by non-admin user
by Alan Dixon 29 Aug '06

29 Aug '06

I've just posted a small patch to the node.module that would preserve the node options properties ('status', 'promote', 'sticky', 'revision') when a non-admin user edits their post (current behaviour is that these properties revert to their system defaults). This change was requested by a client and I think it's worth considering for drupal's core. Details at http://drupal.org/node/81314 -- Alan Dixon, Web Developer http://alan.g.dixon.googlepages.com/

1 0

Configurable content types in core
by Neil Drumm 29 Aug '06

29 Aug '06

I committed the first part of Content Creation Kit, configurable content types, to core. Here are some next steps: - Test and find the bugs that we haven't found yet. - Make book, blog, and forum types work with only configurable content types. - Documentation (I've had a hard time explaining this). - Start moving fields module towards core, only 4 weeks left. On fields module, I haven't looked at it much recently, but I'm guessing I'll make the same request I did of content module, merge it into node module. I'm not 100% sure of this quite yet, since not as many people will have custom fields. If a feature is basic functionality which most people will use, prefer adding it to the most logical module (and conditionally including any appropriate code), instead of adding another module. If a computer can decide if code needs to be included or not, it will probably be smarter than a user. The real question is, should we have fields always be configurable or should the be a global switch (a module) to turn them off? -- Neil Drumm http://delocalizedham.com/

12 16