The trigger for this was this change record for D10.1.x where two new permissions were introduced: "Delete any file" and "Delete own files".
We currently have individual per-file-type permission for the following: - [FILETYPE]: Edit own files - [FILETYPE]: Edit any files - [FILETYPE]: Delete own files - [FILETYPE]: Delete any files - [FILETYPE]: Download own files - [FILETYPE]: Download any files
In addition we have the following "global" file-related permissions (besides the "Bypass file access control" permissions, which allows every operation against any file type): - View own private files - View private files - View own files - View files - Manage or replace any file - Delete any file
This issue here is mainly about adding the following two permissions, for completeness/consistency: - Manage or replace own files - Delete own files
These new permissions would apply to all current and future file types, same as their "any" counterparts.
In addition to the above two permissions, I was wondering about the following:
1. The "View files" permission has the following description: Includes the following stream wrappers: Public files.. Should we add the same description in the "View own files" permission? (currently has no description)
2. Should we rename the human-readable names of the "View own files" and "View files" permissions to "View own non-private files" and "View non-private files"? I am intentionally proposing to use non-private instead of public, as there may be other stream wrappers that are not private, and non-private seems like a good "umbrella" term for all of them.
3. Should we rename "[FILETYPE]: Edit own files" and "[FILETYPE]: Edit any files" to use Manage or replace instead of Edit?
4. (This is the opposite/alternative of the previous point) Should we rename "Manage or replace any file" and "Manage or replace own files" to use Edit instead of Manage or replace? (in which case we can add some description to clarify that "edit" means "manage and replace")
Recent comments
In a blog post titled "Github Tips and Tricks for Contrib Maintainers", I'd like to see some of the following topics: When is the README sufficient for documentation? When should...
Github Tips and Tricks for Contrib Maintainers
Thanks Alejandro. That was the clues I needed.
Ubercart - Programmatically add product to cart and straight to Checkout
Have you tried uc_cart_add_item()? You need to provide the nid of the product. Then you can use backdrop_goto('cart/checkout'); to send the user to the checkout screen. uc_cart_add_item...
Ubercart - Programmatically add product to cart and straight to Checkout