Calling all aspiring web developers! DrupalEasy Academy’s super popular Zero-to-Drupal workshop, (and all the awesome learning resources that go with it) is available anywhere, live through our online classroom June 18th and 19th (and on scheduled dates every other month!) Register now !
Everyone seems to need more and better Drupal talent. There are too many instances where projects are delayed, or even turned away or lost because we can't find the people with the proficiency to do the work. Even though high demand for Drupal is a relatively good problem, it is still one that begs for a solution. There's a plethora of training programs (including through DrupalEasy) out there for the self-motivated, tech savvy, Drupal-aware. The issue is, even with the mass of training available and promoted through the community, we still can't fill the gap, especially for the community's long term needs. This dilemma exists for the same reason that we face awareness challenges of the Drupal CMS overall; there is no sizable list of behemoth companies with huge marketing budgets or focused, funded, grand scale efforts to raise awareness outside of the community.
When building a Drupal-based website or theme, you will invariably create some test nodes of a content type that has at least one text area field. You should then add some example text, to see how those fields will look on the website. But beyond those nodes focused on styling, you may find it necessary or advisable to create a large number of additional test nodes of that content type. When you begin this process, you may wonder whether it would be best to add placeholder text (such as the venerable "Lorem ipsum") or leave those fields empty.
Drupal 7's HTTP access file, .htaccess, contains some URL rewriting code for redirecting all site visitors to the domain name starting with "www.", in case they try to go to the domain name without the prefix. For instance, you might want all visitors to go to www.example.com, and never example.com, for SEO purposes.
This is achieved by uncommenting the code on lines 81-82:
This guest post was written by Ben Hosmer , a Drupal user new to module development as well as an active member of the Florida Drupal user community. He often blogs about Drupal related topics at radarearth.com
Experienced programmers know the many benefits of using descriptive identifiers, such as the names of variables and functions. Descriptive names make it easier for the original developer — and all who follow — to understand the intent of the code, and to make global changes with minimal risk. In Drupal, when creating a new content type, the site developer assigns a human-readable name (which may consist of alphanumeric characters and spaces) and a computer-readable name (which may consist of lowercase letters, numbers, and underscores).
In my previous post , I talked about how I implemented the dynamic marker system on OffRoadAtlas.com . In this post, I'll cover the functionality that the PdMarker adds to the site. When you first hit the home page of the site, you'll see that the main content area is separated into two main sections: the narrow column to the left of the map (I call this the "info column") and the map itself. The idea behind the info column is that as users click on markers on the map, instead of the standard GMap info window, a very brief
I recently upgraded OffRoadAtlas.com with a custom map interface based on the GMap module. I was able to do this while leaving the GMap module is virtually un-hacked (with the exception of modifying the "GMAP_API_VERSION" variable) - all of the customizations were made via an additional "helper" module that was written specifically for this site. The site utilizes a map on the home page that shows all the off-roading areas and clubs in the database. The problem I was trying to solve was that I didn't want to have to load all 1,500+ points each time the home page was