See the Mailing lists or Drupal Issue queue. There are also various working groups on groups.drupal.org

PostgreSQL 8 upgrade; database encoding, collation UNICODE vs. SQL_ASCII

Again, Snoop InfoSystems got it running again, this time on the latest revision of PostgreSQL.

Points to remember:

node access leaves no room to check for node owner?

I've been trying to understand node access and things are starting to come together however I believe there is something missing - unless I've missed something ;)

It would seem that owners of a node lose access to a node they've created if the owner doesn't have the permission being checked for using node access. Implementing node_access_example for instance wipes out a user's blog for them since they don't have access and they can't change the private flag since they don't have access. I find it ironic that other's could view thier content but not them.

The obvious answer is to enable whatever permission the user is supposed to have to allow them to read private nodes - however I don't believe this is the way it should work.... A user should be able to read their own private nodes, without being able to read other peoples private nodes...

This doesn't seem possible under the current scheme.

It seems that this is because of the way node access works, since the grants seem to be an all or nothing thing.

Essentially unless a node is specifically allowed by having an entry in the node_access table or a user is specifically granted the correct permission for that realm they don't see nodes based on that realm...? Do I understand that correctly?

I was trying to think of way to build a module that would fake this out somehow - like create a node_access table entry each time a user adds a node, say for realm node_owner that would then have a partner hook_node_grant that granted only the actually node owner a permission - but even this seems impossible as the whole thing is wrapped up in a sql that doesn't consider each individual $nid.

Block access by role: done.

I've implemented a way to permit the visualization of blocks on per-role basis, on the CVS HEAD version. It is not a new module, but some hacks in block.module and user.module, plus a new table (block_access).
How it works:

User List / Profile

When I visit http://drupal.org/profile, I see a pretty nice layout for the profile.module called "User List." Is this a new feature that is coming in a future release, because mine looks that same (bad) no matter what theme I used. Also, the user list keeps re-sorting itself based on last login. Does anyone have a work around for this. I would like to be able to display all users in an intuitive directory type interface and there doesn't seem to be an way to do this.

Problems getting filestore2.module to work

Hi, I setup filestore2 module as outlined in the instructiosn but I get the following error when I click on teh "upload files link" under "create content"

Fatal error: Call to undefined function: fscache_is_file_stored() in C:\apachefriends\xampp\htdocs\drupal\modules\filestore2.module on line 338

Any suggsetions?

RS

Easy Edit of Page

I would like to spark converstaion and possible request a core change>

One of the reason Drupal is so powerful is the list of options a user has for each node created. Sticky, promote, read prmissions, comments, etc. But for the average "Editor" of the site I have pre-defined these options for them and just want them to edit the content.

I would suggest this:

Under EDIT:
- The first fields should be the Title, Alis, and Body
- The Submit button should be on the top not the bottom.
- All of the other features should be undrneath

Pages

Subscribe with RSS Subscribe to RSS - Deprecated - Drupal core