Drupal 7 tip : Get field values from entity objects like nodes, users, taxonomy, ... | Totally drupal | Dominique De Cooman
er_db_schema_drupal_7.png (PNG Image, 2553 × 2399 pixels)
This is a simple statement, but in a world of competing content management systems, it needs some validation. So why is Drupal awesome? Website Design | Drupal Development | Augusta GA | Why Drupal is AWESOME
Building a mobile app API using Drupal, Node.js and MongoDB | Mobile Drupal In February 2012 our team at ConsumerSearch launched the ConsumerSearch Reviews iOS app. This handsome app helps you during your product purchase by providing extensive product reviews, comparisons, pricing information and online and local store product availability. Try it out during your next purchase -- you'll be surprised how much time you'll save in researching the best products.
Patches This section explains how to help by finding issues to work on, creating and submitting patches. Finding issues to work on Most issues are solved by developers that have a need to have them solved, because they are impacted by the issue or they are the maintainer and help to keep their module up to date. Some developers also pick an issue of their liking and start developing and submitting a patch. The following links are collections of such issues to work on:http://drupal.org/project/issueshttp://drupal.org/patch/spotlight
This page documents a high-level overview of the current best practice recommendations for contributing change requests, in the form of a patch file, to projects (e.g., modules, themes, Drupal core, etc) hosted on Drupal.org using Git. For a more advanced workflow with Git, please refer to the Advanced patch contributor guide. Drush issue queue commands makes it easier and faster to create and work with patches. Note 1: If you're unfamiliar with patching Drupal, please read the Getting Involved section on Patches. Note 2: If you choose to create patches with a tool other than Git, be sure to produce a -p1 patch; the old -p0 format was phased out in 2011 Making a Drupal patch with Git
Classic Graphics bet big on Drupal. Our largest customers get their orders on time because we have built systems for them based on Drupal. Even though we're up to 300 employees now, with layers of management, the non-technical management still is aware that we use Drupal for custom development in part because Bryan and I heavily evangelized Drupal within Classic. Thinking ahead One of the concerns we discuss at infrequent intervals is what Classic would do if Drupal ceased to exist or if Drupal is still the best choice for doing our custom development now and in the future for the types of accounts we're pursuing. Our considerations also have to include our guesses about how the community will adopt things like Symfony or what Drupal 9 might look like.