- Development - lists.drupal.org

access control for periodicals - does my plan make sense?
by Dave Cohen 24 Sep '06

24 Sep '06

Looking for some advice and ideas.... A client is publishing a periodical online. Only paid subscribers will have access to the nodes that are part of the periodical. Subscriptions are not necessarily continuous. So for example a user might subscribe in 2006; not subscribe in 2007; then subscribe again in 2008. In 2008, such a user should be able to view content from 2006 and 2008, but not 2007. I have a flexible system in mind; in which each subscription has a start, end and expiration. Whether a node is visible will depend on whether its creation date falls between the start and end of a subscription. My question is not about this part, but about how best to hide the nodes that the user has not paid for. I do not plan to use "standard" access control; that is, the node_access table and grants, because I don't see how to cleanly map a subscription start and end date to a grant id. But that's OK because I don't need to entirely hide the existence of these nodes. I just need to hide the full contents of the node. So my plan is to put some logic in hook_nodeapi. If $op == 'view', and the user has not subscribed to the node in question, I can do something like: $node->body = t('Sorry, you have to subscribe to view this.'); I'm writing to this group because I think is a reasonable approach, but I'm not sure. Any thoughts or suggestions? Thanks, -Dave

3 5

Can not upload new module
by Drupal Indonesia 22 Sep '06

22 Sep '06

First, apologize me if my question too simple. I have created CVS account and approved. Now I want to upload my new module. I am using SmartCVS, what should I enter in: - Access method: pserver, sserver ot ext - server name - repository path regards.

4 6

hook_update_always
by Dave Cohen 22 Sep '06

22 Sep '06

Is it possible to perform some action every time the update.php script is run? I'd like my module's hook to be called each time, but I cannot figure a way to do it. I've tried returning '#finished' => 0, from my hook_update_N, but that results in an infinite loop each time update.php is invoked. (Is that a bug or on purpose?) This is drupal 4.7, BTW. Thanks, -Dave

2 3

RE: [development] Indymedia and Drupal
by Steven Peck 22 Sep '06

22 Sep '06

Also, they have a group http://groups.drupal.org/indymedia > -----Original Message----- > From: development-bounces(a)drupal.org > [mailto:development-bounces@drupal.org] On Behalf Of Dries Buytaert > Sent: Thursday, September 21, 2006 1:46 PM > To: development(a)drupal.org > Subject: [development] Indymedia and Drupal > > Hello world, > > might be of interest: > > http://buytaert.net/indymedia-and-drupal#comment-580 > http://techmeet.sarava.org/English/CMSSurveyReportDrupal > > -- > Dries Buytaert :: http://www.buytaert.net/ > > >

1 0

Multi-site absolute paths?
by Sam Tresler 22 Sep '06

22 Sep '06

Been following a forum thread and was wondering if anyone had any input towards a way to make multi-site pathnames more manageble Thread: http://drupal.org/node/84895 The basic issue is that pathnames for a multi-site install can easily get huge. But there is strong desire to keep all site-relevant material in the /sites/sitename folder. Suggested fixes were symbolic links from drupal root direct to, say, the files folder, but that isn't portable to Windows, gets unwieldy with many sites, and doesn't account for the sites/themes and sites/modules folders. Example situtation. One codebase - two installs. CSS absolute path to background image. http://example.com/sites/example.com/files/images/background.jpg it gets worse with subdomains... http://test_layout.example.com/sites/test_layout.example.com/files/images/b… Does anyone know a good portable workaround? Am I missing something obvious? -- Sam Tresler sam(a)treslerdesigns.com

5 7

Indymedia and Drupal
by Dries Buytaert 21 Sep '06

21 Sep '06

Hello world, might be of interest: http://buytaert.net/indymedia-and-drupal#comment-580 http://techmeet.sarava.org/English/CMSSurveyReportDrupal -- Dries Buytaert :: http://www.buytaert.net/

1 0

Drupal multi-lingual meeting
by Dries Buytaert 21 Sep '06

21 Sep '06

Hello world, if there are Drupal people in Brussels that want to brainstorm a little about multi-lingual Drupal sites (and how to get i18n into Drupal core), feel free to join us at GovCamp tomorrow: http://govcamp.org/index.php/Main_Page http://govcamp.org/index.php/GovCamp_Brussels We'll have a dedicated Drupal brainstorm room from 16:00h to 18:00h. Afterwards, we'll go for drinks in The Wild Geese: http://drupalcon.org/node/14 Latest updates at: http://drupalcon.org/ -- Dries Buytaert :: http://www.buytaert.net/

3 2

tango icons
by Farsheed 21 Sep '06

21 Sep '06

Hi, I have a question. I believe this was discussed before, but I'm still a bit fuzzy on the topic. Are Gnome Tango icons off limits for including in Drupal themes? http://art.gnome.org/themes/icon/ The Tango icons here say they have a Creative Commons license, but Gnome is a GNU/GPL project as far as I can tell. So...since they are distributed with GNU, we can use them with Drupal right? Farsheed __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

3 2

code names for core releases? (was Re: Suggestion for people releasing new modules and themes into CVS)
by Derek Wright 21 Sep '06

21 Sep '06

[this topic deserves a new thread] 1) code names *are* a developer-ism. yes, all problems in computer science can be solved by either caching or adding another level of indirection, but in this case, the indirection is sort of a pain in the ass, and can also lead to confusion, as much as it might help some people. 2) it seems like only a handful of releases are ambiguous about what the next version # is going to be. now that we *know* 5.0 is the next release, i'm positive the next one will be 5.1, not 6.0. so, for 5.1, a code name is just needless indirection and alternate (therefore, probably confusing) naming. we're not going to want to mark issues in the issue queue "blue" or "salamander", (which *would* be an improvement over "cvs", but still), we're going to want to mark them as "5.1.0-dev" (just like the version string in system.module)... 3) given that there are really only a small # of releases where this is a problem, i don't see much harm in using "4.8/5.0", or even, calling it "4.8.0-dev" until proven otherwise. not ideal, but better than "cvs", "TRUNK", or "development version". <goes-out-on-limb> 4) can't dries make this decision a little earlier? ;) yes, some things might change, but it seems like we're going to have a pretty reasonable idea of what's going to happen further in advance than the code freeze. given that both digits are officially part of the "major version" (according to http://drupal.org/handbook/version-info "X.Y indicate the current major stable release version."), it doesn't *really* matter that much if it's 5.0 or 4.8. ;) we never worry about compatibility between "minor" release numbers, so it's not like we have to wait on 5.0 vs. 4.8 until we know for sure if it's still compatible with 4.7 or not, etc. it's entirely arbitrary, and the fact is that be delaying the decision, we're creating all this unnecessary confusion. </goes-out-on-limb> this all has relevance for the new release system, storing releases as nodes, etc, which is part of why i care. anything other than "cvs" or "next release" would be an improvement, so i won't put up too much of a fight if people are really set on the code-name thing, but i'd rather we just stuck to numbers, and in the small handful of cases where there might be 2 possible values, either a) just decide early and stick with it -- no one's going to die or get fired or become homeless if dries calls it (X+1).0 or X.(Y+1), b) call it "A/B" until it's decided, c) keep calling it X.(Y+1) until proven otherwise (which will only happen every once in a while)... thanks, -derek

8 11

RE: [development] code names for core releases?
by Nelson, Curtis 21 Sep '06

21 Sep '06

> I guess it's obvious I'm in favor of codenames, andrew > > [1] http://en.wikipedia.org/wiki/Color_of_the_bikeshed And so the first codename becomes "bikeshed"

7 11