I experienced this issue recently while syncing a database from an Acquia hosted dev environment to my local environment. This error led me to investigate the dump file which I found included global transaction identifier (GTID) sets. I was able to work around this issue by suppressing the GTID sets using the --set-gtid-purged=OFF option for the mysqldump command. Combining that option with the drush sql-sync command allows a successful sync.
A local Drupal environment can be created in many different ways. I recommend this approach for many reasons. Most of all, this method is used by many of the top professionals to develop enterprise Drupal sites. Additionally, it's automated, and easy enough for a beginner to get started, without worrying about all the technical details. At least, not to start (smirking).
I ran into an issue implementing reCaptcha on my website, after making several updates and changes to my architecture. The problem was the reCaptcha was always failing, even after every successful submission. In order to figure out the problem, I put the following code in the submit method of the Drupal7Post class.
I received this error when I tried to reinstall Drupal. I was creating a feature to include on other sites, and wanted to make sure everything worked on a clean install. The problem was caused by the following line in my settings.php file, which I added for the Domain Access module:
include './sites/all/modules/contrib/domain/settings.inc';
Commenting out that line allowed Drupal to install successfully.
The only way I could find to have more than one recipient for an email action is to add both the Token and Token Actions modules, and then create a 'Send tokenized email...' action with the recipient email addresses separated by commas. It took me a while to figure this out. So, I hope it helps someone.
