Deprecated - Drupal core

So, I have been reviewing modules left and right recently, and I am seeing a lot similarities in

• Taxonomy Access Control
• Node perm by role
• Workflow
• Organic Groups

These modules are fantastic on their own, but are difficult if not impossible to combine. The problem, as I see it, is that they are each recreating the wheel. Specifically, they are trying to emulate the taxonomy system, each with greater and lesser degrees of success.

Please, take it this post as something that tries to be constructive.

I've been trying to catch and report bugs, providing the patch when I thought I knew how, maybe expecting a patch was reviewed in a few days and then, if correct, committed to head, but that doesn't seem to happen and the issues remain in the same status. And not ony about the patches I have provided, the patch queue is growing and growing...

May I ask where is the bottleneck? Is there anything else that we can do to help?

Hello,
I am intending to use Drupal for a Corporate document repository but I have a minor problem which I would like assitance to resolve. When a user creates content the system provides the facility to track versions. This is excellent, but if the user then deletes the content, then the complete document appears to be physically deleted from the database, and this is not suitable for a versioning system.

What I would like to know, how would I remove or deactivate the delete button so that content cannot be deleted?

Alternatively, the Delete function should only be available to the Admin user as a structured system clean-up. When a user deletes content the system should flag the content as deleted and reflect this change, not physically delete the conent from the database.

The second point related to this is that there is a module called Archive, but as far as I can tell this only displays the content that was created on the selected date. The word Archive conjurs the image of removing content from the site and making it available as a separate search option. If the delete button was to flag the content as deleted, then I would expect using Archive would allow me to see what content was deleted.

Unfortunately I am not a programmer, but at the least I would like to limit or remove the delete button from general use, and at best I would like all deleted content to be treated as a new revision and a status flag set to indicate the content as deleted, rather than the content being totally deleted from the database.

originally posted in "book" re: how to upgrade modules from 4.6 to 4.7; but not sure what visibility that gets so thought i would re-post here

===================================

I am a little new at this so bare with me...

...but i have read through the node changes listed above and i don't see where it is mentioned that node_submit() now returns $node where in 4.6 it returned $nide->nid

node_submit also doesnt seem to do a validation anymore????

or perhaps i should not be using node_submit now???

I've noticed that basically all nodes that allow comments have 2 urls:

site.com/node/45 and
site.com/comment/reply/45

that show identical content and both get indexed in search engines (which is no good).
To me this doesn't make sense. Any idea if this has a certain reason?

i am new to drupal...When i tried to create taxonomy for categories -navigation blocks like in http://drupal.org/node/47623

The deafult drupal installation only had taxonomy.module..Now i added taxonomy_blocks,taxonomy_association,taxonomy_menu ..even now i cannot create such blocks..

Should i inlcude all these modules for it