Problem/Motivation

This module appears to be a good approach to add a feature to a D9 site. But running
composer require 'drupal/entity_word:^2.7'
returns
drupal/entity_word 2.x-dev is an alias of drupal/entity_word dev-2.x and thus requires it to be installed too.
- drupal/entity_word[dev-2.x, 2.7.0] require phpoffice/phpword 0.17.0 -> satisfiable by phpoffice/phpword[0.17.0].
- phpoffice/phpword 0.17.0 requires zendframework/zend-escaper ^2.2 -> satisfiable by zendframework/zend-escaper[2.2.0rc1, ..., 2.7.x-dev (alias of dev-develop)].
- laminas/laminas-escaper 2.9.0 conflicts with zendframework/zend-escaper 2.6.1.

Cannot understand the first problem. Running a dev module in production is not considered best practice?

Is the required depedency zendframework/zend-escaper incompatible with drupal/core-recommended? If so, how to build a Drupal that is secure and is current?

Steps to reproduce

Create a fresh drupal 9 site using drupal/core-recommended.
Run composer require 'drupal/entity_word:^2.7'

Proposed resolution

Determine if project is compatible with Drupal 9.

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork entity_word-3283503

Command icon Show commands

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:

About issue forks

Comments

sam452 created an issue. See original summary.

mmjvb’s picture

mmjvb commented
Component: Documentation » Code
Status: Active » Needs review

Suggest to use ~0.18.3 instead to allow for further bug fixes.

jayprakash01 opened merge request !1

jayprakash01 made their first commit to this issue’s fork.

jayprakash01 opened merge request !2

  • jayprakash01 committed e70eae7 on 8.x-2.x 
    Issue #3283503: laminas/laminas-escaper 2.9.0 conflicts with...

  • jayprakash01 committed 05282c4 on 8.x-2.x 
    Issue #3283503 by sam452: updated phpoffice version
jayprakash01’s picture

jayprakash01 commented
jayprakash01’s picture

jayprakash01 commented
Version: 8.x-2.7 » 3.0.0
Status: Needs review » Fixed

Request changes are implemented. Now it is fixed.

mmjvb’s picture

mmjvb commented
Status: Fixed » Needs work

Not really!

The website encountered an unexpected error. Please try again later.

Drupal\Core\Extension\InfoParserException: The 'core_version_requirement' constraint (^8.8 || ^9) requires the 'core' key not be set in modules/contrib/entity_word/entity_word.info.yml in Drupal\Core\Extension\InfoParserDynamic->parse() (line 91 of core/lib/Drupal/Core/Extension/InfoParserDynamic.php).
Drupal\Core\Extension\InfoParser->parse('modules/contrib/entity_word/entity_word.info.yml') (Line: 554)
Dru

This is because it doesn't make sense to declare support for older D8 versions when you only allow above 8.8. So, the core key needs to go.

- While you are at it you might want to change composer.json:
-- use correct name: "name": "drupal/entity_word",
-- Set a proper license:- License "GPL-2.0+" is a deprecated SPDX license identifier, use "GPL-2.0-or-later" instead
-- Allow for bug fixes: "phpoffice/phpword": "~0.18.3",

  • 7ff5802 committed on 8.x-2.x 
    Issue #3283503, #3109084, #3109086 by [mmjvb, rgristroph]: Fixed issue
jayprakash01’s picture

jayprakash01 commented
Status: Needs work » Fixed

Thanks @mmjvb. Fixed now.

mmjvb’s picture

mmjvb commented

Thanks, released in 3.1.0 today.

Probably too early for ^10 as that is in alpha5.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.