Deprecated - Drupal core

Well, I was installing the image module and it made me create a vocabulary (I called it image). Then I added some terms to the vocabulary: icon, screenshot, photo.

By mistake I added icon twice and it let me do this. Shouldn't this be prohibited by Drupal? Is there any reason to allow duplicate terms in a vocabulary?

I've been pouring over the forums and other references for a day or two now and noodling the possible ways to make front page modification easy for people (including me!). In general, I see that a few folks are asking to be able to have a slighly modified front page. It appears at first (from the responses) that this is more than Drupal currently allows for ... but, this is not entirely the case and I feel there's a simple way around this challenge. Here's a few quick thoughts and I'd be very interested in feedback:

• Two approaches

1. Custom module (which is what I see recommended a lot)

• If using the custom module approach, a lot of Drupal and PHP knowledge is required and it still does note answer the question (for me) of how to apply a different theme.

• If using the CSS approach, then there needs to be a way to set the ID of BODY to "frontpage," from there, using descendant selectors, the layout can be adjusted (e.g. different background column images, etc.)

So, for me, the CSS route is much faster and extendable (not to mention, easier for non-programmer types)
That said: here's what I'd like to do...

• Use phpTemplate, as it the presentation and logic are separate, which makes for a nice, fast, way to skin Drupal
• Use CSS as the way to have different positioning, layout, background images, etc. for "home page" elements.

First of all, I want to apologise if this is not the place where I should put this issue or if it was already been made. I tried to use the search mechanisms but they're not working today and I also couldn't find anything similar just looking around.

I have Drupal 4.5.0 installed at home and I wanted to make some access restrictions. What I wanted exactly: I wanted that people who are not logged cannot see the Polls and the Forums, but they can see other content. Both modules check if the user has "access content" permission. But it was not enough for me, because I want everybody to have access to the other content. So, here I'll describe how I solved it and if you like you can make something similar (or tell me another easier way to do it).

1) The first thing to do was to modify the node.module, in the function node_view. I added this check in the beggining of the function. This calls the 'access' hook in the module, with the $op 'display' and only displays the node if it returns TRUE (or if doens't return --> return null):

        $access = module_invoke(node_get_module_name($node), 'access', 'display', $node);
          if (!is_null($access) && ! $access) {
            return;
          }

2) Then I had to change each module. Here I'll show what how I changed the pool.module.

a) Create a new permission, that the administrator can use to give display access to roles/users

hello drupal developers!

i've tried posting this to the list, but all of yesterday's posts are MIA, and i don't seem to be receiving any drupal-devel messages at all since.... anyway, here's my questions:

now that drupal 4.5 has integrated mo'bettah menu control in core, is it possible yet to:

* specify horizontal or verical orientation for a given menu?
* specify menu placement on a per-node/taxonomy basis?
* place menus (as blocks) into areas other than left/right; e.g., top/bottom/inset?

and if any of these don't yet exist:

I really don't have time for CVS and bug search with all the other stuff that needs to be done. Especially since it does not produce any immediate action. So I'll post my little hacks and fixes here. Anyone working in the development of Drupal is welcome to check it out when they get time.

Besides I like talking about code more than anything else and this gives me an excuse :)

Menu.inc

line 349 produces an error because the code uses a bug in array_merge to enter a value. array_merge only accepts arrays in PHP5.

original:

update:A final roadmap is now placed in the books

I compiled all battle plans into a single document that lists most mentioned battle plans. This way we can not only group our efforts better, but outsiders can see in genrel where drupal is heading and what needs still to be done.

This is only a proposal, I will not publish it in this form if anyone does not want his name released, or does not want to work in a "team". In both cases I will remove the names.
If you want to be added to a team, or want a new "project" with "projectgroup" added, please comment too. In a week from today (28 october) i ill publish this roadmap.