By mattengland on

As per my failed attempt to find solutions for the problems presented in http://drupal.org/node/21712 , I made the following updates/patches to the 4.6.0 code. Here's a reference to the files:

blog-edit-control-patch-for-drupal-4.6.0-dated-2005-05-02.tar.gz

The above link comes off briefcase.yahoo.com...kind of a shabby way to do this, but I see no convenient way of uploading files to Drupal.org. :(

I've never coded a lick of php before in my life, so try to keep that in mind. (I'm a long-time C/C++ programmer, though, and php looks like it tried to keep the same syntax, so it was easy enough.)

As per http://drupal.org/node/21884 : How should I proceed with this? I'd like to get this stuff into the core/main-path code. Can someone do this for me, or should do I need to ratchet up a CVS environment/tools to do so?

Also, and more imporantly: does it look like this stuff should work? It works for me thus far.

-Matt

Comments

mattengland’s picture

mattengland commented

Notes I should have added above:

The purpose is to allow an administrator to grant which users have the ability to create and delete blog entries without allowing them to edit existing blogs. (The intent is to keep content more stable and reliable over time, particularly for business references...and in my software-development group.)

The main point: treat blog-entry posts like email: once it's out there, you can't edit it. In this case, one *can* take it back by deleting it (hence the "out")...but the only way to do this is by manually adding "/delete" to the end of the URL. I'd like to add this capability in the GUI, but that's more work then I care to do at the moment. I invite others to do this...and/or tell me how I can easily update my "patch" to do this right now?

Also: I added a "last updated on xxxx" reference for those blog entries that were updated (by authors without the above restriction), allowing readers the "awareness" that something has changed since the initial post.

Note that blog.module now has 3 different access-control settings:

  1. create own blog
  2. delete own blog
  3. edit own blog

For most of my users I'm going to try enabling the first 2 permissions will disabling the 3rd.

I suspect this may work on other nodes/content besides blog, but I have not tested this, since my Drupal site only support blogs at the moment.

-Matt

mattengland’s picture

mattengland commented

Darnit, the yahoo briefcase reference link breaks. It looks like it's not a permalink.

Is there someplace I can simply upload this .tar.gz to Drupal.org? Recommendations? (I *really* wish someone could on the file-attachment module and upload permissions so I could just do this for this forum post...)

-Matt

mattengland’s picture

mattengland commented

I made an isssue ( http://drupal.org/node/21887 ) file upload, here's a link to the file:

blog-edit-control-patch-for-drupal-4.6.0-dated-2005-05-02.tar.gz

No more briefcase.yahoo.com dependencies. Enjoy!

-Matt

mattengland’s picture

mattengland commented

As for the proper process for contributions like this: If I find time, I'll be trying to follow the procedures as mentioned here:
http://drupal.org/node/21884

Also: future requirements for this "patch":

  • Allow "meta-data" editiing (like the category of a blog entry) without changing the node core content.
  • Use a revisioning system to track changes like MediaWiki's. Alas, this is a huge requirement to implement, I would rather MediaWiki and Drupal be able to share their features (maybe with XML content "sharing") and/or just plain merge the systems somehow. This can diverge into a entirely new topic, which I may or may not pursue later.

-Matt