Drupal News

erdfisch: Drupalcon mentored core sprint - part 2 - your experience as a sprinter

  • Drupalcon mentored core sprint - part 2 - your experience as a sprinter 12.05.2018 Michael Lenahan Body:  Drupalcon mentored core sprint - part 2 - your experience as a sprinter

    Hello! You've arrived at part 2 of a series of 3 blog posts about the Mentored Core Sprint, which traditionally takes place every Friday at Drupalcon.

    If you haven't already, please go back and read part 1.

    You may think sprinting is not for you ...

    So, you may be the kind of person who usually stays away from the Sprint Room at Drupal events. We understand. You would like to find something to work on, but when you step in the room, you get the feeling you're interrupting something really important that you don't understand.

    It's okay. We've all been there.

    That's why the Drupal Community invented the Mentored Core Sprint. If you stay for this sprint day, you will be among friends. You can ask any question you like. The venue is packed with people who want to make it a useful experience for you.

    Come as you are

    All you need in order to take part in the first-time mentored sprint are two things:

    • Your self, a human who is interested in Drupal
    • Your laptop

    To get productive, your laptop needs a local installation of Drupal. Don't have one yet? Well, it's your lucky day because you can your Windows or Mac laptop set up at the first-time setup workshop!

    Need a local Drupal installation? Come to the first-time setup workshop

    After about half an hour, your laptop is now ready, and you can go to the sprint room to work on Drupal Core issues ...

    You do not need to be a coder ...

    You do not need to be a coder to work on Drupal Core. Let's say, you're a project manager. You have skills in clarifying issues, deciding what needs to be done next, managing developers, and herding cats. You're great at taking large problems and breaking them down into smaller problems that designers or developers can solve. This is what you do all day when you're at work.

    Well, that's also what happens here at the Major Issue Triage table!

    But - you could just as easily join any other table, because your skills will be needed there, as well!

    Never Drupal alone

    At this sprint, no-one works on their own. You work collaboratively in a small group (maybe 3-4 people). So, if you don't have coding or design skills, you will have someone alongside you who does, just like at work.

    Collaborating together, you will learn how the Drupal issue queue works. You will, most likely, not fix any large issues during the sprint.

    Learn the process of contributing

    Instead, you will learn the process of contributing to Drupal. You will learn how to use the issue queue so you can stay in touch with the friends you made today, so that you fix the issue over the coming weeks after Drupalcon.

    It's never too late

    Even if you've been in the Drupal community for over a decade, just come along. Jump in. You'll enjoy it.

    A very welcoming place to start contributing is to work on Drupal documentation. This is how I made my first contribution, at Drupalcon London in 2011. In Vienna, this table was mentored by Amber Matz from Drupalize.Me.

    This is one of the most experienced mentors, Valery Lourie (valthebald). We'll meet him again in part 3, when we come to the Drupalcon Vienna live commit.

    Here's Dries. He comes along and walks around, no one takes any notice because they are too engaged and too busy. And so he gets to talk to people without being interrupted.

    This is what Drupal is about. It's not about the code. It's about the people.

    Next time. Just come. As a sprinter or a mentor. EVERYONE is welcome, we mean that.

    This is a three-part blog post series:
    Part one is here
    You've just finished reading part two
    Part three is coming soon

    Credit to Amazee Labs and Roy Segall for use of photos from the Drupalcon Vienna flickr stream, made available under the CC BY-NC-SA 2.0 licence.

    Schlagworte/Tags:  planet drupal-planet drupalcon mentoring code sprint Ihr Name Kommentar/Comment Kommentar hinzufügen/Add comment Leave this field blank

    0 sec ago

What kind of testing environment do you use?

  • I run a pretty small site and wanted to really get more in to the development of it. Right now my biggest hurdle is coming up with a good testing environment that I can run locally. I have a copy of Drupal running locally, but am hitting several obstacles when it comes to making it an actual copy of my real site, and seeing how I could actually use it to test other than just doing all the steps there first and then doing it all again in production.

    What kind of testing setups do you use on your sites?

    submitted by /u/Taken4GrantD
    [link] [comments]

    6 hours 49 min ago

Drupal core announcements: Drupal 8 will require PHP 7.0 or higher starting March 6, 2019 (one year from now)

  • Drupal 8 will require PHP 7.0 or higher starting March 6, 2019. Drupal 8 users who are running Drupal 8 on PHP 5.5 or PHP 5.6 should begin planning to upgrade their PHP version to 7.0 or higher. Drupal 8.6 will be the final Drupal 8 version to support PHP 5, and will reach end-of-life on March 6, 2019, when Drupal 8.7.0 is released. (If 8.7.0 is released before March 6, 2019, the release number for the end-of-life will be updated accordingly, but the end-of-life date will remain the same.)

    When planning for which PHP version to upgrade to, consider that PHP 7.2 was released on November 30, 2017 and will remain supported longer than older PHP 7 versions.

    Why is support being dropped for PHP 5.5 and 5.6?
    • PHP 5.5 has already reached official end-of-life in 2016. Following that, a growing number of the PHP libraries used by Drupal 8 have also started to discontinue support for PHP 5.5.
    • PHP 5.6 stopped receiving active support from PHP maintainers in January 2017. This means that it is no longer receiving bugfixes, even for some very serious bugs that impact Drupal development.
    • PHP 5.6 is the final PHP 5 version, so the PHP maintainers are providing two years of security fixes for PHP 5.6 beyond its active support, through December 2018. This is a few months after Drupal 8.6's scheduled release and well before Drupal 8.7 would be released.
    • Drupal 8's automated tests require the PHPUnit library, which will drop support for PHP 5.6 in February 2018. Several other third-party dependencies are also dropping PHP 5.6 support in their latest versions.
    • To minimize disruption for both Drupal users and Drupal developers, Drupal 8's support of PHP 5.5 and PHP 5.6 will end at the same time.

    We understand that upgrading from PHP 5 to PHP 7 may require time to plan and deploy. We suggest upgrading to PHP 7 in 2018 (rather than waiting for Drupal 8.7.0’s release).

    What if I'm using a hosting service that doesn't offer PHP 7?

    A majority of PHP hosting providers already offer PHP 7. If you're using one that doesn't, we suggest asking that provider when they will make it available, and if it's not until after March 2019, leave a comment on our tracking issue linking to that hosting provider, so that we can better understand the outliers, and perhaps offer some help.

    What if I'm at an organization that maintains its own hosting, and we're using Ubuntu 14.04, which bundles PHP 5.5?

    You have a few options if you are using Ubuntu 14.04:

    1. The preferred option is to plan an upgrade to Ubuntu 18.04 (to be released on April 2018, 2018). This version will be the most future-compatible.
    2. Another option is to upgrade Ubuntu 16.04, which is available now. You may need to upgrade Ubuntu again in a couple years if you choose to upgrade to 16.04 now.
    3. Finally, you can choose to upgrade to a separate build of PHP. Ondřej Surý provides a widely used PPA for doing this.
    When will Drupal 8 drop support for PHP 7.0?

    Support for PHP 7.0 will continue until at least March 6, 2019. We do not yet know whether Drupal 8's PHP 7.0 support will continue past that date, but we will post another announcement as soon as the end of PHP 7.0 support has been scheduled. We recommend you update to PHP 7.1 or higher since those versions will be supported longer.

    How does this affect Drupal 8 core development?

    Backported fixes account for about 80% of all changes and must continue to work on PHP 5.5 and 5.6 throughout Drupal 8.6.x's support cycle. For this reason, no PHP 7-only changes will be made until the 8.8.x branch is opened in early 2019 (or 8.9.x if 8.8.0 is released in 2018). Once 8.8.x is opened, the library dependencies in that branch can be updated to versions that have a PHP 7.0 requirement, and the Drupal code itself in that branch can begin relying on PHP 7 features. (Drupal 8 release cycle information)

    The automated test suite already defaults to using PHPUnit 6 on environments that use PHP 7, but falls back to PHPUnit 4 on PHP 5. The fallback will be removed in the 8.8.x branch.

    Does this affect Drupal 7?

    No. Drupal 7 remains compatible with PHP 5.2.4 and higher. A separate announcement will be issued if and when that changes.

    9 hours 34 min ago

ELI5: Progressively Decoupled Drupal vs. Hybrid Wordpress

  • I'm in the process of selecting a CMS architecture and platform to power a site I will build. I'm leaning towards Drupal and the progressively decoupled architecture using the Decoupled Blocks module and either Angular or React for custom components.

    Unfortunately I'm not the only one involved in this decision making process so I had a few questions for anyone that's familiar with both Drupal and Wordpress as content backbones for an enterprise grade site:

    1. What are the advantages of using Drupal vs. Wordpress here? The "Hybrid" decoupling model using WP plugins and theme embedded content is very similar to decoupled blocks in Drupal. Other than the core elements of the platform (e.g. nicer APIs, BigPipe integration) what are the benefits to Drupal's approach here?

    2. Are there any limitations with progressively coupled Drupal content that I should be aware of? I may have a requirement that involves advanced configuration of a Decoupled Block to incorporate what data is fetched and how it is displayed by a marketing user, is this a concern?

    Any help or literature on the subject that compares both platforms would be extremely helpful. Thanks in advanced!

    submitted by /u/jayeffkay
    [link] [comments]

    12 hours 21 min ago

PreviousNext: Ok Drupal - talking to Drupal

WeKnow: Survival guide to Backup & Restore MongoDB

  • Survival guide to Backup & Restore MongoDB

    Despite being on the market for over a decade, to many, MongoDB still carries a mythical tone with a hint of ‘wizardry’.

    The popular misconception is that MongoDB is only suitable for hip startups and former startups that are still considered ‘hip’ and out of the box, such as AirBnB.

    Even with all the buzz and talk around MongoDB, the adoption rate remains relatively low in comparison with other ‘standard’ relational database technologies. Not many seem to understand that to be successful in the world of code you must approach everything new with an open mind.

    Besides bearing an open mind, you need to incorporate an avenue to test and learn new technologies and tools. Personally, I choose to learn how to use new tools by trying to accomplish routine tasks.

    enzo Mon, 01/22/2018 - 19:06

    15 hours 11 min ago

Question about paragraph bundles

  • I am in a situation where my employer has subscribed to the Acquia Drupal platform, and are attempting to incorporate their Lift personalized marketing software into our website. I recently received an email asking for this specific change:

    "We created a node of "Personalised Content" content type that outputs the html (with inline styles) for the banner for Iowa residents on homepage.

    So as a next step to do the same thing in a proper manner (and for other personalisations of the same kind), we need to have created a paragraph bundle that would output the same html. We can then attach the same paragraph to the "Personalised Content" nodes to create the personalisations.

    It's important to note that the css to be used/applied for the output html should be provided by the theme on the pages where we want to set up the personalisations. The aim is to make it easier for content authors to create content without writing html or css themselves."

    I went back to Acquia asking for clarification, and their response is "Lift is unable to supply assistance for this request. They recommend seeking guidance from the Drupal community."

    Honestly, I have moderate experience with Drupal... not an expert, but not a newb either. Can anyone give some advice as to what Lift needs completed? The site has other paragraph bundles, but they all contain fields... text, textboxes. They just say to create a paragraph bundle, and are vague on any other requirements.

    Also... I had nothing to do with selecting Acquia... that decision was made long before I came on board this company. I'm just the one paying the price.


    submitted by /u/heather_ann_69
    [link] [comments]

    15 hours 33 min ago

Drupal 8 - Override backoffice select options and output

Memory (hardware) requirement for Drupal website