The technical content posted on Zyxware.com is being managed and reviewed by a team called the Tech Content Team (TCT) and all the content that gets published goes through a TCT review process. Please find below the TCT initial review checklist that is used for the initial check on articles before they are accepted into the TCT workflow.
The technical content posted on Zyxware.com is being managed and reviewed by a team called the Tech Content Team (TCT) and all the content that gets published goes through a TCT review process. Please find below the TCT publishing review checklist that is used for the final check on articles before they go live on the site.
The technical content posted on Zyxware.com is being managed and reviewed by a team called the Tech Content Team (TCT) and all the content that gets published goes through a TCT review process. Please find below the TCT content quality checklist that is used for the final check on articles before they go live on the site.
The technical content posted on Zyxware.com is being managed and reviewed by a team called the Tech Content Team (TCT) and all the content that gets published goes through a TCT review process. Please find below the TCT technical review checklist that is used for the final check on articles before they go live on the site.
If you use git as the version control system for your software projects be it Drupal or non-Drupal projects then there is a very good chance for you to have tried deleting branches locally. It is not very often that you have to delete branches from the remote repository. However when people delete branches from remote repositories these branches would still show up in local repositories of the developers. Here is how you handle this.
When migrating from Drupal 5, the normal path would be to migrate everything (core/modules/themes) to the latest Drupal 5 versions, and then to the latest Drupal 6 versions, and then over to the Drupal 7 versions. How fortunate would have been the developers assigned the job if everything was as simple as that!
This is how you would normally render a view display passing filter inputs via code:
$view = views_get_view('view-name');
$view->set_display('display-name');
$view->is_cacheable = FALSE;
$filter_1 = $view->get_item('display-name', 'filter', 'filter_1_id');
$filter_2 = $view->get_item('display-name', 'filter', 'filter_2_id');
$filter_1['value'] = "value1";
$filter_2['value'] = "value2";
$view->set_item('display-name', 'filter', 'filter_1_id', $filter_1);
$view->set_item('display-name', 'filter', 'filter_2_id', $filter_2);
dpm($view->render());
It's another Friday Morning at the office, and Sandeep's fingers are running across his keyboard at twice the speed of light (or well, at a few fractions of the speed of light).
STATUATORY WARNING: Get ready to be Terminally Surprised
(and you thought you knew programming?)
It was one normal Friday Morning, and Tingu was thinking of how to spend the rest of her day, when Binny came along with sl and bb to make Tingu's day...
Friday 30 March 2012
Git is a popular version Control System that is Free Software. Created by Linux Torvalds to manage the development and deployment of the Linux kernel. The advantages of Git prompted developers to use it in many other software projects which required a robust version control system. Recently Drupal made the official transition from CVS to Git citing its advantages. So If you want to be a great developer you should get to know Git and its strengths when compared to existing Version Control Systems. Read on to get a better perspective on Git and its importance to Drupal.