Let's go through an example to create this following interactive image map.
We've all been there with the character limit needs of new Drupal fields: you're creating a new content type, and based on the design, you really want to limit a field or two to a certain number of characters. You can, of course, trim the output on the display or via views, but sometimes you don't want to just trim or cut off the field - you want the author to ensure it makes sense within that character limit by enforcing it on the input end rather than just cutting it off during display!
Today I want to introduce you to the Collapse Text module. It's such a life-saver for those long, long text-heavy pages, in which it may be difficult to guide the user through the sections that are most important to them.
The Collapse Text module allows you to create collapsible/expandable sections in your Drupal pages directly from the editing interface (though it doesn't work that well with CKEditor - more on that later) through the use of special tags to delineate the beginning and end of the text section you want to make collapsible.
All of us who have been working with Drupal for a while have run into this issue: you want to disable a module that you are no longer using, but it's grayed-out on the 'Modules' tab, and so you aren't able to disable and uninstall it.
It says Required by: Drupal (Fields pending deletion)
Required by: Drupal (Fields pending deletion)
Well, you know what this means, so you go to the fields list screen at /admin/reports/fields
Want to have access to a large array of cool, creative fonts via the UI, which you can apply to a variety of CSS styles across your site? Yes, you say? Here's a step-by-step guide to using the wonderful @font-your-face module.
Have you ever created a webform in Drupal and wished you could pass some info into it? Perhaps you want to capture something about the user who's filling out the form or where they're coming from or other similar information that may be able to be passed in automatically.
Fear not! It's quite easy to pass information into Drupal's webforms through URLs. Just grab the variables from the URL, set them as defaults into your necessary webform fields, and even make these fields editable by the user, disabled (but visible) or hidden altogether. That should fit just about any need you have.
Solving the problem of systems talking to other systems has so many applications in our world of endless information. For our tutorial, though, let's imagine that we have a small form, either on an app or external site, which users can use to create profiles. We want that user submitted data to be saved on our separate Drupal site in a content type called 'bio', which has very similar (though not identical) fields. Let's get it all setup!
Drupal Commerce was made to work for selling and buying products that have a regular set price. There are many add-on contrib modules you can use to set a discount and other ways of modifying the price, but again, the expectation is that you're selling a product that does have some sort of regular base price.
Well, what if that's not the case? What if you want to use Drupal Commerce to allow users to pay the invoices they owe you, for example? In that case, you'd have a product called 'Invoice', whose price is completely unknown. One user may need to pay a $10.00 invoice, while another may owe you $230.50. Drupal Commerce can still accommodate such scenarios, but you will need to create some custom rules to make it work.
Follow along with this tutorial for one possible setup to accomplish invoice payments through Drupal Commerce.
You may be using Apache solr search on your production Drupal site (maybe even through your Acquia hosting, where it comes as a free option), but may have been testing on your local version of your site without that search option enabled. I've found the documentation on setting up Solr locally for your Drupal site a little lacking online, so here is a tutorial on how I did it myself. Now testing on my local site is easy, since my two search environments are pretty much identical!