Dear maintainers:

Trying to install Dynamic Layouts via composer (composer require 'drupal/dynamic_layouts:^1.4') leads to:

Installation failed, reverting ./composer.json to its original content.

[InvalidArgumentException]
The given package is missing url information

Regards,
Maruthi

Comments

maruthi9999 created an issue. See original summary.

falco010’s picture

falco010
Location 🇳🇱 The Netherlands
commented
Issue summary: View changes

Hi Maruthi,

I could reproduce this, however I am not sure what is causing this. Maybe there is something wrong with the composer packages on Drupal.

A solution that worked for me was this:

  1. composer require 'drupal/dynamic_layouts:1.x-dev'
  2. composer require 'drupal/dynamic_layouts:^1.4'
cshimer’s picture

cshimer commented

Good day,

I was able to install version 8.x-1.4 but was getting the same error and noticed that version 8.x-1.4 is missing the version number in the "dynamic_layouts.info.yml" file. When I cleared cache I was also seeing a warning: "Module dynamic_layouts has an entry in the system.schema key/value [warning]".

Line numbers 10 - 13 in the previous version's info file are missing in this new version.

# Information added by Drupal.org packaging script on 2018-03-08
version: '8.x-1.3'
core: '8.x'
project: 'dynamic_layouts'

Cheryl Shimer
IQ Solutions, Inc.

maruthi9999’s picture

maruthi9999 commented

After I have tried with the step 1 and 2 in the comment#2 , then I am able to install the module. Thank you for the solution,
And when i tried to create a new layout using dynamic layouts I am getting following errors.

Access denied
"You are not authorized to access this page."

Should I create a new issue for the above warnings?
Also in the module permissions, I am not seeing checkbox on admin column.
Thank you verymuch on your response

  • fabianderijk committed ec591a6 on 8.x-1.x 
    Issue #3163318: Getting composer error while installing module
fabianderijk’s picture

fabianderijk
him/his
Primary language Dutch
Location Alphen aan den Rijn
commented
Status: Active » Fixed

This is now fixed in the 8.x-1.5 release. I removed a bit to much from the info.yml file....

Status: Fixed » Closed (fixed)

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