Aggregator settings error after installing on D10

Created on 22 May 2024, 7 months ago
Updated 29 May 2024, 7 months ago

I've installed Aggregator modrule on Drupal 10.2.6. It seems working. But if go to admin/config/services/aggregator/settings, it displays a blank page with the message "The website encountered an unexpected error. Try again later.""

I checked Recent log message:
Error: Interface "Laminas\Feed\Reader\ExtensionManagerInterface" not found in include() (line 13 of .../public_html/m/modules/aggregator/src/ZfExtensionManagerSfContainer.php).

How to solve this issue?

πŸ’¬ Support request
Status

Active

Version

2.2

Component

Code

Created by

πŸ‡³πŸ‡±Netherlands astra

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @astra
  • πŸ‡³πŸ‡±Netherlands astra
  • πŸ‡³πŸ‡±Netherlands astra
  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    Did you install using composer?

  • Issue was unassigned.
  • πŸ‡³πŸ‡±Netherlands astra
  • πŸ‡³πŸ‡±Netherlands astra

    I didn't use composer to install it. The Drupal site is hosted on Hostinger. I installed Aggregator by Add new module of Extent at the site backend.

  • Status changed to Closed: works as designed 7 months ago
  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    This module has third party dependencies and can only be installed with composer

  • πŸ‡³πŸ‡±Netherlands astra

    I tried using composer to install Aggregator via SSH:
    composer2 require "drupal/aggregator:^2.2"
    But I got the message: No security vulnerability advisories found

    It cannot complete installation. What's wrong?

  • Status changed to Active 7 months ago
  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    It is difficult to debug what's wrong in your environment

    Can you confirm your project has a root composer.json file and started from a composer template?

  • πŸ‡³πŸ‡±Netherlands astra

    Yes, I can see composer.json under the root.
    By the way, my Drupal 10 site is on a subdomain. I went to the subdomain folder and use composer:
    composer2 require "drupal/aggregator:^2.2"

    Anything wrong?

  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    You need to run composer commands in the same folder as the composer.json file

    Can you share your composer.json file?

  • πŸ‡³πŸ‡±Netherlands astra

    I don't know how to share composer.json file. You can tell me how to.

    My sites hosted on Hostinger. I logged in to SSH and I can see 2 folders in the root:
    domains
    public_html
    I can find composer.json under the public_html
    My Drupal 10 site is installed to the subdomain m.helan123.com, I can go to the folder:
    domains/helan123.com/public_html/m

    where do I run composer to install the Aggregator module?

  • πŸ‡ΊπŸ‡ΈUnited States dcam

    It sounds like you need to run it in the public_html directory. Run composer show there and see if it lists drupal/core and other modules. If it does, then that's where you should require Aggregator.

  • πŸ‡³πŸ‡±Netherlands astra

    Run composer2 show in the public_html(not a root of Drupal), I can see it lists:
    ...
    drupal/core 10.2.6
    drupal/core-composer-scaffold 10.2.6
    drupal/core-project-message 10.2.6
    drupal/core-recommended 10.2.6
    drupal/core-vendor-hardening 10.2.6
    ...

    But the public_html directory is not the root of my Drupal site where I want to install modules. Is it possible to run composer here?

    I have multiple Drupal sites hosted in the same Hostinger account, they are in other directories like:
    domains/drupalsite1.com/public_html
    domains/drupalsite2.com/public_html
    domains/drupalsite2.com/public_html/subsite

    Now I want install Aggregator to the subsite:
    domains/helan123.com/public_html/m

    Where do I run composer to install the Aggregator module to the specific site?

  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    You can run it anywhere there is a composer.json file and the output of composer show includes Drupal core.

    Note that if you run it in the public html folder, the code might be available to install on all the domains, but you don't have to enable the module in all of them. Composer require just downloads all the needed files and libraries

  • πŸ‡³πŸ‡±Netherlands astra

    I run composer in the public_html:
    composer2 require "drupal/aggregator:^2.2"

    I can see the message:
    ...
    In Filesystem.php line 284:
    Could not delete /home/.../public_html/sites/default/default.services.yml:
    ...

    Is it something wrong?

  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    It is most likely file permissions on the sites/default folder

  • πŸ‡³πŸ‡±Netherlands astra

    Okay, I will update the file permissions and try it again.

    I don't like the Aggregator module is downloaded to multiple Drupal sites that don't need this module. If install the Aggregator module to the specific site, Is there any solution?

    Should I copy composer.json file to the Drupal directory and run composer there?

  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    Aggregator was part of core until D10
    It was on disk on many sites without being installed

  • πŸ‡³πŸ‡±Netherlands astra

    Yes, Aggregator is in core before D10 that's easy for me to use without installing and updating myself. I have several old version Drupal sites with Aggregator. Now it's difficulty to install with D10. I like using this module and maybe often need to install and update it. I'm a Drupal fan use use it from D4 to D10. I'm not a techical of Drupal, So I need find a good solution.

    Now I have 2 sites of D10 with different domains, and more new Drupal sites in the future that share the composer system on Hostinger. But I need using composer to install Aggregator and other extent modules for a single site.

    So I want to know where to run:
    composer2 require "drupal/aggregator:^2.2"

    It can only install the module to the site:
    domains/helan123.com/public_html/m

    Is there any solution?

  • πŸ‡³πŸ‡±Netherlands astra

    I copy the content of composer.json here. I see the line "url": "https://packages.drupal.org/8". It seems for D8.
    Anything wrong to use it for D10?

    {
    "name": "drupal/legacy-project",
    "description": "Project template for Drupal projects with composer following drupal/drupal layout",
    "type": "project",
    "license": "GPL-2.0-or-later",
    "homepage": " https://www.drupal.org/project/drupal β†’ ",
    "support": {
    "docs": " https://www.drupal.org/docs/user_guide/en/index.html β†’ ",
    "chat": " https://www.drupal.org/node/314178 β†’ "
    },
    "repositories": [
    {
    "type": "composer",
    "url": "https://packages.drupal.org/8"
    }
    ],
    "require": {
    "composer/installers": "^2.0",
    "drupal/aggregator": "^2.2",
    "drupal/core-composer-scaffold": "^10.2",
    "drupal/core-project-message": "^10.2",
    "drupal/core-recommended": "^10.2",
    "drupal/core-vendor-hardening": "^10.2"
    },
    "conflict": {
    "drupal/drupal": "*"
    },
    "minimum-stability": "stable",
    "prefer-stable": true,
    "config": {
    "allow-plugins": {
    "composer/installers": true,
    "drupal/core-composer-scaffold": true,
    "drupal/core-project-message": true,
    "drupal/core-vendor-hardening": true,
    "phpstan/extension-installer": true,
    "dealerdirect/phpcodesniffer-composer-installer": true,
    "php-http/discovery": true
    },
    "sort-packages": true
    },
    "extra": {
    "drupal-scaffold": {
    "locations": {
    "web-root": "./"
    }
    },
    "installer-paths": {
    "core": [
    "type:drupal-core"
    ],
    "libraries/{$name}": [
    "type:drupal-library"
    ],
    "modules/contrib/{$name}": [
    "type:drupal-module"
    ],
    "profiles/contrib/{$name}": [
    "type:drupal-profile"
    ],
    "themes/contrib/{$name}": [
    "type:drupal-theme"
    ],
    "drush/Commands/contrib/{$name}": [
    "type:drupal-drush"
    ],
    "modules/custom/{$name}": [
    "type:drupal-custom-module"
    ],
    "profiles/custom/{$name}": [
    "type:drupal-custom-profile"
    ],
    "themes/custom/{$name}": [
    "type:drupal-custom-theme"
    ]
    },
    "drupal-core-project-message": {
    "include-keys": [
    "homepage",
    "support"
    ],
    "post-create-project-cmd-message": [
    " ",
    " Congratulations, you’ve installed the Drupal codebase ",
    " from the drupal/legacy-project template! ",
    " ",
    "",
    "Next steps:",
    " * Install the site: https://www.drupal.org/docs/installing-drupal β†’ ",
    " * Read the user guide: https://www.drupal.org/docs/user_guide/en/index.html β†’ ",
    " * Get support: https://www.drupal.org/support β†’ ",
    " * Get involved with the Drupal community:",
    " https://www.drupal.org/getting-involved β†’ ",
    " * Remove the plugin that prints this message:",
    " composer remove drupal/core-project-message"
    ]
    }
    }
    }

  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    You should run the command in public_html
    Your composer.json looks it already has aggregator in it?

  • πŸ‡³πŸ‡±Netherlands astra

    Yes, I have run composer in public_html:
    composer2 require "drupal/aggregator:^2.2"

    I checked it at the site backend. The Aggregator module is available in every D10 site (the code is available to install on all the domains). I can enable Aggregator of the D10 site in the root public_html. It looks that composer works well. But I don't need Aggregator for this site.

    Then For the site (m.helan123.com) that I need install Aggregator, I go to Extent/Web services, check Aggregator and click on Install. The module cannot be enabled but I get the message:
    Error message
    Unable to install Aggregator, filter.format.aggregator_html already exists in active configuration.

    What's wrong?

  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    That sounds like carry over from a previous install that failed.

    If you visit admin -> config -> content authoring -> input formats - can you delte the aggregator html format and try again?

    If not, do you have access to drush?

    If so, can you run `drush cdel filter.format.aggregator_html` and then try again to reinstall

  • πŸ‡³πŸ‡±Netherlands astra

    I use composer to install drush in public_html:
    composer require --dev drush/drush

    Execute the following command to check:
    ./vendor/bin/drush --version
    Drush Commandline Tool 12.5.2.0

    I ran drush but got commad not found:
    drush cdel filter.format.aggregator_html
    -bash: drush: command not found

    drush doesn't work?

  • πŸ‡ΊπŸ‡ΈUnited States dcam

    Does the same thing happen if you run vendor/bin/drush cdel filter.format.aggregator_html?

  • πŸ‡³πŸ‡±Netherlands astra

    Okay I will try running vendor/bin/drush cdel filter.format.aggregator_html

    But I don't understand why run drush to delete somthing in public_html (root)? because no problem to enable Aggregator in this site.

    Should I install drush again to the site (domains/helan123.com/public_html/m) that has the problem of Aggregator?

    Where to run drush?

  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    Please try to delete from the UI first

  • πŸ‡³πŸ‡±Netherlands astra

    Do you mean to uninstall Aggregator from the UI?

    The problem is that Aggregator cannot be enabled, I can't find it in the Uninstall list of the UI.

  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    No, the filter format - see comment 24

  • πŸ‡³πŸ‡±Netherlands astra

    I forgot to tell you that I had deleted the aggregator html format already but the problem still couldn't be solved. Then I tried thrush.

  • πŸ‡³πŸ‡±Netherlands astra

    Should I install drush again to the site (domains/helan123.com/public_html/m) that has the problem of Aggregator?

  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    If you've deleted the filter format, you should now be able to enable aggregator module

  • πŸ‡³πŸ‡±Netherlands astra

    No. Still unable to install it. See the screenshots attached.
    Error message
    Unable to install Aggregator, filter.format.aggregator_html already exists in active configuration.

  • πŸ‡¦πŸ‡ΊAustralia larowlan πŸ‡¦πŸ‡ΊπŸ.au GMT+10

    Seems like it wasn't deleted then?

  • πŸ‡³πŸ‡±Netherlands astra

    The Aggregator HTML format had been deleted, but it's still not possible to enable Aggregator.

Production build 0.71.5 2024