I am using taxonomy_access to restrict access to certain nodes depending on their access. However I am attempting to retrofit a PHP application into Drupal and I am hoping to find a way to be able to pull access levels through taxonomy_access.
For example I want to add a taxonomy vocab for something like, "Edit calendar items."
I would like to get the current user ID logged in, check if they are given access to properly edit caledar items and then give them access or deny them.
A major decision I'm facing is whether to use Drupal's "public" or "private" file download method. Does anyone have some insights into the pros and cons of each?
In my fairly common use case, most of my generic files (such as images or user-submitted files) could be public, but there are a few files I'd like to keep private (such as proprietary PDF documents or electronic products).
Here are the pros and cons of "private" file access as I see it:
I am new to Drupal, and am wondering how the different types of content like pages, stories or blogs are best used. Can you suggest the best ones for these sorts of examples:
1) Simple Journal or Diary writing like a holiday
2) For holding related information, like manuals of instructions
3) Items like film or music reviews
4) To do type items for me to remember
I would only rarely require other user input, maybe on a working project. I guess that the categories are key to classifying too. It just seems that there is a lot of choice.
I hope someone can help me with this. I'm trying to create a CCK content type that has a variable number of a set of fields- very similar to creating a custom product for the e-commerce module. The e-commerce module itself is not an option, as this does not allow for a tax deductible amounts as part of the price, nor is there an available module to integrate with our credit card processor, USA Epay.