If God did not exist, it would be necessary to invent him.
Most developers know how to do these, but a lot of people follow the temptation and skip them in the rush to go live.
These simple steps reassure future developers and clients that you know what you are doing, subsequently increasing your value with just a few minutes of work.
All which means you can charge more and book more clients, both of which lead to the ability to do more of the things you love that are just for fun!Read more
There are a boat-load of modules that send notifications..Tags: notificationsdrupal 7Drupal Development18ffeaturescharlottesville city councilviews rulesprofile2taxonomy
Recently I found myself musing about two Drupal-related posts from back in 2007 that projected very different futures for the software project.
The first was by Jeff Robbins of Lullabot: “How Drupal Will Save the World.”
Robbins took as his reference case a community in Nigeria facing exploitation by a multinational oil company. Drupal, he suggested, could empower the community and “give a voice to those who might not otherwise be heard,” driving an internet that was “a powerful force for social change.” To achieve that vision, Robbins laid out technical challenges, centered on making the software easier to learn and use.
A few months after Robbins’ post, Drupal contributor Fergus Geraghty initiated a Drupal.org discussion, “7 million reasons to consider democratising Drupal?” Drupal project lead Dries Buytaert had recently co-founded the company Acquia, and Buytaert’s start-up had just announced its first round of $7 million in venture capital financing. Geraghty expressed concern that the new commercial demands of Acquia could come to shape the overall direction of Drupal, pushing the project in the direction of profit maximization. Against this future, Geraghty proposed the creation of a co-operative to serve as the owner of the Drupal project.
Seven years later, which of these futures are we living? Is Drupal empowering the marginalized and saving the world?
Or is it serving “the man”?Software Freedom and Social Change
The idea that Drupal and free software could have a role in revolutionizing society might not be as off-the-wall as it sounds.
In Mutual Aid: A Factor of Evolution, the 19th century anarchist Peter Kropotkin countered the social Darwinist “survival of the fittest” thesis by arguing that cooperation was a driving force of evolution and a basis for free human societies.
This is the third in a series of blog posts about the relationship between Drupal and Backdrop CMS, a recently-released fork of Drupal. The goal of the series is to explain how a module (or theme) developer can take a Drupal project they currently maintain and support it for Backdrop as well, while keeping duplicate work to a minimum.
This module allows an interface to remove the apachesolr indexed content(s)/
document(s) of selected bundle. Administrator/Developer can delete the
particular entity id(s)
Developer can use this module as an example to remove the apachesolr indexed
Usually when you try to uninstall a field-based module you're confronted with the following error message:[module] is a required module and can't be disabled. Reason: Field type(s) in use - see Field list
In this blogpost I'm showing you how to uninstall such a module anyway (deleting all the stored data).Tags:
When you start a new project, you want your client to be happy with your solution because then you’ll get paid for what you’ve delivered. But what if your customer isn’t happy with your project results? Most likely, you won’t get paid the full amount of your order. The project setup with all the necessary agreements is one of the most critical parts of a project, and it influences the overall project's results. The good thing is that it’s not as hard as it seems to draft solid project agreements. When we at Bright Solutions start a new project, we always consider the following three questions. This provides a good basis for a robust project process that will deliver results and, ultimately, make clients happy.1) What should you deliver and when?
This question is essential and the most important one, so I’ll devote a few words to it. Spend as much time as needed to clarify all your client’s detailed requirements and have him commit to them. This detailed agreement should already be part of your quote. Don't just talk vaguely about requirements; use mind maps, mock-ups and user stories – they’re good tools for requirements engineering. This will help you avoid misunderstandings and failed projects. I’ll give you a short example:
"We need a registration process" is a requirement, in fact. You could agree on this – but you really should elaborate the particulars to reduce the risk of change requests down the road. "We need a registration process that allows a user to enter his/her company and user name in a single-line text field and with a button to sign in via Facebook" is a much more detailed requirement! Any old process by which a user can register would fulfill the first requirement, but this may not be what your customer expects. Next, always clarify the type of contract that underlies your business relationship. There are really only two kinds:
- Time and material: You’ll be hired for your skills and paid by the working hour, regardless of the result. Freelancers mostly work on this basis in project teams.
- Contract for work and labor: With this sort of contract you get paid only for the results, no matter how long you spend on delivering it.
Be conscientious and don't confuse these two contract types. Take care of the details during the engineering of requirements and write them all down.2) Who is responsible for what?
Clarify your role in the project and what kind of responsibility you’re assuming in this role. Are you a project manager, responsible for the project’s success? Are you a developer who just does the work you’re assigned? Or, are you an architect who transforms requirements into the software architecture that the developers need to do their part? This should be defined at the start of every undertaking to avoid misunderstandings during the project.3) When will I get paid?
Last but not least you should clarify when you’ll get paid. There are several options and it should be clear which one applies. Your client won’t be happy if you just send an invoice whenever you want: you should invoice according to your agreement. This could take one of the following forms:
- After the project is completely finished and successful (this payment modality is mostly for work-and-labor contracts)
- At the end of a specific time period (week, month, year), based on the hours you spent on a project (mostly for time-and-material contracts)
- After delivering pre-defined milestones
Add your payment modality to your quote to ensure that both you and your client agree on the same facts.
There’s a lot of project-related jargon floating around these days, like "agile", "fixed price", "waterfall" and "T&M". Ask 10 different people and you’ll get 11 different opinions on how these terms might apply to your projects! But my advice is: when it comes to negotiations with your client or contractor, simply focus on clarifying these three crucial questions and you’ll lay a strong foundation for your business relationship. Don’t be misled by buzzwords if you don't know exactly what they mean for you.
In upcoming blog posts I’ll share some additional information about successful project setup, management and controlling.
DrupalCamp Johannesburg 2015 will be held on Saturday the 28th of March 2015, from 09:00 until 15:00 at:
Business Connexion Park North
789 16th Road
Just off New Road, Midrand
Attendance to DrupalCamp Johannesburg is free; Let us know you are going to be there on meetup.com.
Please consider sponsoring DrupalCamp Johannesburg 2015, we have very affordable options available:Gold Sponsors: R 6 000
- Logo on a Stage Banner.
- Logo on a large Shark Fin.
- 6 Vinyl (back-of-laptop) Gold Sponsor Stickers.
- Noted, always, on DASA.org.za website as a Gold Sponsor.
- Logo on a Stage Banner.
- Logo on a medium Shark Fin.
- 4 Vinyl (back-of-laptop) Silver Sponsor Stickers.
- Noted, always, on DASA.org.za website as a Silver Sponsor.
- 2 Vinyl (back-of-laptop) Individual Sponsor Stickers.
- Noted, always, on DASA.org.za website as an Individual Sponsor.
Because we have printed material to prepare, the deadline for confirming that you will be a sponsor and for receiving your creative (logo for landscape, ISO216) is noon the 5th of March. It's urgent to contact email@example.com as soon as possible to arrange sponsorship. The deadlines are tight and it may be tough to handle a heavier load of work close to the deadline.DASA Board
DASA Governing Board Members agreed, when we formed DASA, to always stand aside if limited sponsorship options are available and the community wishes to sponsor an event. We have only five Gold and five Silver sponsorship spots open. If the community sponsors those and board members already also booked sponsorship, the board members' sponsorship will be downgraded to the first available lower level sponsorship.
Version 0.9.3 of the Dramble—running Drupal 8 on 6 Raspberry Pis
I've been tinkering with computers since I was a kid, but in the past ten or so years, mainstream computing has become more and more locked down, enclosed, lightweight, and, well, polished. I even wrote a blog post about how, nowadays, most computers are amazing. Long gone are the days when I had to worry about line voltage, IRQ settings, diagnosing bad capacitors, and replacing 40-pin cables that went bad!
But I'm always tempted back into my earlier years of more hardware-oriented hacking when I pull out one of my Raspberry Pi B+/A+ or Arduino Unos. These devices are as raw of modern computers as you can get—requiring you to actual touch the silicone chips and pins to be able to even use the devices. I've been building a temperature monitoring network that's based around a Node.js/Express app using Pis and Arduinos placed around my house. I've also been working a lot lately on a project that incorporates three of my current favorite technologies: The Raspberry Pi 2 model B (just announced earlier this month), Ansible, and Drupal!
I wanted to get some clarity on what I mean by the term "site builder". In a general sense, it refers to the actual process of building a website, but in Drupal the term Site Builder tends to have a specific meaning. I realised that my definition may vary from others so I wanted to be precise about what I think it means, and what I think it means to be a Drupal Site Builder.
I am a developer. I studied programming languages in depth. I did research into the semantic analysis of object oriented languages. But, when it comes to Drupal, I love to be a Site Builder.
I run a Creative Coding Meetup in London. At last night's meeting I was explaining Friday's Drupal Camp training to someone. I am clear about the aims and objectives of the training, I know my material, and I've given similar trainings many times before, but, the fact I labelled it an "intermediate" and "site builder" training causes some confusion.
First of all, I realised that using the word "intermediate" doesn't really mean anything. Drupal developers (or anyone building Drupal sites) of all skill levels have benefited from this training. So, perhaps what I mean by "intermediate" is actually "not beginner". As all I am really saying is that I'm not covering the very basics of getting Drupal up and running.
The term "site builder" is more problematic, possibly because my definition of a Drupal Site Builder may be wider than what most people expect. I thought about this a lot, and what I came up with was a clear set of statements of what I think it means to be a Drupal Site Builder...The Drupal Site Builder Manifesto
As Drupal Site Builders...
We work in a multi-disciplinary role.
We take initiative, and play a central role in the web development process.
We are usually the ones to take ownership of the final product.
We don't just “click and configure” websites. We have knowledge of all the areas involved in building a Drupal website.
We work with the rest of the team to ensure everyone is doing what they do best and contributing to the project in a meaningful way.
We may not all be trained developers, but we do appreciate how to think like a developer. We apply software development principles and Drupal best practises when creating Drupal configuation.
We may not all know how to write optimal PHP code, but we know when to build something using Drupal core or contributed modules, and when we need a custom plugin or custom module creating.
We may not all be able to produce the most stunning web designs, but because we understand how Drupal works we will work with designers to ensure their designs are consistent and well structured.
We may not all know all the latest front-end tricks, but when given well build front-end code we know how to get Drupal to generate the appropriate markup.
Most importantly, we know how to get the best results out of Drupal's building blocks, we know how to turn good designs and ideas into great websites, and we know how to build websites in a methodical, flexible, and maintainable way.
How do you collect public comments on a web-based PDF? It should be simple. But it isn’t.
Field formatter which renders text as a link pointing to its own entity. Useful when rendering a text field as part of a view.
Attach fieldgroups to an entity without creating tables for those fields, and store the data as a json string as if it was a textfield.
One of the more complex user interface issues yet to be solved is to provide groups of fields to the content manager while maintaining a sound data model. These groups of fields would generally be described as meta data for the content object being curated, and do not serve any purpose outside of the context of its parent object.
For those of us who have been breathlessly waiting, it’s finally here: registration for DrupalCon Los Angeles is open at last!
Coming up in May, DrupalCon Los Angeles promises to be a fantastic time — so make sure you register today to get the earlybird rate.
This module displays related entities based on relation.module using specified target entity view mode.
Current status: Module works with limitations.
- Relation must be configured with only one source and only one target entity types.
This project creates a new Webform field type called 'smart_ip' that uses the Smart IP module to provide additional data about the form submitter in hidden fields. The data will show up on the Results/Submissions admin pages, but will be hidden on the form submission.
This could be beneficial for lead generation sites that needs to filter leads by city or state.
There are a log of ways to arrange fields in drupal 7... If possible I like using display suite... it's convenient great for most projects... however when working with government forms there is often a need to be consistent with existing paper forms.Tags: Drupal Developmentarrange fieldsdrupal 7government formsvdotcharlottesville city council18f
Eric Mandel, CEO of infrastructure provider Blackmesh, and I got the chance to speak at PHP World 2014 (where I was also a keynote speaker). We spoke about his history with development, open source, and Drupal. I also had the chance to ask Eric about how Blackmesh has become a leader in the area of corporate contribution to Drupal, employing Cathy Theys to work on Drupal core, mentor new Drupal contributors, and help out at code sprints around the world.