Apple arbeitet angeblich an Bügelkopfhörern mit Geräuschunterdrückung
CSU im Kabinett: Bär wird Digitalstaatsministerin, Scheuer Minister für digitale Infrastruktur
Größere Zeichen oder Smartphone-Leser laufen ins Verderben
Continuous Lifecycle London: Frühbucherrabatt verlängert
Zeit-Synchronisation per Stromnetz: Konflikt zwischen Serbien und Kosovo lässt Uhren nachgehen
Daimler geht mit vollelektrischem Stadtbus in Serie
Jabra Elite 65t: spitzenmäßiges True-Wireless-Headset im Test
Russland will in Mondforschung auch enger mit China zusammenarbeiten
WeKnow: How to install Drupal 8 from an existing configuration
The Configuration Management (CM) system, is probably one of the most well known and exciting features of Drupal 8. But wouldn't be even more awesome to be able to install a site, export configuration and then re-install site from scratch importing the previously exported configuration?
For those who are not yet clear what we are talking about, this post is related to fixing the infamous exception error message when importing configuration:
"Site UUID in source storage does not match the target storage."
Why would you want to be able to install your site from an existing configuration?Automate the creation of reproducible build/artifacts from scratch at any stage (Development, QA, Production) to test, launch or deploy your site.
jmolivas Wed, 03/07/2018 - 08:03Amazon-Gründer Jeff Bezos ist reichster Mensch der Welt
Elektroautos: Telekom will ab Sommer Verteilerkästen zu Ladestationen aufrüsten
Bank-APIs: Welche gibt es und was bieten sie?
WordPress dominiert die Content-Management-Systeme
Aldi Nord: 49-Zoll-Fernseher mit 4K und HDR für 380 Euro, Coffee-Lake-Komplettsystem für 500 Euro
Amazon will keine Google-Nest-Geräte mehr verkaufen
Into the Breach angespielt: Taktikperle von den FTL-Machern
Webinar: Bereit für die DSGVO?
Bei 40 günstigen Android-Smartphones ist ein Trojaner ab Werk inklusive
Acro Media: CiviCRM Installation in Drupal 8 & Commerce 2
It’s amazing how, just a couple of years ago, Drupal 8 was in its initial stages and was getting ready for its first stable release. But now, in 2018, we have stable releases and contributed module development on D8 has been progressing rapidly (as of this writing, we’re at nearly 5,000 D8 modules). CiviCRM, the best open source customer management tool, is one such community contributed integration that has been making such Drupal 8 strides.
When one of our clients needed their D7 CiviCRM ported over to their new D8 site, the prospects were not good: CiviCRM seemed to be lagging behind and the general online consensus was that things weren’t working, and boy are we glad the internet was wrong. The people behind the open-source content management framework has gotten its D8 version out and interestingly, most of it works beautifully. To our surprise (and relief!), the integration with the D8 site went incredibly well, of course, with a few kinks here and there. Those kinks are primarily due to the fact that Civi ships with its own Symfony version, which is a different version than what Drupal uses and that causes a conflict. For more information on it, read here.
We were able to do our Civi installation by following the steps mentioned in the wonderful blog by David Snopek. So, even though it was a bit complicated, it was definitely a learning experience for us and we thought we would share some of that knowledge here. In this blog we’ll be detailing how to install the richly packed Customer Relationship Management tool called CiviCRM on an existing Drupal 8 Commerce 2 ecommerce store. However, if you’d like to install a new Vanilla Drupal Commerce 8 site with CiviCRM already setup, we’d suggest you follow the easy-to-use instructions in Snopek’s blog.
Steps for Installing CiviCRM (Existing Installation)In Drupal 8, installing CiviCRM is a bit more complicated than doing just a simple...
$ composer require drupal/civicrm
...like you would for other modules.
If you are waiting for a more standardized policy/process for installing Civi, it might not be in the near future, as the maintainers feel that we already have a process that works and they want to spent their time concentrating on getting the actual module more stable and fixing functional bugs. They also need to come together and agree upon what is the best way to organize the code and do its build. So, the process to get it installed on a D8 installation requires quite a few steps, but if you do it right, it will work.
Below we’ve tried to slim down those steps and made it a bit more concise, so that, essentially, all you would need to do is copy and paste the commands and be on your way to using a fully integrated CiviCRM on top of Drupal 8. It took us a couple of attempts to get it right when we first installed it as some of the steps were in different places and missing a step would mean you had to start over.
Installing CiviCRM on an existing D8 sitePrerequisites:
- Composer - not just the tool, but your Drupal 8 site should be using composer to manage dependencies.
- Bower - another package management tool. Yes, we are rich with package managers in this process.
- Git - Source control (managing the code that runs your site) is an essential part of every build, but particularly, it’s a requirement of Composer, because it uses that source control to lock down which packages you are building on.
Note: as CiviCRM Core hasn’t been added to Packagist yet, we’ll be using David Snopek’s fork.
- In your D8 installation, ensure that your "Vendor" directory is outside of your document root. So your directory structure would be like this:
your_d8_site_directory
├─ composer.json
├─ composer.lock
├─ vendor
└─ web (your document root) - Create a backup of your database.
- Go to our github repository, civicrm_d8_install_script, and copy the .env and civicrm_setup.sh files to your Drupal 8 project root directory.
- Run civicrm_setup.sh from your project root directory.
bash ./civicrm_setup.shThis will download all the necessary modules and dependencies needed to install CiviCRM. - Now, go to the "Extend" page (at /admin/modules) and install the CiviCRM module.
- This will create a civicrm.settings.php in your "/sites/default directory" which contains information about where the database is, etc.
- This will also create all the necessary tables in your Drupal database.
- Logout of Drupal and log back in again.
- Say what? Yeah, this is needed to sync your logged-in account with CiviCRM contacts.
- Get the Civi theme to apply by going to "/civicrm/admin/setting/url?reset=1" and set the CiviCRM Resource URL to "/vendor/civicrm/civicrm-core" and click “Save”.
- If everything worked correctly, you should see a CiviCRM link up at the top.
- Click on the CiviCRM link and you should be taken to a page like this:
- You can also confirm that the module is actually working by typing in the email of the user that you are logged in as, and it should bring up the contact in CiviCRM. This means that contacts are automatically being synced between Drupal and CiviCRM.
And that is it, you can throw your hands up in the air to celebrate, as you’ve just installed CiviCRM in a matter of minutes.
More from Acro Media- Blog: Quickbooks Enterprise Integration in Drupal Commerce 2
- View some of our Drupal Commerce modules
- Learn more about Drupal Commerce integrations
Would you like Quickbooks integrated into your Drupal Commerce website, but need a hand doing it? We've done it many times and would love to help.
Dries Buytaert: Cooking with Alexa and Drupal
When I'm home, one of the devices I use most frequently is the Amazon Echo. I use it to play music, check the weather, set timers, check traffic, and more. It's a gadget that is beginning to inform many of my daily habits.
Discovering how organizations can use a device like the Amazon Echo is big part of my professional life too. For the past two years, Acquia Labs has been helping customers take advantage of conversational interfaces, beacons and augmented reality to remove friction from user experiences. One of the most exciting examples of this was the development of Ask GeorgiaGov, an Alexa skill that enables Georgia state residents to use an Amazon Echo to easily interact with government agencies.
The demo video below shows another example. It features a shopper named Alex, who has just returned from Freshland Market (a fictional grocery store). After selecting a salmon recipe from Freshland Market's website, Alex has all the ingredients she needs to get started. Alex begins by asking Alexa how to make her preferred salmon recipe for eight people. The recipe on Freshland Market's Drupal website is for four people, so the Freshland Market Alexa skill automatically adjusts the number of ingredients needed to accommodate eight people. By simply asking Alexa a series of questions, Alex is able to preheat the oven, make ingredient substitutions and complete the recipe without ever looking at her phone or laptop. With Alexa, Alex is able to stay focused on the joy of cooking, instead of following a complex recipe.
This project was easy to implement because the team took advantage of the Alexa integration module, which allows Drupal to respond to Alexa skill requests. Originally created by Jakub Suchy (Acquia) and maintained by Chris Hamper (Acquia). The Alexa integration module enables Drupal to respond to custom voice commands, otherwise known as "skills".
Once an Amazon Echo user provides a verbal query, known as an "utterance", this vocal input is converted into a text-based request (the "intent") that is sent to the Freshland Market website (the "endpoint"). From there, a combination of custom code and the Alexa module for Drupal 8 responds to the Amazon Echo with the requested information.
Over the past year, it's been very exciting to see the Acquia Labs team build a connected customer journey using chatbots, augmented reality and now, voice assistance. It's a great example of how organizations can build cross-channel customer experiences that take place both online and offline, in store and at home, and across multiple touch points. While Freshland Market is a fictional store, any organization could begin creating these user experiences today.
Special thanks to Chris Hamper and Preston So for building the Freshland Market Alexa skill, and thank you to Ash Heath and Drew Robertson for producing the demo videos.