October 2006 - Development - lists.drupal.org

Re: [development] [support] multisite technical question
by VJ Rao 26 Oct '06

26 Oct '06

Thanks Greg. If I needed to filter search I would probably do that on a site specific level ( in the themes or with a simple module), rather than hack core..I am leaning towards doing that at this point. Has anyone tried to filter search results with a module/theming script before? I considered not sharing TAC, but right now the cons outweigh the pros. Infact, Im not so sure I want TAC anymore..I initially wanted it to make sure roles with website only permissions (as opposed to multisite content managers) dont tag content across websites..the problem though is when these guys update text on content, they will remove all the tags which the content managers had (coz lower roles dont have access to global tags) Regads, V On 10/25/06, Greg SBC <gregbjh(a)sbcglobal.net> wrote: > > I came across a similar issue with creating content. I wanted the > dominant term of a sub-site (made like yours) to be automatically selected > when creating new content from that subdomain (I also use TAC for access > control). I had to use the 'taxomony_default' modules and set the defaults > using the settings.php files, the 'conf' array. If you did something this, > then you would have to hack the search module to automatically filter by > this default term. Not simple or elegant. > > Another way is to not share the TAC tables. But then you will have to > reconfigure each subsite with the TAC permissions, which depending on the > number may be a rather daunting task. But then no hacking modules. This is a > powerful, but complex way to differentiate your site permissions. I did this > for my site at www.skejo.com. > > Greg > > ------------------------------ > *From:* support-bounces(a)drupal.org [mailto:support-bounces@drupal.org] *On > Behalf Of *VJ Rao > *Sent:* Wednesday, October 25, 2006 1:45 PM > *To:* support(a)drupal.org; development(a)drupal.org > *Subject:* [support] multisite technical question > > > Hi, > > I have a multisite install where Im sharing content (nodes) , taxonomy and > users. (I am only not sharing the following tables : menu, cache, variable, > accesslog, watchdog) > > I present content to different websites based on tags (for example > subdomain1.example.com will only present blogs tagged under vocabulary > subdomain1 , similar functionality for subdomain2.example.com etc..cross > tagged content will appear on both sites) > > The problem Im facing is with search...I want anonymous users on > subdomain1.example.com to only see content tagged under subdomain1 while > searching. > > Is there anyway to achieve this? I have installed TAC but setting > permissions for anonymous users on a per site basis is not possible... > > Is there anything else I can be trying? > > There is a way to change 'anonymous' user per site on > administer->settings...but that only seems to change the name > > Thanks, > > VJ > > > > -- > [ Drupal support list | http://lists.drupal.org/ ] > >

1 1

Drupal Modules and Linux Distros
by Seemant Kulleen 26 Oct '06

26 Oct '06

Hi Everyone, So, there's been talk for a while in Gentooland of packaging up drupal modules to offer to gentoo users. As people are probably aware, the Gentoo way is to fetch source tarballs directly from upstream sources and build on the users' boxes. Drupal modules have historically been problematic for us to package, however. The thing is we do digest checking on the tarballs to assure some level of integrity. So, once a tarball is released, we count on that tarball not changing (a change signifies something potentially sinister happened). So, I'd like to make a request to the development community here (especially authors of contributed modules): would it be possible to change tarball versions when the contents change? That would help us in Gentoo to finally bring drupal modules to the Gentoo masses. Please note that drupal itself suffers no such ailment, and we're very happy with it. I'm not sure how other distributions' packagers feel about this issue, but I'd like to help achieve a resolution here. Thanks! -- Seemant Kulleen Developer, Gentoo Linux

12 17

Re: [development] Counting .info files [Was: Documenting contribs]
by Michelle Cox 26 Oct '06

26 Oct '06

On 10/25/2006 9:43:55 PM, Boris Mann (boris(a)bryght.com) wrote: > Michelle, we may as well take this back to documentation. Myself > and > Kieran have done this over time, generally without pre-notifying > maintainers, etc.. e.g. look at Event, which has manual links to > dependent modules, etc. Although, looking at it, I took out the > "recommended" link to flexinode...and replace it to one for CCK. > > If it doesn't involve issues, it's usually best to keep it off the dev > list :P Well, it actually started on the support list... Hehe... I brought it here because I was hoping to fire up the maintainers to go forth and . I don't mind switching to docs, if that's what people want. They all show up in Mailwasher as "Drupal" to me. ;) Michelle

1 0

Documenting contribs
by Michelle Cox 26 Oct '06

26 Oct '06

I recently looked through the entire list of contrib modules and there's some cleanup needed. * Shorter teasers so the download page isn't so huge * Some modules still need tagging * Modules that are similar could use "See also's" * Also, there are a lot of modules that aren't documented in the handbook A thread on the support list went a bit off topic and I asked there what module maintainers think of having someone changing their project pages. I got one response that the maintainer would like to be notified first. I decided to put this on the dev list and start a new topic to get more thoughts on this. If you maintain modules and have a bit of time (yeah, right, eh? ;) could you take a look at your modules and see if the project pages could use a little work? If you don't have the time, do you object to someone else doing it? I'm willing to email maintainers before touching their pages if that's what's wanted. I also could use some help with this project. I've been saying I'm going to do it for over a week and haven't done it. Good intentions and all that... :) If someone wants to help, we could each tackle a part of the alphabet and then it wouldn't be such a daunting task. I'm also looking for any review/comparisons between modules to add to the handbook. If you've had to decide between similar modules and are able to write up your decision making progress, let me know. Thanks, Michelle PS: Do you think this should be crossposted to the doc list? It is doc-oriented, but I needed to put it where maintainers would see it. I don't like crossposting unless people think it's warranted.

13 22

Drupal LEGO
by Gabor Hojtsy 26 Oct '06

26 Oct '06

Hi, When I was preparing my slides to present Drupal 5.0 at the Hungarian Drupal Conference (http://buytaert.net/drupalcon-hungary-attendees) it came to me that it would be nice to somehow display the different groups of people I aim my presentation at (developers, themers, end users). Ber's LEGO association came to my mind, and thought that it would be nice to execute this somehow. Since we had some Drupal mugs around here, I decided to fill up a mug with LEGO stuff (ie. modules, themes inside :) and pick up some blue LEGO guys and girls to play the roles. Here is what I ended up with. I uploaded the original photos, but since I don't have a Pro account, the maximum you can download is 1024x768 (which is what I used for my presentations anyway): http://flickr.com/photos/72242657@N00/sets/72157594344908738/ Maybe I give inspiration to someone and we will see more like this in the future :) Anyway, I licensed the images so that you can use these in your presentations or any other stuff as long as you give me the credit and keep using the same license. Ps. my slides are downloadable from here, but since they are hungarian, I doubt you will understand the contents :) http://drupal.hu/konferencia/2006/program/drupalbemutato Gabor

5 4

Re: [development] Counting .info files [Was: Documenting contribs]
by Michelle Cox 26 Oct '06

26 Oct '06

On 10/25/2006 8:54:53 PM, inkfree press (inkfree(a)gmail.com) wrote: > "Michelle Cox" wrote: > > > This preserves the > >> > contributors' autonomy while > >> encouraging quality improvements. I do agree that the module > >> descriptions are often of poor quality. Just to be clear, I didn't write that... :) Michelle

1 0

fall
by Browning Royal 26 Oct '06

26 Oct '06

Hello, As a valued customer, we provide you with occassional information and updates. Our records indicate that you may be in need of a refill. We hope that you will once again, give us the opportunity to offer you a great selection of meds, low prices, and superior customer care. If you would like to place an order or browse our current products and specials, please visit the link below: http://videocandystore.info Yours Truly, Dr. Browning Royal brown debt videocandystore.info/fgh.php

2 1

Default core theme
by Dries Buytaert 26 Oct '06

26 Oct '06

Hello world, the past week or two, Steven Wittens has been working hard on Steef's original Themetastic. Frankly, I think we have a winner. I find it much better than Deliciously Zen or the original istyledthis.nl. The colors are perfect (good branding), and the theme has everything it needs to be bluemarine's pretty sister. The implementation is fully up to sniff to. :-) For those who haven't kept track of the recent developments, please point your browser to: http://drupal.org/node/88202 (issue) http://acko.net/themetastic (demo #1) http://www.acko.net/themetastic-fixed/ (demo #2) Is propose that we go ahead with this theme, and that we look into replacing more themes in Drupal 6.0. That gives us plenty of time to work out some of the remaining quirks, to decide what other themes to add, to engage more designers, to migrate existing themes, etc. So, I think we're going ahead with Themetastic. :) Thanks, -- Dries Buytaert :: http://www.buytaert.net/

18 31

Re: [development] More than one thread per list (was Re: Drupal Modules and Linux Distros)
by Michelle Cox 25 Oct '06

25 Oct '06

Ah, shoot, I pasted the wrong bit. Sorry, Moshe. I meant to paste the bit you said from my thread. Did my email too fast, sorry. This is the bit I _meant_ to attribute to Moshe: As an aside (i.e. lets not sidetrack this thread), one of the original visions of the new .info files is that their names and descriptions will be used by drupal.org project module. Thats one of the reasons we chose plain text .ini instead of PHP. I like reuse of .info files because it centralizes project metadata. We probably need some more metadata fields. Sorry, Michelle On 10/25/2006 3:44:32 PM, Michelle Cox (mcox(a)charter.net) wrote: > Note: I changed the topic so I > don't derail the distro thread with this > > Moshe said: > > It is sad to see this discussion side-tracked. The purpose of this > > discussion is NOT to debate why packagers exist (that is not what > > Seemant > > asked for), but to figure out how we can better cooperate. The world > > doesn't > care about your opinion about packagers; whatever it is you think > > about them, they are not going to go away. So if > you're not going to > > help make Drupal better for packagers, don't add > noise to the discussion > > either. It would be a waste of time and bits. Thanks. > > Michelle said: > > This isn't a sidetrack; it's an important point. If the current > project descriptions will be overwritten by the .info files, then > there's no > > point spending time now cleaning up the text itself. There's > still > tagging needing to be done, but I > don't want to be changing the ? > > project description if it's all > getting wiped out soon. > > Jonathan said: > >It's a good point, but it really is sidetracked from the original > >request. > >Also, you're > directly

2 1

Re: [development] Documenting contribs
by Michelle Cox 25 Oct '06

25 Oct '06

On 10/25/2006 4:12:25 PM, Earl Miles (merlin(a)logrus.com) wrote: > This is fine, but the last time I had someone 'correct' something for > me, they didn't understand what I was doing and got it wrong. So there's > something to be said for at least acknowledging the module maintainer > here. The sort of correcting I originally meant wouldn't be drastic changes. I think if the text needs substantial changes, co-coordinating that with the maintainer is a good idea. It sounds like the general feeling is that things such as tagging and formatting should just be done without having to ask first. Sound ok? Michelle

1 0