One of the servers we maintain suddenly started developing performance hiccups. The site running on the server was a fully static website configured with static page caching via boost. The site used to receive a reasonably good volume of anonymous and search engine traffic on a daily basis. The only form on the site was a search form which existed as a separate page.
Drupal Technical
The success of a website depends on many aspects, its maintenance being the most crucial. Only a well maintained website will have a vibrant impact on the visitors. The below checklist helps you ensure that your Drupal website is well oiled time to time.
Backups and Maintenance
Have you ever thought about the security of your Drupal website on the web? If not, it’s high time you did that. Either be the case, here’s a simple checklist to make sure you have the essentials ready:
And so you have a Drupal site. But have you made sure that your site’s content is as required? Here’s a simple checklist to help you with that:
User Content
Here’s a simple checklist to make sure you do not miss out any of the essential configurations while taking your Drupal site live:
Configuration
You have your new Drupal site all ready for take off. You just want to make sure you have everything well in place. Here is a little checklist for you to make sure you have the essentials ready. In this part of the checklist series, we look at the important performance related essentials for a Drupal website, so that your site is ready to receive the multitudes it oughta get. These will help you ensure that your site will sail smooth in times of high traffic.
For any site - be it Drupal or non-Drupal, this is most probably due to simple mistakes made while entering attributes. Let us see one very common case where a simple mistake can cause glaring issues:
We usually see the css given something like this. We do not see any glaring issue in the class defined below.
#header {
background:url("images/headback.png")repeat-x;
width:1020px;
height:120px;
font-family:arial;
position:relative;
}
A white screen shows up while submitting a form in your Drupal Site?
There could be many possible causes for WSODs (White Screen of Death) in Drupal, such as PHP error reporting settings, memory exhaustion, etc. If the exact reason could be figured out, fixing becomes much easier.
For treating this specific WSOD issue on form submit, check for the following symptoms:
Drupal’s Devel module provides a wide range of functionalities that make a Drupal developer’s life much saner. Of these, the most useful one is the function dpm() which seems to have a twin clone - dsm().
For those who are unaware, dpm() is a highly useful function for neatly printing (pretty printing) arrays/objects etc in drupal. There is also a function dsm() in the devel module, which seems to do the same thing.
Then which is the correct one?
The UC eCheck.Net module is a Drupal module that implements eCheck payments using Authorize.Net's eCheck.Net service and is a popular module for online shopping websites using Drupal for making payments along with Ubercart. The module was officially released for Drupal 6. We have managed to release the updated version of UC eCheck.Net to work with Drupal 7 and is available for download.
In a common secnario if a user types the url of a Drupal based website without the 'www'.prefix they will be automatically redirected to the required site with the complete url. This is very convenient for most web users who do not want to type in the obvious 'www' prefix. Webmasters can configure this by changing the settings of the Drupal .htaccess file. However this will be a problem if the Drupal site has a mobile version with an 'm.' prefix. Users wishing to access the mobile version of that Drupal site will inevitably be redirected to the main website.
By default Drupal 7 has two types of views - The Full node view and the Teaser view. This has been the case for all previous versions of Drupal. However if your requirements are different, then you might have to create a custom view that is tailored to meet your specific needs. Check out how to create a simple custom “View mode” for nodes in Drupal 7.
We are pleased to announce the launch of our new website Top Drupal Books. Here you can get to know all about the Top Drupal books that can get you started in learning Drupal. Find out more on the best selling Drupal books available in the market from topdrupalbooks.com
The Drupal Menu System handles both the navigational system (visible menus and links) as well as the Drupal callbacks in the back end. The menu links listed on the header of a Drupal site is normally the primary menu or the secondary menu. These menus are sets of static links that you create via the Drupal admin interface. However sometimes it is useful to have a login / logout link in the primary or the secondary menu depending on whether the user is logged out or logged in. Here is how you add this.
On a Drupal site, when setting up pathauto for nodes, sometimes it is useful to have the full nested path of parent terms of the channel (or primary vocabulary) for the article in the url alias to give the impression of a directory structure to the taxonomy vocabulary. This will allow users to see urls to nodes like domain/term1/term2/term3/node-title-or-whatever where term3 is the channel under which the article is published.
Drupal is supposed to be a very secure CMS and the Drupal security team is a highly efficient team of people scouting the Drupal camp to find and sort out security issues as soon as they crop up. But no amount of programming will fix security issues caused by incorrect configuration of a Drupal site. Here is a checklist of items that you have to confirm after you deploy a new Drupal installation.
This is a basic installation instruction for installing Drupal in your shared cpanel hosting account. Although the instructions are for installing Drupal 7 and for installing it specifically on your cpanel hosting account, the steps outlined (or something similar) should work for installing other versions of Drupal or installing it in other hosting accounts. Read the complete instructions before trying this out.
Running Drupal on a shared hosting environment could become a challenge when the site starts getting a lot of visitors. So f you run your Drupal installation on one of the shared hosting providers like GoDaddy, Hostgator, Dreamhost etc and your site is reasonably popular then it is likely that you would have run into performance issues if the site is not configured correctly. If you configure your Drupal site correctly you should be able to stick with shared hosting for a longer period of time before moving on to dedicated hosting.
We have recently been toying with the Drupal API module in an attempt to set up our own Drupal API documentation site just like Lullabot did. As of today we have managed to set up something that is fairly functional and somewhat similar to the Drupal.org documentation site. Check out our own Drupal API reference site.
The site currently contains documentation about the top 500 Drupal modules and their D5, D6, D7 and D8 versions in addition to the documentation for Drupal 5, Drupal 6, Drupal 7 and Drupal 8.
Drupal uses a reasonably powerful mechanism to create, prepare and send emails generated within the system. We maintain two modules related to emails in Drupal - Mail Merge and MailQ (Mail Queue) - and get the opportunity to work with the mail subsystem in Drupal. Here is a brief write-up on how the mail system works in Drupal.