I think most non-developer users are pretty perplexed when faced with the Date choices presented to them while adding a date field to a content type.
I am not sure what would be the best way to address this issue, but here are my thoughts so far.
- There is a need for a short description somewhere near where the user has to make this choice and due to the complexity of the Date formats possibly also a link to more detailed documentation.
- There is not enough space on the
Manage Fieldspage at/admin/structure/types/manage/foo/fieldsfor brief explanation or even a link.
One option could be to present the user only with one choice and then allow them to select one of the Date formats on the Field Settings page where there is more space to provide some brief description next to each Date type with a link to more detailed explanation.
Can anyone think of a better (easier or more user friendly) way to present this choice to the user?
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