Drupal Interview Questions: drupal developer

Showing posts with label drupal developer. Show all posts

Friday, April 25, 2014

Drupal Job Interview Questions and Answers ( a set of 50 questions, q52-q101)

101. What hardware does Drupal.org run on?

People often wonder what kind of hardware drupal.org runs on. Throughout the project history this has been a tough question. For a while it was a server in a random office building. That server eventually died and required a fund-raising effort to replace (the funds were raised in 24 hours!).

The critical infrastructure is all configured to share the load and be redundant. For example, db1 and db2 are configured to be master-slave most of the time to provide for better performance and allow the slave to be promoted to master if the master fails.

Read More here https://drupal.org/node/1280436

100. Drupal and Working with JavaScript

Drupal provides methods for implementing JavaScript. Using these methods will help to keep your code clean and to ensure compatibility with the way other modules implement JavaScript.

A couple of simple principles guide Drupal's JavaScript approach:

· All pages should be perfectly functional without scripts. JavaScript provides alternatives or supplements - not replacements - for standard elements.

No JavaScript is hard-coded into pages. Rather, actions are attached dynamically to page elements--and only if the needed JavaScript support is present.

Read more here https://drupal.org/node/121997

99. Why does Drupal need a database? What databases are supported?

Drupal stores its information - the individual pages, the registered users, and so on - in the database. The database forms the back-end for your Drupal site. At this time, Drupal supports MySQL (or an equivalent such as MariaDB), PostgreSQL, and in Drupal 7, SQLite.

Wednesday, April 23, 2014

92. Drupal 8 , Changelog.txt - What's new in Drupal 8

Drupal 8.0, xxxx-xx-xx (development version)

----------------------

- Added Twig as the default template engine and converted all .tpl.php templates

  to .html.twig.

- Added tour module. Provides highly contextual tips for UI elements.

- Improved entity system.

    * Added support for saving and deleting entities through the controller.

    * Entities are now classed objects, implementing EntityInterface.

    * Drupal now understands the concept of a "default" revision, tracked

      independently from the latest revision, allowing for the creation of

      drafts while the current revision stays published.

    * All entity types, not just nodes, now have support for revisions.

- Replaced the core routing system with one built on the Symfony2 framework.

- Configuration:

    * Added a centralized file-based configuration system.

    * Allows module authors to provide configuration in a standard format.

    * Implements functionality to get, set, add and remove configuration.

    * Includes ability to override configuration values with language variants

      and other runtime values.

- Added the CKEditor WYSIWYG editor. Provides a drag-and-drop configuration UI.

- Included the HTML5 Shiv library to support HTML5 elements in IE 8 and below.

- Included the following Symfony2 components:

    * ClassLoader - PSR-0-compatible autoload routines.

    * DependencyInjection - Flexible dependency injection container.

    * EventDispatcher - Object-oriented lightweight event handling system.

    * HttpFoundation - Abstraction objects for HTTP requests and responses.

    * HttpKernel - Core system for managing incoming HTTP request and responses.

    * Process - Allows for executing commands in a sub-process.

    * Routing - Framework for mapping incoming requests to controller

      information.

    * Yaml - Parser for YAML files.

- Included the Assetic asset management framework for PHP.

- Included Backbone.js and Underscore.js JavaScript frameworks.

- Support added for making HTTP requests through a proxy server.

- Removed modules from core.

    * The following modules have been removed from core, because contributed

      modules with similar functionality are available:

      * Blog

      * Dashboard

      * OpenID

      * PHP Filter

      * Poll

      * Profile

      * Trigger

- Removed the Overlay module from core.

- Removed the Garland theme from core.

- Removed the Statistics module's accesslog functionality and reports from core.

- Removed backwards-compatibility with 'magic_quotes_gpc'/'magic_quotes_runtime'

  PHP configuration settings. Both are required to be disabled.

- Universally Unique IDentifier (UUID):

    * Support for generating and validating UUIDs.

- JavaScript changes:

    * Updated to jQuery 2.1.0

    * Updated to jQuery UI 1.10.2

    * Removed jquery.bbq

- Tremendously improved language support all around.

    * Great language improvements for users:

      * Improved language selection with user preference detection in the

        installer.

      * Moved base language support to Language module.

      * Greatly simplified the interface for setting up languages.

      * Improved browser language detection considerably.

      * Language domain and path prefix configuraton simplified and centralized;

        path prefix detection is now default.

      * Added HTML 5 language markup; language information added in markup in

        several more places.

      * Made it possible to assign external language codes to local languages.

      * Introduced the possibility of an administration-specific language

        preference for users.

    * Simplified and added new features in interface translation:

      * Made interface translation directly accessible from language list.

      * Centralized interface translation import to one directory.

      * Drupal can now be translated to English and English can be deleted.

      * Much improved built-in translation interface.

      * Added support for singular/plural discovery and translation.

      * Customized translations are tracked so your modifications can

        be identified and protected from translation update overwrites.

      * All Gettext files are now imported in chunks, better for low resource

        environments.

    * Improved content language support:

      * Made it possible to assign language to taxonomy terms, vocabularies,

        menu items, and files.

      * Added a field translation based content translation module that applies

        to all content entities.

      * Removed the old node-copy based content translation module.

      * Introduced language defaults configuration for each entity type and

        subtype.

      * Added entity language variance support to search module.

      * Search indexing and query preprocessors now get language information.

      * Unified content translation permission granularity with content editing

        permissions.

      * Made the language selector freely orderable in entity forms.

    * Better configuration language support

      * Added language selectors to most configuration options (views, menus,

        etc.)

      * Added a configuration translation user interface that works with any

        configuration with translatable values (blocks, views, fields, etc).

      * Added language options to block visibility.

    * Much improved language APIs for developers:

      * Added simple APIs and hooks to save/delete/update languages.

      * New Language class wraps language information, used universally.

      * Unified database schemas and APIs to make it easier to spot where

        language codes are referenced.

      * Made the language negotiation system APIs more consistent for

        developers.

      * Made it possible for users to have a preferred language separate from

        their user entity language.

      * The text formatter from t() is now available as format_string().

      * Added support for interface translation contexts in Drupal.t(),

        Drupal.formatPlural() as well as routing, tabs, actions, and contextual

        links.

      * Removed textgroups support from interface translation in favor of

        native configuration language support.

      * Added configuration schema system to support generating translation

        forms for any configuration.

      * Reworked Gettext PO support to use pluggable read/write handlers.

      * Added language select form element in the Form API.

- Added E-mail field type to core.

- Added Link field type to core.

- Added Phone number field type to core.

- Added local image input filter, to enable secure image posting.

- Added Views and Views UI module to core.

- Added Entity Reference field type to core.

- Added Date field type to core.

- Added a Web Services module package.

    * Added a RESTful web services provider module.

    * Added a serialization module using the Symfony serialization component.

    * Added a Hypertext Application Language (HAL) serialization module.

    * Added a HTTP Basic authentication provider module.

Source : // https://api.drupal.org/api/drupal/core%21CHANGELOG.txt/8

Saturday, April 19, 2014

72. What is drupal weight ?

A term used by Drupal to define the priority or order in which a function is processed or a block / node is displayed. From Drupal 6, the weight field is adjusted dynamically using a drag-and-drop interface. Note: A lower weight value (-10) will float to the top of lists, while heavier (+10) weights will appear lower in lists.

69. What is theme and theme engine in drupal ?

theme

A file or collection of files (PHP, INFO, CSS, JPG, GIF, PNG), which together determine the look and feel of a site. A theme contains elements such as the header, icons, block layout, etc. Drupal modules define themeable functions which can be overridden by the theme file. There are additional themes available in the themes section of downloads.

theme engine

A set of scripts that interprets code and makes theming a site easier. These scripts take the dynamically generated content and output it to HTML. Drupal has three theme engines in addition to being able to write a theme that bypasses the theme engine. The default theme engine is phpTemplate. There are additional theme engines for downloads.

Wednesday, April 16, 2014

66. What is drupal region ?

Defined areas of a page where content can be placed. Basic regions include: Header, Footer, Content, Left sidebar, Right Sidebar. Different themes can define different regions so the options are often different per-site. Content is assigned to regions via blocks. They can be ordered by weight within regions to define the order in which they display.

62. What is cron in drupal ?

A command scheduler that executes commands or scripts (e.g. scripts to backup a database) automatically at specified time and date intervals. Drupal uses a “cron job” to perform periodic tasks that help Drupal to run smoothly and efficiently.