All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
You spend so much time writing secure code, and doing security updates, but you're putting all of that in danger with your wiki. A huge percentage of agencies put passwords into wikis - and other shared resources!!!
Using a shared Google/Office document, spreadsheet - even with black text on a black background - isn't much better! So, think of "wiki" in this context as being any "low-cost, low-security, high-accessibility, super-convenient storage."
You are putting your agency AND your customers at risk by keeping passwords in your company wiki!
Read more to find out why, and a better way to do it!
The Drupal Association Board is responsible for the Drupal Association’s financial health and as part of their duty, they vote to approve monthly financial statements. The board met on September 23, 2017 at the board retreat that took place before DrupalCon Vienna and voted to approve the Q2 2017 financial statements that were prepared by our virtual CFO service, Summit CPA.
This blog walks you through our Q2 2017 Financials and how we performed against the two financial KPIs that we measure against each month:
Cash Reserve: Have a cash balance of 15-30% of Total Revenue
Net Income Profit Margin: End 2017 with a net income profit of 10%
Below is a summary of how we performed against our KPIs each month in the second quarter of 2017.KPI Goal April May June Cash Reserve 15-30% 60% of goal 84% of goal 88% of goal Net Income Margin (NIM) % 10% 49.9% -29.8% -48.9%
The table above shows that Q2 was strong as a whole, due to the big income assist DrupalCon Baltimore gave.
With May and June below the KPI goal, we reviewed the entire quarter results as a whole. The quarter was buoyed by DrupalCon Baltimore which produced a majority of the $2,328,367 in April’s revenue and after its expenses, April landed $1,163,390 in net income. Following DrupalCon, May and June collectively accounted for $542,530 in revenue, producing a $214,711 net loss. When taken in total, we generated revenue of $2,870,897 and net income of $948,679. This equates to a NIM of 33.04% for the second quarter measuring above the net income margin goal.
You can see we did not achieve our cash reserve goal this quarter. The Drupal Association is still in its financial turn around so we did not meet our goal for the second quarter, however we are much closer to doing so than we have been in the past.
This chart below shows how cash reserves are building in Q2 and getting closer to hitting the cash reserve goal for this quarter.Monthly Updates
April results toward our KPIs had us holding $1.2M in cash, which is 84% of the stated cash reserve goal. Due to DrupalCon Baltimore reporting strong sales in both trainings and general conference tickets, we resulted in 49.9% of net income KPI. Expenses for DrupalCon Baltimore came in lower, catering had significant savings of $50K.
For May, our cash reserve goal increased 11% through additional sales in Digital Sponsorships programs and DrupalCon ticket sales. May expenses had DrupalCon Baltimore $15.8k less than forecasted, and IT had some savings in their budget as well, which helped cash reserves.
June had costs from Baltimore which lowered net income by $70k than originally forecasted. This was seen in event production costs that were $100k higher than anticipated, along with an unanticipated $14k in professional expenses. Reducing the impact of those costs, income in other programs came in $55k higher, the majority being rebates from DrupalCon Baltimore. This impacted the cash reserve KPI, where we reached 88% of our goal.
We would not be able to do our mission-driven work without the support and contributions of our community. Contributions come in many forms, through the purchase of DrupalCon tickets and event sponsorships, through our Supporters and Members, Drupal.org sponsors, recruiters who post jobs on Drupal Jobs and many other fantastic ways our community supports the Drupal eco-system. We are deeply grateful for everyone who contributes their time, talent, and treasure to move Drupal forward.
Thank you!File attachments: june cash reserve.jpeg
Migration is a term, which all the developers who have started working in Drupal 8 have gone through once at least in their development cycle. Migration can be done of many things like site migration (i.e migrate from Drupal 7 to Drupal 8), user migration, content migration. In simple terms, we can migrate all types of entity in Drupal 8.
How this migration works:
Migrate works by reading a row from a source plugin then running each property through a pipeline of Process plugins thus, resulting in a row to a destination plugin.
Why we write Process plugin?
Drupal is the big community where each member wants to share his or her experience with others. That’s why there are a lot of Drupal events. We held one of them.
How the DevOps movement is pointing the way forward to higher quality Drupal projects, faster delivery, happier team members, and satisfied clients for projects of any scale
Over the past several years, the best practices surrounding Drupal DevOps have expanded and improved, including continuous integration, continuous delivery, continuous deployment, and automated testing. In turn more organizations are discovering the benefits of these automated tools and deployment methods:
- Faster development – developers can deliver more work in less time and reduce project costs (or deliver more work for the same budget)
- Higher quality – with repeatable builds and automated tests against live production content for every change we reduces stress and uncertainty surrounding deployments of new features and bug fixes
- Transparent development cycles – frequent builds mean any team member can check on the progress of any task at any time
- Better collaboration – team members and stakeholders can focus on the features that matter instead of collaborating over the mundane details of builds and deploys
Whether a site is under active development or already in production, these benefits result in less stress, higher quality projects, happier developers, and satisfied stakeholders.
Now Drupal 8.4 is released, and Drupal 8.5 development is underway, it is a good time to give an update on what is happening with Drupal's Layout Initiative.8.4: Stable versions of layout functionality
Traditionally, site builders have used one of two layout solutions in Drupal: Panelizer and Panels. Both are contributed modules outside of Drupal core, and both achieved stable releases in the middle of 2017. Given the popularity of these modules, having stable releases closed a major functionality gap that prevented people from building sites with Drupal 8.8.4: A Layout API in core
The Layout Discovery module added in Drupal 8.3 core has now been marked stable. This module adds a Layout API to core. Both the aforementioned Panelizer and Panels modules have already adopted the new Layout API with their 8.4 release. A unified Layout API in core eliminates fragmentation and encourages collaboration.8.5+: A Layout Builder in core
Today, Drupal's layout management solutions exist as contributed modules. Because creating and building layouts is expected to be out-of-the-box functionality, we're working towards adding layout building capabilities to Drupal core.
Using the Layout Builder, you start by selecting predefined layouts for different sections of the page, and then populate those layouts with one or more blocks. I showed the Layout Builder in my DrupalCon Vienna keynote and it was really well received:8.5+: Use the new Layout Builder UI for the Field Layout module
One of the nice improvements that went in Drupal 8.3 was the Field Layout module, which provides the ability to apply pre-defined layouts to what we call "entity displays". Instead of applying layouts to individual pages, you can apply layouts to types of content regardless of what page they are displayed on. For example, you can create a content type 'Recipe' and visually lay out the different fields that make up a recipe. Because the layout is associated with the recipe rather than with a specific page, recipes will be laid out consistently across your website regardless of what page they are shown on.
The basic functionality is already included in Drupal core as part of the experimental Fields Layout module. The goal for Drupal 8.5 is to stabilize the Fields Layout module, and to improve its user experience by using the new Layout Builder. Eventually, designing the layout for a recipe could look like this:Closing thoughts
Layouts remains a strategic priority for Drupal 8 as it was the second most important site builder priority identified in my 2016 State of Drupal survey, right behind Migrations. I'm excited to see the work already accomplished by the Layout team, and look forward to seeing their progress in Drupal 8.5! If you want to help, check out the Layout Initiative roadmap.
Special thanks to Angie Byron for contributions to this blog post, to Tim Plunkett and Kris Vanderwater for their feedback during the writing process, and to Emilie Nouveau for the screenshot and video contributions.
TL;DR: For PHP Hexadecimals, Decimals and Octals are all Integers, so they must be declared as @param integer
While I was working on a patch I had to write the docblock of a function which received a hexadecimal number and I wasn't sure what I was supposed to put in the @type param.
I went to Drupal's API documentation and comments standards page to see which is the best type for this param and I found the following:
Data types can be primitive types (int, string, etc.), complex PHP built-in types (array, object, resource), or PHP classes.
Alright, a hexadecimal number is not a complex PHP built-in type nor a PHP Class so it must be a primitive type, so I went to the PHP documentation page to see which primitives PHP has and I found the following:
- float (floating-point number, aka double)
So there wasn't a specific reference for a Hexadecimal number...
In the end Pieter Frenssen helped me (Thanks!) with this, and he showed me that in PHP, it doesn't matter what the base number is and it can be an octal, hexadecimal or a decimal, for PHP they all are integers (which makes sense but I wanted to be sure) and he shared this small snippet where we can see that PHP sees the numbers as integers and the base doesn't matter:$ php -a Interactive shell php > var_dump(gettype(0x0f)); string(7) "integer" php > var_dump(0x08 === 8); bool(true)
So if you are writing the documentation of a function in which one of its params is a hexadecimal number you must declare it as Integer.
Elevated Third’s CEO, Jeff Calderone, recently shared his insights with Clutch on Drupal, how to choose a platform and how to choose the right web developers to build your website. This is part of a series of interviews that Clutch has been conducting to educate businesses on the options they have when building a website.
Clutch is a B2B ratings and reviews website that ranks digital agencies to help business buyers choose the best partner for their next dev project. We’re currently ranked as a top 5 Drupal Development firm and a top 5 Denver web designer in their research.
Drupal is one of the most popular opensource CMSs. Its community of developers ensures that the platforms continues to evolve and improve. According to Jeff:
“Drupal is great because it gives you a lot of functionality out of the box, the core functionality that’s been built by thousands of developers over time. It’s really solid, tested, and secure. The modules that are created by the community are really where the power comes and where it stands out. We can start with a key suite of modules and core functionality and often get our clients 60-70% of the way to where they want to go, but then be confident that we can build custom modules and functionality to get them the rest of the way, and oftentimes, replicate the functionality of a fully custom website for much less because we’re using the opensource community that has created all this functionality over time.”
Each business has different needs for their website. When it comes to choosing a website platform, Jeff offered:
“Especially if they’re in the B2B space and have that longer sales cycle, I think they need to pick a platform that is going to be able to grow with them and integrate with their existing legacy systems as well as connect with marketing automation and Salesforce and CRM in a way that is user proof. Personalization is coming. Voice activation is coming. All of those exist in some form already. Building on a platform like Drupal allows you to get something up and running quickly and be modular both now and in the future and add onto a solid core as these technologies and trends become actual.”
Another challenge that companies face is choosing the right partner for their project. According to Jeff the key to finding the right company is:
“Focusing on an agency that’s going to understand your business and solve the right problem as opposed to just developers who are going to build what they’re told to build… There are a lot of shops that have good developers that will build whatever you tell them to. We focus on providing that strategic insight. Half our agency is strategy and UX and design and helping the company to solve the right problem trusting that the other side of our shop, the Drupal developers, can implement and build those things that we recommend… It’s key to have that integrated approach and not just one or the other.”
If your business goals and website requirements are planned out early on, choosing the right platform and partner for your company will be simple. To learn more about Drupal, you can read the full interview here.
Moving to a new e-commerce platform can be a massive undertaking, but Drupal is making it simple. Whether you currently use Commerce 1, Ubercart, Shopify, or Magento, there is (or will soon be) an easy way to move over to Commerce 2 and see what it can offer you. Watch the latest High5 video here to learn more.What moving means
There are a ton of different parts that make up your e-commerce site: products, product variations, orders, customers, account balances, user logins, etc. One of the first things you need to decide is which parts you're going to migrate. Maybe you want to pull order data, but not discounts, which can be notoriously difficult to move over. Products are obviously essential, but moving tax rules over is not nearly as crucial, since you could probably set those up yourself (and if you work with a third party for that anyway, migrating tax rules is a waste of time).What migrate tools can do
Migrating your site manually is incredibly labor-intensive and prone to failure (you try moving 10,000 products manually without screwing any of them up.) Automating the process with migrating tools that have been thoroughly tested will give you a lot more consistency when moving your data around. And the best part is that this is all open source; we're releasing these tools so that anyone can migrate their site on their own at no charge.How the tools were developed
We started from the most common stuff (products, orders) and worked our way out to customers and discounts and product classes and all the rest. We have sample sets that we test for each of those aspects. So we have full databases of Ubercart sites, for instance, that we migrate over so we can see which parts are missing and what needs to be improved. We continually work to build those missing pieces and fill out all those edge cases.What's ready and what's coming
We have all the basics done for Ubercart; if you want to do an Ubercart to Commerce 2 migration right now, you can do it, though you might have to do a little bit of configuring and customizing to get the edge cases. We're trying to get to a point where you can literally just push a button and have everything move over, but that's still a couple months away. Commerce 1 is close to that, Magento is pretty basic, and Shopify is more of a prototype right now.
Clare breaks down how to reassign nodes from one taxonomy term to another. Code samples included.
Today, Skvare has released a new version of CiviCRM Entity, 2.0-beta11. This release contains a new feature, an admin configuration page which allows site administrators to disable exposure of entity types to Drupal.
CiviCRM Entity is a Drupal module which exposed CiviCRM API entity types as native Drupal entity types, providing Views, Rules, Entity Reference field integration, and Drupal native pages and forms for each. It supports both CiviCRM 4.6 LTS and CiviCRM 4.7.
Previous versions of CiviCRM Entity allowed developers to control access to Drupal based pages and forms for entity types, but there was no way for administrators to control what entity types were available in Views, Rules, or Entity Reference fields. As CiviCRM Entity has evolved over the past 2 years, over 45 entity types have been supported, including all the major financial record types. There are cases where many of these entity types are not used in Views, Rules, etc.., and admins may not want to make data of these entity types available to be used in Views by lower-ranking administrative users. Disabling an entity type in CiviCRM Entity does not affect the Core Views integration. However it will not make any of the additions that CiviCRM Entity provides, and for types not supported by CiviCRM Core, integration can now easily be toggled on/off.
Having all entity types enabled can affect performance in some aspects. Generally, this does not affect cached page load for normal users, but anytime you clear the cache, or the Views cache, having 45 entity types can cause cache rebuild to be intensive, not to mention all the additional menu paths that are generated for the Admin menu. Disabling entity types that you do not use will streamline admin user performance, and make the site in total that much faster by reducing memory footprint.
For existing users of CiviCRM Entity, the module can be upgraded as per Drupal standard, and there are no necessary config changes to make. There are updates that need to be run by going to "/update.php" or running "drush updatedb" from the command line. These updates simply set up a configuration variable, and do not affect the CiviCRM database. All available entity types are enabled by default for new or upgraded installations.
All submodules that are packaged with the CiviCRM Entity will automatically enable entity types that are required by the submodule and will enforce that these entity types remain enabled as long as the submodule is enabled.Usage
You will find an admin configuration page at "admin/structure/civicrm-entity/settings". A user with a role with 'administer CiviCRM Entity' permission is required to access and manage the settings on this page.
It is important to remember to enable all entity types used by your site's configuration and 3rd party modules. This page does not check if an entity type is required by an existing View, Rule, Entity Reference field. Disabling an entity type will break functionality in any rule, view, or field that requires it, so proceed with caution. However, re-enabling will restore functionality for those entities.
For developers of 3rd party modules or custom modules making use of CiviCRM Entity, you are responsible for ensuring an entity type is always available. This requires only a hook_form_alter() implementation to disable the necessary configuration page checkbox, or adding a validation or submit handler to the form.Future
We consider CiviCRM Entity for Drupal 7 to be feature complete, and it has been quite some time since there was a major bug found. We plan to release a non-beta stable 2.0 version at the end of this year. This upcoming stable release will be regarded as a Long Term Support release, and any major changes or updates will move to a 3.x branch. The primary focus of new development will now shift to the Drupal 8 version development. We will continue to support the 7.x-2.x branch throughout the life of Drupal 7 for bug fixes and minor feature updates. We will support for CiviCRM 4.6 LTS for its lifetime, and most likely beyond.DrupalExtensions
I started adding unit tests to Drupal Code Builder about 3 years ago, and I’ve been gradually expanding on them ever since. It’s made refactoring the code a pleasant rather than stressful experience.
However, while all generator types are covered, the level of detail the tests go into isn’t that deep. Back when I wrote the tests, they mostly needed to check for hook implementations that were generated, and so quick and dirty regexes on the generated code did the job: match 'mymodule_form_alter' in the generated code, basically. I gradually extended those to cover things like class declarations and methods, but that approach is very much cracking at the seams.
So it’s time to switch to something more powerful, and more suited to the task.
I’ve already removed my frankly hideous attempt at verifying that generated code is correctly-formed PHP, replacing it with a call to PHP’s own code linter. My own code was running the generated PHP code files through eval() (yes, I know!) to check nothing crashed, which was quick and worked but only up to a point: tests couldn’t create the same function twice, as eval()ing code that contains a function declaration brings it into the global namespace, and it didn’t work at all for classes where while tests were being run, as the parent classes in Drupal core or contrib aren't present.
It's already proved worthwhile, as once I'd converted the tests, I found an error in the generated code: a stray quote mark in base field definitions for a content entity, which my approach wasn't picking up, and never would have.
The second phase is going to be to use PHPCS and Drupal Coder to check that generated code follows Drupal Coding Standards. I'm currently getting that to work in my testing base class, although it might be a while before I push it, as I suspect it's going to complain about quite a few nipicks in the generated code that I'll then have to spend some time fixing.
The third phase (this is a 3-phrase programme, all the best ones are) is going to be to look into using PHP-Parser to check for the presence of functions and methods in the code, rather than my regex-based approach. This is going to allow for much more thorough checking of the generated code, with things such as method order in the code, service injection, and more.
After that, it'll be back to some more refactoring and code clean-up, and then some more code generators! I have a few ideas of what else Drupal Code Builder could generate, but more ideas are welcome in the issue queue on github.Tags: drupal code builder
This story is reposted from Drudesk.com thanks to Drupal Ukraine Community.
Hello everyone! Drupal Ukraine Community is thriving. Last year’s Lviv Drupal Camp 2016 seems like only yesterday, but now it’s time to share our latest camp with you. This is the story of Lutsk Drupal Camp 2017, the annual camp for all Ukrainian Drupalers. We promise you a really interesting story. After all, who’s able to tell you more about the event than the organizers — the teams from Drudesk and InternetDevels, powered by Drupal Ukraine Community? Let’s go!Lutsk Drupal Camp 2017 and its blue ocean
The official logo for Lutsk Drupal Camp 2017 was the Druplicon’s “infinity” eyes with scenes of Lutsk city reflected in them. It also resembled a fish to many. At Lutsk Drupal Camp, the blue color of the eyes was everywhere — on T-shirts, badges, backpacks, notebooks, and so on. Wherever you stepped, the blue wave carried you. And the main hero in this story was our favorite “drop” — Drupal!
+1 step to DrupalCon Ukraine
It’s no secret that the Ukranian Drupal community dreams about hosting DrupalCon in Ukraine some day. Holding Drupal Camp in the ancient and cosy city of Lutsk is one more step to holding DrupalCon in Ukraine!Lutsk Drupal Camp 2017, the main event
Starting with the morning’s registration, it was clear that the day would turn out incredibly positive. The organizers (in dark blue T-shirts) worked like busy bees taking care of every small detail and were ready to solve any possible problem.
Luckily, there were no problems to solve! Well, okay there was just one. The speakers at Lutsk Drupal Camp 2017 were so awesome that it was hard to choose which sessions to attend! They touched upon the most interesting and modern aspects of Drupal development, asked about the audience’s experiences and shared their own.
The concentration of famous speakers per square meter of space was sometimes so high it made you dizzy. They were also glad to receive the certificates of appreciation from us!
During Lutsk Drupal Camp 2017, there was also a time to catch up for old and new friends.
And even for some sports.
Of course, Drupalers are driven by inspiration, but some additional snacks never go amiss.
But this was just a rehearsal before the main lunch we all had together at Lutsk Drupal Camp 2017.
Of course, it isn’t Camp without Drudesk and InternetDevels team taking photos together.
And with all the guests as well.Lutsk Drupal Camp 2017 and the flames of our love for Drupal
After all the speeches finished, the sponsors named the winners of their prize drawings, and the closing ceremony summed up this big day, there was more to look forward to. The big party in the XIV century medieval Lubart’s castle was a chance for all the guests to see Lutsk' main attraction and, of course, to enjoy each other’s company.
The friendly atmosphere, hot snacks, and the energy of vibrant music played by the rock band warmed up the cool evening.
But we had something even hotter, too, as our love for Drupal kindled into real fire. The fire show within the medieval walls was truly impressive. The final touch was “Lutsk Drupal Camp 2017” “written” with fire.
Thanks to everyone involved in the awesome Lutsk Drupal Camp 2017. Hope to see you again soon! Follow us on Facebook and other social media. Find Drupal Ukraine community at drupal.org/drupal-ukraine-community.
Today, I am excited to announce that Michael Sullivan will be joining Acquia as its CEO.The search for a new CEO
Last spring, Tom Erickson announced that he was stepping down as Acquia's CEO. For over eight years, Tom and I have been working side-by-side to build and run Acquia. I've been lucky to have Tom as my partner as he is one of the most talented leaders I know. When Tom announced he'd be stepping down as Acquia's CEO, finding a new CEO became my top priority for Acquia. For six months, the search consumed a good deal of my time. I was supported by a search committee drawn from Acquia's board of directors, including Rich D'Amore, Tom Bogan, and Michael Skok. Together, we screened over 140 candidates and interviewed 10 in-depth. Finding the right candidate was hard work and time consuming, but we kept the bar high at all times. As much as I enjoyed meeting so many great candidates and hearing their perspective on our business, I'm glad that the search is finally behind me.The right fit for Acquia
Finding a business partner is like dating; you have to get to know each other, build trust, and see if there is a match. Identifying and recruiting the best candidate is difficult because unlike dating, you have to consider how the partnership will also impact your team, customers, partners, and community. Once I got to know Mike, it didn't take me long to realize how he could help scale Acquia and help make our customers and partners successful. I also realized how much I would enjoy working with him. The fit felt right.
With 25 years of senior leadership in SaaS, enterprise content management and content governance, Mike is well prepared to lead our business. Mike will join Acquia from Micro Focus, where he participated in the merger of Micro Focus with Hewlett Packard Enterprise's software business. The combined company became the world's seventh largest pure-play software company and the largest UK technology firm listed on the London Stock Exchange. At Micro Focus and Hewlett Packard Enterprise, Mike was the Senior Vice President and General Manager for Software-as-a-Service and was responsible for managing over 30 SaaS products.
This summer, I shared that Acquia expanded its focus from website management to data-driven customer journeys. We extended the capabilities of the Acquia Platform with journey orchestration, commerce integrations and digital asset management tools. The fact that Mike has so much experience running a diverse portfolio of SaaS products is something I really valued. Mike's expertise can guide us in our transformation from a single product company to a multi-product company.Creating a partnership
For many years, I have woken up everyday determined to set a vision for the future, formulate a strategy to achieve that vision, and help my fellow Acquians figure out how to achieve that vision.
One of the most important things in finding a partner and CEO for Acquia was having a shared vision for the future and an understanding of the importance of cloud, Open Source, data-driven experiences, customer success and more. This was very important to me as I could not imagine working with a partner who isn't passionate about these same things. It is clear that Mike shares this vision and is excited about Acquia's future.
Furthermore, Mike's operational strength and enterprise experience will be a natural complement to my focus on vision and product strategy. His expertise will allow Acquia to accelerate its mission to "build the universal platform for the world's greatest digital experiences."Formalizing my own role
In addition to Mike joining Acquia as CEO, my role will be elevated to Chairman. I will also continue in my position as Acquia CTO. My role has always extended beyond what is traditionally expected of a CTO; my responsibilities have bridged products and engineering, fundraising, investor relations, sales and marketing, resource allocation, and more. Serving as Chairman will formalize the various responsibilities I've taken on over the past decade. I'm also excited to work with Mike because it is an opportunity for me to learn from him and grow as a leader.Acquia's next decade
The web has the power to change lives, educate the masses, create new economies, disrupt business models and make the world smaller in the best of ways. Digital will continue to change every industry, every company and every life on the planet. The next decade holds enormous promise for Acquia and Drupal because of what the power of digital holds for business and society at large. We are uniquely positioned to deliver the benefits of open source, cloud and data-driven experiences to help organizations succeed in an increasingly complex digital world.
I'm excited to welcome Mike to Acquia as its CEO because I believe he is the right fit for Acquia, has the experience it takes to be our CEO and will be a great business partner to bring Acquia's vision to life. Welcome to the team, Mike!
In the previous article, we covered teaching your Drupal installation to send mail to users. But that is only half the battle, now we need to make sure the mail we send hits Inbox and not Spam folder. This article describes some options you have that offer relevant solutions. Unfortunately, no one can guarantee 100% inbox hits, but keeping the amount of mail filtered to Spam to a minimum is quite possible.Tags