Deprecated - Drupal core

There should be additions to the changelog made whenever a bug is fixed or when a previously not working function is brought up to working status. This would decrease the amount of double posting of bugs. People are not getting hits on their bug searchs because of the wording used to report them and the way they encounter the bug. The changelog updates should be weekly at the very least.

I've been looking through common.inc, and am puzzled by the fact that the form_checkbox code makes a call to form_hidden, which as far as I can tell leads to any checkbox tag being preceded by a hidden tag that defines the same variable. I can't come up with a reason for this behavior---I would assume that it is illegal or at least ill defined to have an html page where the same input variable is defined twice. And I am also suspicous of the fact that this form_hidden call is not invoked on any form creation function call other than form_checkbox.

hi,

i've just completed a new site for European Digital Rights. since they are a security and privacy conscious organization, they are questioning the need for cookies for anonymous users.

i assume that the php session cookie is needed for tracking a session for logged in users, but why is it created for anonymous users? am i right that this cookie gets created when 'session_start()' is executed? is there a way to modify the code to only send it to the browser when a user logs in?

I have been exploring JonBob's excellent modules for providing granular access to nodes, and indeed currently have nodeperm_taxonomy in use at my site. However, it doesn't really provide the correct default behaviour for my users who don't know what they are doing, so last week during a long plane ride, I gave some thought to a slight variation on functionality, and might perhaps try and create a module that performs that way (and from looking, but not yet understanding the code in detail - I suspect this can be done without patching) as a contribution (although I am sure I will have a steep learning curve here). I would welcome comments on the functionality suggested below.

The module - lets call it the "Access" module will provide an administer function. This will be used to set the default access rights to any node based on a users role. It will have one drop down list box per role currently defined, with the following 5 options

No Access
View Node
Comment on Node
Edit Node
Delete Node

These defaults (and any changes - see below) will apply to Non Authors - I assume Authors will always have Delete rights

This is all this administration module will do.

There will also be an entry in the admin/user/configure/permission function which provides two lines to the permissions per role check box list (a check in the box enables this). Those two lines will be

Hi all,
in my opinion a necessary feature on taxonomy should be node type filtering; in the case one vocabulary is used by many node types (for example a topic could be used for stories and forums), actually there is possibility to filter out ONLY forums on that argument, but, selecting nodes based on that topic Drupal shows both stories AND forums related to that topic.

In the past, several hacks were made to accomplish such a feature, but none of them works with the new 4.5 RC, where taxonomy syntax changed significanlty.

My proposal could be to enhance the new taxonomy syntax as follows:

taxonomy/term/term_1+term_2/

this would filter nodes relate to term_1 or term_2.

taxonomy/term/term_1+term_2(type1+type2)/

this would filter nodes relate to term_1 or term_2 but with node_type='type1' or node_type='type2'.

taxonomy/term/term_1,term_2/

this would filter nodes relate to term_1 and term_2.

taxonomy/term/term_1,term_2(type1)/

this would filter nodes relate to term_1 and term_2 but with node_type='type1'

Depth and the eventual final '/feed' parameter would remain the same, preserving the new syntax.

Obviously, not specifying node_type filtering, Drupal selects all node types related to the specific tids.

I found the place in taxonomy module where to add node type filtering, and I would be glad to know your opinions before working on a patch to accomplish this feature, that could be inside 4.5.

I'm trying to track down a bug in my 4.5 installation. In the original post for forums, the number 1 is mysteriously appearing and I can't find it in the code. Here's the code snippet:

<!-- begin content -->
  <div class="node ">
    1
     
    <span class="submitted">Submitted by 

Any ideas on where to look would be appreciated.

-Robert

------
visit me at http://www.robshouse.net