With Drupal 7 right across the nook, I have lately positioned myself to the duty of ramping up on what is new, what’s modified, and what do I as a module developer wish to know once I sit all the way down to code my first Drupal 7 module (or improve one of my D6 modules *shameless plug*). I’ve spent the previous few weeks scouring over the Drupal 7 core and API documentation, and allow me be the first to inform you if have not heard it yet (unlikely): higher times are ahead. For all of us. The volume of API adjustments from Drupal 6 to Drupal 7 are wide and sweeping. Drupal 7 is for sure still Drupal, which means that it nonetheless feels and acts like Drupal. Nodes are nonetheless nodes that can have taxonomy and comments, customers are still customers with roles and permissions, so on and so forth. But nearly everything underneath the hood and within the UI, for that subject, has been advanced upon and/or re-factored. From a coders point of view, I am quickly to be in developers heaven while Drupal 7 is going stable. From the standpoint of being a framework, Drupal 7s API is more mature and modern. You might want to virtually bring to mind Drupal 6 as a kid in top-college and with Drupal 7 that child has graduated and is now in a position for the actual world. The refactoring that has taken place over the last couple of years and the entire new options now available will likely be a boon for module and subject matter builders alike. This additionally explains simply why now we have had to wait see you later for a stable release. . .
This article would be the first in a sequence exploring Drupal 7s API. For this article (itself a two-phase series), I wish to talk about what I think, as a developer, is probably the most considerable and important change to the Drupal core. The new database abstraction layer (or DBTNG Database: The Subsequent Generation) is a whole overhaul of the database layer now we have grown familiar with in variations Drupal 6 and before. Built on PDO, the database layer in Drupal is now truly abstract, which means that it is database agnostic. This provides Drupal the flexibility to run on any selection of other systems with no need to write new code or modification any present code that interacts with the database. This additionally signifies that we will be able to expect to look much more undertaking-level Drupal sites once Drupal 7 hits strong because its footprint within the corporate global will now be able to develop substantially. So, permits see what all this means. First and foremost, gone are the days of getting to write ludicrously long and complex MySQL or Postgres dependent SQL statements to fetch or write data. Long gone are the times of getting to outline your placeholders type. And gone are the days of getting to worry about what may happen for your data if an insert or update query failed in the middle of executing (yes, we after all get to make use of transactions!).
Allows soar proper in and start with fundamental SELECT queries in Drupal 7s new database layer. Drupal 7 introduces us to the ideas of static and dynamic queries. Static queries are queries that get handed to the database as is, which means you question the database with a SQL string you write. Dynamic queries are built by means of Drupal using a query object and that question items methods. A couple of fundamental examples might assist illustrate the difference. Record dealing with has also been improved. Particularly, one real flaw with Drupal 6 was once it’s incapability to implement non-public file coping with (for security functions) and CSS report aggregation on the similar time. The issue was once moderately severe as a result of without CSS file aggregation, greater web pages may just holiday in Internet Explorer as a result of its inability to take care of huge choice of CSS file. The other used to be to set document dealing with to public and run the danger of storing private or industrial files within the document root. Glad that is over with…
General, I can’t look forward to a stable Drupal 7 release. A lot of the options that make Website pre-builder’s distributions more straightforward to use off-the-shelf in Drupal 6 are actually integrated in the middle Drupal 7 package. Because of this we can get started adding some actual kick-ass options to the Drupal 7 distributions as a result of all the basics at the moment are treated in core.
Drupal 7 is an upgraded version of Drupal 6. It offers more modules and programs to make web building easy