Closed (fixed)
Project:
Social Post Twitter
Version:
3.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
26 Nov 2021 at 17:12 UTC
Updated:
28 Jun 2022 at 15:19 UTC
Jump to comment: Most recent
While releasing new major version releases of Social Post Twitter for Drupal 9, and because Drupal 9 now supports PHP 8 (and recommends only PHP 7.4 or PHP 8.0, and drops support below PHP 7.3), we really should switch to recent releases of the underlying TwitterOauth library.
Try to install Twitter Oauth with Composer while using PHP 8:
project [drupal9]$ composer update
Gathering patches for root package.
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.
Problem 1
- abraham/twitteroauth[0.7.0, ..., 0.7.4] require php ^5.6 || ^7.0 -> your php version (8.0.11) does not satisfy that requirement.
- abraham/twitteroauth[0.9.0, ..., 0.9.2] require php ^5.6 || ^7.0 || ^7.1 || ^7.2 -> your php version (8.0.11) does not satisfy that requirement.
- drupal/social_post_twitter 3.x-dev is an alias of drupal/social_post_twitter dev-3.x and thus requires it to be installed too.
- drupal/social_post_twitter dev-3.x requires abraham/twitteroauth ~0.7 -> satisfiable by abraham/twitteroauth[0.7.0, ..., 0.9.2].
- Root composer.json requires drupal/social_post_twitter 3.x-dev@dev -> satisfiable by drupal/social_post_twitter[3.x-dev (alias of dev-3.x)].
Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
composer [update] failed, composer command failed: exit status 2. stderr=
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
Anonymous (not verified) commentedHi, Is this issue planned to be fixed? We're currently unable to get Social Post Twitter to work with PHP 8 (recommended for Drupal 9) without this fix. Thanks.
Comment #5
saidatomComment #8
wellsThanks for the report and MR! This change is in the 3.0.0-beta3 release.
Comment #9
wells