VIEWS: 16 PAGES: 2 POSTED ON: 4/6/2011
?With Drupal 7 right around the corner, I've lately placed myself to the task of ramping up on what is new, what's modified, and what do I as a module developer want to recognise when I take a seat down to code my first Drupal 7 module (or improve one in all my D6 modules *shameless plug*). I've spent the last few weeks scouring over the Drupal 7 core and API documentation, and allow me be the first to tell you if have not heard it but (not going): higher times are ahead. For all of us. The amount of API changes from Drupal 6 to Drupal 7 are wide and sweeping. Drupal 7 is unquestionably still Drupal, that means that it still feels and acts like Drupal. Nodes are still nodes that may have taxonomy and feedback, customers are still users with roles and permissions, so on and so forth. However just about the whole lot beneath the hood and within the UI, for that topic, has been stepped forward upon and/or re-factored. From a coders perspective, I'm soon to be in developers heaven whilst Drupal 7 is going stable. From the standpoint of being a framework, Drupal 7s API is extra mature and modern. It's worthwhile to nearly call to mind Drupal 6 as a child in prime-faculty and with Drupal 7 that kid has graduated and is now in a position for the real world. The refactoring that has taken place during the last couple of years and all the new features now to be had will be a boon for module and theme builders alike. This also explains just why now we have had to wait so long for a strong release. . . This article will be the first in a sequence exploring Drupal 7s API. For this text (itself a -section collection), I need to speak about what I feel, as a developer, is the most considerable and essential modification to the Drupal core. The new database abstraction layer (or DBTNG Database: The Subsequent Era) is a complete overhaul of the database layer now we have grown aware of in variations Drupal 6 and before. Constructed on PDO, the database layer in Drupal is now actually abstract, that means that it is database agnostic. This gives Drupal the versatility to run on any choice of other systems without having to write down new code or modification any existing code that interacts with the database. This additionally implies that we will be able to be expecting to peer much more enterprise-stage Drupal web sites as soon as Drupal 7 hits stable because its footprint in the company global will now be able to develop substantially. So, allows see what all this means. At first, gone are the times of getting to put in writing ludicrously long and complex MySQL or Postgres established SQL statements to fetch or write data. Long past are the days of getting to outline your placeholders type. And gone are the times of getting to worry approximately what may occur to your data if an insert or update question failed in the course of executing (yes, we after all get to use transactions!). Permits soar right in and get started 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 query the database with a SQL string you write. Dynamic queries are constructed by Drupal using a query item and that question objects methods. A couple of basic examples might lend a hand illustrate the difference. File coping with has additionally been improved. Particularly, one real flaw with Drupal 6 was it is incapability to put into effect private file coping with (for safety purposes) and CSS record aggregation at the same time. The issue was once somewhat serious because with out CSS file aggregation, higher web pages could break in Internet Explorer as a result of its inability to take care of large selection of CSS file. The other was once to set record managing to public and run the risk of storing personal or industrial documents within the report root. Happy that is over with... Overall, I can't stay up for a strong Drupal 7 release. So much of the options that make Website online pre-builder's distributions more uncomplicated to use off-the-shelf in Drupal 6 at the moment are integrated in the center Drupal 7 package. Which means we will start adding a few real kick-ass options to the Drupal 7 distributions because the entire fundamentals are now handled in core.
Pages to are hidden for
"Drupal 7 Vs Drupal 6"Please download to view full document