Drupal Development
more_horiz
close

on 30th May 2013 / by Anoop John
If you are an organization trying to set up a new website or if you are planning to upgrade your static website to a dynamic website here are some key reasons why Drupal is a good solution for you to bank on. a) Ability to continue to use the site for a long time - As an organization you would want to ensure that the investment you are making into the site is something that would continue giving you returns into the future. Drupal is a framework that will allow you to continue to use your site for several years with minimal maintenance. A Drupal major version will continue to be supported from the point it is released to the point till the release of the second major version after that. So a site built in Drupal 7 can safely be used until Drupal 9 is released. Typical release cycle is 1.5 - 2 years. So your site should be supported for at least 4 years. b) Continuous support and bug fixes - It is impossible to create software without bugs, but at the same time there is no reason why bugs cannot be fixed once they are found out. Drupal and contributed modules are community supported and bugs and issues that are identified are contiuously being fixed and newer versions released. This will allow your site to continue to be improved upon with minimal investment on the development front. c) Continuous security evaluation and fixes - Like with bugs it is almost impossible to create a software without security issues. However Drupal takes security very seriously and comes up with security fixes both for the Drupal core and for Drupal modules as soon as the loophole is identified and a solution is worked out. There is a crack team of community volunteers in the Drupal security team who focusses on the security aspects of Drupal continously. So if a site maintainer takes care of all the security updates that come out for the Drupal core and modules used on his site he would be able to more or less assume that his site is reasonably safe from all known vulterabilities. d) Do not have to pay for re-inventing the wheel - Drupal comes with more than 10000 modules covering a wide range of conceivable functionalities that anybody would want on their websites. Even if your requirements are not exactly met by these modules it would still be possible to tweak / customize these modules to meet your requirements. Trying to customize to meet the last 5% of the requirements is always going to be cheaper and faster than trying to build the whole thing from scratch. e) Rapid Application Development - Drupal provides a lot of tools to help a capable developer a very good RAD framework that can help convert ideas into products with very short turn around times. Optimizing the products and theming them to perfection might take time but getting proof of concepts out can be done very fast. These are only some of the key points that would make Drupal a good choice for your enterprise platform. If you are interested in knowing more before taking a decision we will be happy to provide consultancy support to help you take the right decision. If you have already decided to go with Drupal we will be happy to offer development support to help build your platform for you. Contact us to know more. Web Development Drupal Drupal Development Enterprise Solutions Leave a reply Your email address will not be published. Required fields are marker *
close

on 30th May 2013 / by Anoop John
If you are looking to find a reliable company in India to outsource your Drupal work then read more to see why we would be a good fit as a partner. Experience in Drupal - We have been exclusively working with Drupal since 2006 and we have clocked more than 150,000 hours of Drupal development. Expertise in Drupal - We have been contributing back to Drupal.org through modules, themes, patches and issue queue support. Our modules and themes are being used by more than 35000 sites across the world. Experience in Outsourced development model - We have delivered more than 120 Drupal projects to clients across the world over these years. Transparency - We follow an agile project development methodology that allows clients to interact very closely with the development team and review and give feedback on the work that is being done. Strong Processes and Systems - Our delivery processes matured over these 7 years will allow us to deliver predictable quality within cost and schedule. Trustworthiness and Reliability - Our long list of repeat clients and partners who have been with us for all these years stands in proof to our trustworthiness and reliability. Sounds interesting? Contact us to discuss more. Drupal Drupal Development Drupal India Leave a reply Your email address will not be published. Required fields are marker *
close

on 29th May 2013 / by tany.antony
Global Redirect is a functional module which ensures the correct redirection of users to the alias of a given drupal path, thus avoiding duplicated content from multiple URLs. This is very important for SEO because otherwise search engines will see the same content at the Drupal path as well as at its alias causing it to believe that the site is duplicating content at two different URLs Usually Drupal shows the same content for same urls ending with or without a slash "/". For instance, examlpe.com/node/21/ examlpe.com/node/21 To Drupal these two are the same page but to a search engine these are two different URLs with the exact same content. Since "duplicate content" is a major SEO issue, Global redirect module is a must from an SEO point of view. Global Redirect addresses this issue by redirecting all the different versions of a URL or a Drupal path to the one URL that is needed. Here are the test cases/checklists against Global redirect module. 1. As the 1st case, ensure that the global redirect module has been enabled. For this, Login as admin and check if the Global Redirect module is marked/checked under the modules list, as shown in the below image. 2. Secondly, ensure that Global Redirect module is working as expected. Follow the below given cases for the same: Ensure that the URL alias given for a node changes automatically and reflects on the URL of that particular node. For testing this, consider a site with domain name example.com. Now follow the below steps: Login to http://example.com as an authenticated user who has the privilege for creating a node/content type. Provide all mandatory details In the "URL path settings" options, provide a path for the node. For example, say "Testing-Global-Redirect-Module" is given for "node 123" (as shown in the below image) Save the node. Note down the node ID of that particular node and paste it in the address bar. The node ID can be obtained by editing the content. Ensure that http://example.com/node/123 changes to http://example.com/Testing-Global-Redirect-Module Ensure that the trailing slashes given in URLs gets removed on firing the url in the address bar. For example, say http://example.com/Testing-Global-Redirect-Module is followed by a slash, i.e. http://example.com/Testing-Global-Redirect-Module/ . On submitting this, http://example.com/Testing-Global-Redirect-Module/ should be automatically redirected to http://example.com/Testing-Global-Redirect-Module Happy testing! If you would like to ensure that different SEO aspects including Global Redirect is set up correctly on your Drupal site take it through a full SEO Audit and correct all issues identified. We will be happy to help you with this. Contact us to know more. Drupal Drupal Development Software Testing Test Cases Web Testing Drupal Testing Drupal SEO Leave a reply Your email address will not be published. Required fields are marker *
close

on 23rd May 2013 / by tany.antony
There wouldn't be any Drupal site that doesn't have forms on it - Drupal being a CMS, forms have always been an integral part of every Drupal version from start. Forms provide an easy interface to the website users to input information to the site. Being entry points of user input data into a website, forms are the ideal places where we should handle all validation for that data, guiding the user along the way. Being an input method, forms are also the most vulnerable parts on a website, that offer hackers easy entry points to your server. With this inherent risk, we have to thoroughly test each and every form element on a Drupal site so as to make sure that all input is validated and made risk-free. We have compiled some test cases and checklists to help you get started with testing your Drupal forms. Do check them out: Test cases/checklists to check against while testing File Upload fields on a Drupal site Test cases/checklists to check against while testing Image Upload fields on a Drupal site Drupal Drupal Development Software Testing Web Testing Leave a reply Your email address will not be published. Required fields are marker * Delphia (not verified) access_time 22 Feb 2019 - 15:04 It is in reality a great and useful piece of info. I am happy that you just shared this helpful information with us. Please keep us up to date like this. Thank you for sharing. Add new comment
close

on 23rd May 2013 / by tany.antony
Just as for File Upload fields, Image Upload fields are equally prone to hack attempts. They also have additional functionality to do post-upload, such as passing the image through various image processing filters / presets. While testing Image Upload Fields, you have to take into consideration all these points. Here are some test cases to help you test image upload fields on a Drupal site: Ensure that a warning message like "The selected image cannot be uploaded. Only images with the extensions given in the help text are allowed" is displayed when we try to upload an image of format that is not supported. Ensure that proper error message is thrown while trying to upload image of size lesser than the minimum limit and greater than the max limit specified. Ensure that images of correct extension and size can be uploaded to the site. Ensure that user can edit/delete the uploaded image. Ensure that the image file viewed is the same as the one uploaded. Ensure that the uploaded image is not cropped off. If client requirement is to set all images to a specific height_width format then ensure that the uploaded image is getting resized to that width, cropping/scaling as per required. These are the most important cases to be considered while testing Image Upload fields. Do let me know through the comments box below if you would have something more to add to this list. If you want us to test your Drupal site let us know as well. Hope this article helps. Happy testing! Drupal Drupal Development Software Testing Test Cases Web Testing Drupal Testing Software Quality Leave a reply Your email address will not be published. Required fields are marker *
close

on 20th May 2013 / by tany.antony
When focusuing on Drupal website development, user roles and permissions are an important way of controlling access to the site. This is more so important when there are multiple individuals besides the website owner who administers the site. Other people can be assigned certain 'roles' which define the kind of access that is to be granted. Basically in Drupal, the Site maintainer and Administrator roles are given all the available permissions and Drupal Administrator role receives all permissions throughout the lifespan of the site. This is not the case for other 'roles', where access within admin permissions and time limits only are granted to users linked to those roles. A major advantage of adding permissions is that, when a new feature is added to a Drupal domain which is not allowed for everyone by default, this functionality can be made specific for a 'role' or a group of 'roles' but granting access to them alone. Roles are not just a way to group permissions, but they also hide important information about the site as well. For this reason, users, roles and their permissions are imperative and have to be set up and configured appropriately and tested systematically. The major Test cases/checklists to be considered while testing roles and permissions in Drupal are documented here. Test cases for user roles and permissions: Ensure the domain allows to create new users with role(s). For this Create a test account and assign the created role to it. Then login as the new user and ensure all privileges given to that role. Alternatively, use a different browser (not a new window in the same browser) to test the role without logging out as administrator. Repeat the above steps for all roles and permissions in the site. In case a new role arises as a requirement while handling a maintenance site or after the completion of site, then it has to be tested extensively before being assigned to any user. The above procedures are to be repeated in such cases as well. Ensure that the permissions granted to custom roles are working as expected. Ensure that "access denied" error message is shown when Anonymous or non permitted users attempt to view a resource which is granted only to certain roles. Anonymous or non permitted users attempt to access a page/URL that is restricted to them. In case a user has more than one role, ensure that multiple roles and the combinations of those permissions (same user with conflicting permissions) work correctly. Ensure that Admin can mark/unmark permissions for users via the permissions page and these changes get reflected in the users role as well. Ensure that user does not have access to permissions once these permissions are taken out from the users role. Drupal Drupal Development Software Testing Test Cases Web Testing Drupal Testing Quality Leave a reply Your email address will not be published. Required fields are marker *
close

on 17th May 2013 / by tany.antony
You might ponder as to why test a link, or even include it as a test case when there are several other major functionalities to be tested in a Drupal website. Every site, be it Drupal or non-Drupal, contains numerous links, some of which lead to external sites and some that whirl within the site. The 'web' works extensively through links, and it is through links that sites are navigated to and get found. Links are also the underlying indicators for security of a site. So links should be paid attention to and be tested thoroughly. Here are some test cases to help you get started: Test cases / testing checklists for testing links: Ensure that upon clicking a link, the user is directed to the required or intended page/part of the website. Ensure that a cart page link cannot be accessed over HTTP. Ensure that color of links change after the page is visited once. (This can vary as per the design). Ensure that the link colour is as per the specification. Ensure that a hand icon is displayed when mouse pointer is hovered over the link. Finally, to make a link on your site look well and good, check Correctness of the words used. Correctness of the spelling. Correctness of their positions(alignment). Drupal Drupal Development Software Testing Test Cases Web Testing Drupal Testing Software Quality Leave a reply Your email address will not be published. Required fields are marker * Shinu (not verified) access_time 22 Feb 2019 - 15:04 1) Ensure that the link has a mouse hover effect ( Eg: An underline appears for the hyper link text when pointing mouse over it ) 2) Ensure that the color change made when clicking a link resets after clearing the browser cache 3) Ensure the linked page content is dependent of the text given in the hyper link. Martha Cole (not verified) access_time 22 Feb 2019 - 15:04 I feel immense pleasure to read articles on CMS platforms trending changes and its advantages. This post provides excellent information on Drupaltesting links. Add new comment
close

on 30th April 2013 / by muhammed.junaid
Triggers and Events are very important concept in the Drupal world. If you want to get your hands dirty tweaking Drupal or dive into Drupal development or simply configure a Drupal website properly you need to be familiar with the Drupal Actions and Triggers. If you want to know more about Drupal Triggers and Actions then read on to find out. Introduction Triggers are events occurring in a Drupal system. A node getting published or a new user getting registered are good examples of Drupal Triggers. When these events (Triggers) are activated, Drupal allows us to perform custom operations within that context. These operations will be defined in functions and these functions are what we refer to as Actions. Triggers and Actions can be considered as pairs, but they are more than that since we can call one or more actions per trigger. Actions can also be assigned to multiple triggers. One of the advantages with Triggers-Actions concept is that a Drupal user with zero coding experience can assign Actions to Triggers without modifying the code. Think about a scenario where the site admin wants to send a custom email when a user logins to their Drupal site for first time. The admin can select an Action that will send a custom email for the Trigger - user login, Moreover using Triggers and actions we can implement customizable complex workflows within Drupal. Triggers Triggers have to be defined within Drupal code. By default, Drupal 7 has several predefined Triggers. To see the Triggers within your Drupal installation go to the Admin page Structure -> Triggers (Trigger module needs to be enabled). You will see tabs for each category of Triggers. System, Node, User modules have Triggers by default. Actions Actions are functions that perform some operations on or using system objects, eg. entities like nodes, users, comments etc. So Actions will acting on some context containing some system object(s). Actions are of two types: ?Basic and Advanced. Basic Actions just work without any configuration. Advanced Actions needs to configured before using it. That means, Advance actions are customizable, they will have their own configuration forms. To see the Actions in your Drupal installation, go to Configuration -> Actions page. You will see all Basic Actions listed there by default. Advanced Actions have to be created by configuring them. You will see a 'Create an advanced Action' form at bottom of the that page. By selecting one of the advanced Actions and pressing the 'Create' button you can create the advanced Action after completing the configuration. Assigning Actions to Triggers Admins can assign Actions to different Triggers. Each trigger can have multiple actions associated with it and each actions can be assigned to more than one Trigger. Hope the article made you familiar with Drupal Actions and Triggers. Stay tuned for Part 2 Drupal Drupal Development Drupal 7 Actions Leave a reply Your email address will not be published. Required fields are marker * johnshantelle143 (not verified) access_time 22 Feb 2019 - 15:04 In the world of drupe you have to understand a lot of things all over the internet. - Steven C. Wyer Add new comment
close

on 18th January 2013 / by dhanyamol.kv
Many a times, IE7 stands out from the group of modern web-browsers owing to its notorious incompatibility with many a standard HTML/CSS/JS. In this article, we are seeing the following case of incompatibility: CSS border for Select (Drop down) element does not work. On one of my Drupal sites, while validating a form, when a required input field has not been filled before hitting the Submit button, an error message is shown, and the field is highlighted with a red border. The red border was achieved with this CSS: .form-item input.error, .form-item textarea.error, .form-item select.error { border: 2px solid red; }This works fine on all browsers except IE7, as shown in the following images: Here is what we see on IE7: Web Development Internet Explorer CSS Drupal Development Browser compatibility CKEditor IE7 Leave a reply Your email address will not be published. Required fields are marker *
close

on 18th January 2013 / by dhanyamol.kv
Many a times, IE7 stands out from the group of modern web-browsers owing to its notorious incompatibility with many a standard HTML/CSS/JS. In this article, we are seeing the following case of incompatibility: In IE7, the CSS 'border-collapse' does not override cell spacing related tags. While adding content using CKeditor in Drupal, users may add inline CSS to style the content. We can style each element in this content using our CSS to match the design of our site. In the case of table element, if we set HTML attribute cellSpacing on the table, like <table cellspacing="5" cellpadding="0">then we can remove this cellSpacing by making following changes in our CSS: table { border-collapse: collapse; } It will remove cellSpacing and table will look like this: But it will not work in IE7 browser. ie., CSS settings like border-collapse: collapsedoes not override an cellspacing HTML attribute on the table element. See the following image for details: Web Development Internet Explorer CSS Drupal Development Browser compatibility CKEditor IE7 Leave a reply Your email address will not be published. Required fields are marker * Mary Jovigil (not verified) access_time 22 Feb 2019 - 15:04 What's up to all, it's really a good for me to visit this website, it consists of priceless Information. Add new comment