Coding Horror: New Programming Jargon
A Duck
A feature added for no other reason than to draw management attention and be removed, thus avoiding unnecessary changes in other aspects of the product.
A Duck
A feature added for no other reason than to draw management attention and be removed, thus avoiding unnecessary changes in other aspects of the product.
We are still responsible for adding the additional products to the user's cart when selected. We do this by adding custom submit handlers to the form. In this case we add two custom submit handlers, one before the standard one to clear the cart in case there's anything else in there, and one after where we add the selected optional products.
* Choose a range of content types and taxonomy vocabularies.
* Results are sorted by relevance (number of matching terms).
* Select which node view mode to use for results display.
* Define a set number of results shown (defaults to 5).
* Results can be shown as a cycle slideshow. (http://jquery.malsup.com/cycle/)
* Optional "More link" can be appended to the bottom of the bean.
In the end, one argument against using Views for our content queries overrode all others: we wanted our client to use Views. Our client had specified that once they received the sites, their own developers would be using Views to build blocks and pages themselves. We knew that if we worked in Views for our own work, the Views we created would eventually be exposed to them, which leads to possibilities of regression and error. We wanted our core querying functionality to continue to function without concern that it might be tampered with.
wondering why I wouldn't just build this in Views. Indeed, this might look a bit masochistic if you're used to Views. However, there are a few things to consider:
EntityFieldQuery is core. If you are interested in keeping your installation as lean as possible, this is something to consider. Views is a contributed module, and so it automatically adds size and overhead to your Drupal install.
The GeShi Filter module provides a filter for source code syntax highlighting for a wide range of languages.
Source code can be entered with for example ... or .... Automatically adding line numbers is possible too with for example [ruby linenumbers="normal"].