All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
This is a simple linked image field.
The mostly usual use case is a block with social icons or something similar.
The work is in progress.
There’s no foolproof way to get an unhackable Drupal site; there could always be an exploit that we don’t know about yet. But there are quite a few ways you can help reduce the risk of getting hacked. Let’s dive into some of the most common ways Drupal sites get hacked, and how to secure your site against these points of entry.Drupal Security Advisories
One of the most common ways to get hacked is to fall behind on known Drupal Security Advisories. Keeping up to date on the latest advisories is ultimately your first line of defense.
There are security advisories for both Drupal core and contributed projects with varying levels of security risk for the exploits found. You can sign up for the security email list to make things easier to keep track of. You can do this by logging into your Drupal.org account and editing your user profile. From there you can subscribe to the security newsletter on the newsletters tab. This list will email you soon after Drupal Security Advisories are released to the public, which helps quickly notify you or your team of possible exploits that need to be fixed.
You can use the Update Status module in Drupal core to see which sites are affected by these advisories. Then add an email address to send Security Alerts to daily or weekly. The Update Status alerts have also notified us in a few cases when the email list was backed up and took longer than it normally would.
Typically, Drupal core security advisories come out on the third Wednesday of the month unless it’s a highly critical update that needs to be patched sooner. Contrib project security advisories can come out on any given Wednesday.Read more
Accessibility tool is mean to help people visual disabilities view content.
The tool allowing users to choose between pre-selected contrasts and to zoom in
and out with highly visible buttons. We have also included a optional help
button to link your sites help page.
Two hundred and fifty people from across Germany and its neighbouring countries gathered in Essen on 17 and 18 March for DrupalCamp Ruhr, an event full of fresh discussions, workshops and presentations.Josef Dabernig Tue, 03/27/2018 - 08:41
The organizers decided to use the Open Space / Barcamp format that provided attendees with the option to pre-select certain sessions, but which could also be combined spontaneously with ad-hoc sessions that the participants had presented in the kick-off session. This meant that, in contrast to our regular conference experience, each of us got to quickly present our idea and were also able to adapt the camp’s schedule collaboratively before we started.
On each day, we would then agree upon the session plan. I ended up doing a planned session and two spontaneous ones. Before I start to explain what I talked about, I would like to highlight what stood out for me, in terms of discussions and themes at the conference:
Drupal 8 Distributions are ready
The initial panel discussion on distributions was a great moment to hear Distribution Maintainers and Leads talk about NP8, deGov, Thunder, Varbase, Commerce, OpenSocial and the Out of the Box initiative. It was great to see how much progress the distribution space has already made in Drupal 8. Distributions are an excellent way to highlight what Drupal can do and push for reusable, generic solutions. As I had worked 4 years with the epiqo team on Recruiter, one of the first Drupal 7 distributions, this was also a good reminder of the interesting challenges we face when creating products based on Drupal. In addition, the panelists also discussed how to best manage configurations using approaches like Features and Config Split.
Local Communities starting to collaborate
Another highlight was the discussions around aligning Drupal community efforts. The project, Local Community Distribution, was created to combine efforts in order to build and maintain local community websites. Representatives from various country initiatives were brought together, along with neighbouring countries such as France and the Netherlands, to share their codebases in the interim, which can be used as a solid foundation to get these projects off the ground. Details of the discussion can be found in this ticket.
Coincidentally, we recently started an initiative to create a new Drupal Switzerland website, so keep an eye on our group’s page or join one of the Zurich Meetups to follow the progress and join the discussion.
Communication moving from Slack to DrupalChat
Over the last few years, a large percentage of instant communication has moved from IRC to Slack because of superior usability. Unfortunately, Slack’s commercial focus limits the community using it - currently most of our channels appear empty due to the fact that Drupal Slack hides old messages. The local communities, therefore, decided to go for DrupalChat.eu as an alternative. If you are interested, follow this issue or join the BOF at DrupalCon NA.
Drupal 8 Initiatives are making progress
In my talk - Drupal 8 Initiatives, I tried to give an overview of the status, history and achievements of the initiatives that are contributing to the Drupal 8 project. It was a great opportunity to highlight how much Drupal 8 has already been evolving over the years as well as to show how any future contributions can be done collaboratively.
In the spontaneous session, we spoke about Agile and Project Management practices as well as the #d8rules initiative.
Keeping an eye on upcoming Drupal events in Europe
Thanks to the DrupalCamp Ruhr team for putting together such a dynamic event!
We are really looking forward to more collaboration and exchanges within the Drupal community during 2018. For those who can’t make it to DrupalCon Nashville, 9-13 April, Europe has you covered. Keep an eye on these events:
As usual, you can also find many more regional events on Drupical and finally, if you are interested in an unconference using the Open Space format, make sure to join us for Agile Lean Europe Zürich 2018, August 22-24.
A 100-player Fortnite livestream hosted by Spanish YouTuber Rubén Doblas Gundersen garnered over 1.1 million viewers. ...
Mark was struck by a car following GDC this past week, and a network of game developers have come together to help his family with travel expenses, medical costs, and rehabilitation. ...
As I mentioned in the closing remarks, this year’s MidCamp was a roller coaster ride. And as I said to people in the halls: the actual camp is the easy part; it’s getting there that is the real challenge.
One would think that after five years of planning MidCamp, this would get easier. Sadly, this has not been the case. Our primary challenge year to year is organizer burnout. The core team keeps shrinking and inevitably someone takes on a significant burden to keep camp on course. This year, that was me, though I’m either too stubborn or too stupid to walk away from the project.
Some specific challenges we faced this year:
- We overreached with the site rebuild, giving us a late start to crucial things like selling sponsorships and opening the call for papers
- We were $15k below our revenue goals just four weeks before camp
- We succeeded in finally getting DePaul faculty to underwrite us as an internal event (which would have saved on both venue rental and catering fees) only to find out that we were too far in the process (and then later find out we will forever be an external event)
To stay afloat, we made adjustments:
- We increased training ticket costs to cover food and training day venue rental
- We canceled all but coffee and water for session days and the Sunday sprint
- We cut any rooms not used for sessions and we massaged our schedule and room reservations (DePaul is unique in letting us reserve by the hour versus whole or half day like many other venues)
- We cut all but limited snacks at the after parties
The extra hours picking up the slack, the repeated bad news, constant fretting over the budget, and all these cuts really made me start to wonder if MidCamp was worth the effort.
I’m at a dozen or more camps each year. The unsolicited MidCamp love I hear at these camps is what keeps me going. And it was also the reason I could not fathom why we were falling apart at the seams. The community seems to think this is a viable camp, but in all other ways, we were not hitting the mark. Which got me thinking this could very well have been the fifth and final MidCamp.
It was with this in mind that I reached out to Twitter with what I call my hat-in-hand tweet. And the community proved, in no uncertain terms, that this camp matters. We hit record numbers of individual sponsors and received over $1,000 in donations, which we’ve never taken before. And sponsors followed with a last-minute show of support.
We had money again, which meant it was time to reverse some of our cuts. Yet the changes we were forced to make had some unforeseen consequences, the most glaring of which was the cavernous emptiness of the main room. This is a model we lifted from DrupalCorn Camp early on and it worked well for a while. But this year it was a colossal fail as people, by and large, did not return to the main room to eat their lunch after grabbing it from the cafeteria, which meant almost no foot traffic for sponsor tables, and a $5,000-per-day room hosting only a few dozen people outside of the keynote, lightning talks, and camp closing.
So with attendee and sponsor feedback, plus diligent head counts of every room every hour (including the main room), we are now armed with actual data instead of anecdotal recollections:
- The multi-purpose sponsor/bof/keynote room was a bust
- There was a 33% drop in session attendance from Friday to Saturday (yikes!)
- And MidCamp—while amazing—was just another camp
It’s time for change. Here is what’s in store for 2019:
- Condensing all of camp to a single floor of the student center
- Allowing slightly longer time between sessions
- Shifting the schedule so that sessions are Thursday and Friday, to address attendance drop-off
- Adding summits to the training day before camp starts to draw more attendance
- Curating sprint initiatives and marketing them early, again to draw more attendance
- Leveraging MidCamp as the onramp to DrupalCon
And that, my friends, brings us to the amazing Druplichaun we revealed for O’MidCamp. To roll camp back a day, we need to push to the following week in 2019, March 20-23. So if you caught sight of the little fella, know that he got away this time, but we anticipate seeing him again in the future.
Feel free to come to Chicago early and watch the river turn green, escape the Chi-rish, and do some fun things with the local community while we ramp up for an all-new MidCamp.
If you made it this far, thanks for reading and consider getting involved! Join the Slack at https://midcamp-slack.herokuapp.com/
See you around,
MidCamp 2019 Fearless Leader (among other things)
Registry On Steroïds(ROS) discovers and adds additional theme preprocess/process functions for theme hook variants, if theme() is called with a variant name. E.g. for theme('node__article__teaser', ..), it will call functions like MYTHEME_preprocess_node__article__teaser() and MYTHEME_preprocess_node__article() in addition to MYTHEME_preprocess_node().