Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
I'm trying to update a site from Drupal 8.4.4. to 8.6.1 but composer seems to be hitched up on something. Initially when running composer update drupal/core webflo/drupal-core-require-dev symfony/* --with-dependencies I was getting the error Package "drupal/core" listed for update is not installed. Ignoring. So I deleted my composer.lock and tried to run composer install again, it finally gave me something usable to go off of, but I'm stuck again. My new error reads:
I installed Social Auth Google with all it's dependencies, using composer, on a local Xampp install. It's working fine and I'm popped up for my Google authentication page. API credential, authorized URL's and callback have been properly defined at Google side.
However, when authenticating the Drupal callback page give following error :
The website encountered an unexpected error. Please try again later.
Cache has been purged and so on.... Beside this, test site is running fine.
I am currently trying to install the S3FS module for my existing Drupal 8 Site. One of the requirements the AWS SDK for PHP v3. Most of the examples I can find online are using Composer to setup their site and then install the module with all its dependencies via Composer.
My current site however isn't setup using Composer so I am wondering how to install this on to my existing site without having to convert my site to a Composer managed site.
I'm getting a mind-boggling push at my firm, internally, to push to Wordpress. The argument is that it's more secure than Drupal and Drupal's market share is dropping.
Mind-boggling, because everything I find is counter to that argument. It's such a strange thing, but they seem to have traction thanks to Drupalgeddon 2 as their arguing point.
My Drupal-8 website has repeatedly experienced a vulnerability which induced it to send outbound unsolicited email. On the account sign up page I employ reCaptcha and an email confirmation requirement. The problem is that malicious agents are able to crack the CAPTCHA and submit bogus email addresses. My server unwittingly sends out confirmation requests to the bogus addresses, causing my domain to get blacklisted for spamming. Does anyone have a suggestion how to combat this vulnerability?