Contrib.social

Move themesPage to ThemeController

Open on Drupal.org →
Created on 22 June 2021, over 3 years ago
Updated 20 October 2023, about 1 year ago

Problem/Motivation

I see a @todo in the JavaDoc for ThemesPage, * @todo Move into ThemeController.

I don't see an issue for this. So this issue is to address that @todo.

Steps to reproduce

Proposed resolution

Either move it to ThemeController, or remove the todo.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

📌 Task
Status

Active

Version

11.0 🔥

Component
Theme  →

Last updated about 20 hours ago

Created by

🇺🇸United States oknate Greater New York City Area

Live updates comments and jobs are added and updated live.
  • Novice

    It would make a good project for someone who is new to the Drupal contribution process. It's preferred over Newbie.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment about 1 year ago →
    🇬🇧United Kingdom FlusteredLondon

    Noob here: I tried to spin this up in DrupalPod with D11, but there are issues with Composer Dependencies. Can anyone assist?

    --------------------

    Problem 1
- Root composer.json requires drupal/core == 11.9999999.9999999.9999999-dev (exact version match), it is satisfiable by drupal/core[11.x-dev] from composer repo (https://repo.packagist.org) but drupal/core[dev-3220216-move-themespage-to, 10.2.x-dev] from path repo (repos/drupal/core) has higher repository priority. The packages from the higher priority repository do not match your constraint and are therefore not installable. That repository is canonical so the lower priority repo's packages are not installable. See https://getcomposer.org/repoprio for details and assistance.

Problem 2
- Root composer.json requires drupal/core-project-message == 11.9999999.9999999.9999999-dev (exact version match), it is satisfiable by drupal/core-project-message[11.x-dev] from composer repo (https://repo.packagist.org) but drupal/core-project-message[dev-3220216-move-themespage-to, 10.1.x-dev] from path repo (repos/drupal/composer/Plugin/ProjectMessage) has higher repository priority. The packages from the higher priority repository do not match your constraint and are therefore not installable. That repository is canonical so the lower priority repo's packages are not installable. See https://getcomposer.org/repoprio for details and assistance.

Problem 3
- Root composer.json requires drupal/core-recommended == 11.9999999.9999999.9999999-dev -> satisfiable by drupal/core-recommended[11.x-dev].
- drupal/core-recommended 11.x-dev requires drupal/core 9.3.x-dev -> satisfiable by drupal/core[9.3.x-dev] from composer repo (https://repo.packagist.org) but drupal/core[dev-3220216-move-themespage-to, 10.2.x-dev] from path repo (repos/drupal/core) has higher repository priority. The packages from the higher priority repository do not match your constraint and are therefore not installable. That repository is canonical so the lower priority repo's packages are not installable. See https://getcomposer.org/repoprio for details and assistance.

Problem 4
- Root composer.json requires drupal/core-dev == 11.9999999.9999999.9999999-dev -> satisfiable by drupal/core-dev[11.x-dev].
- drupal/core-dev 11.x-dev requires symfony/browser-kit ^4.4 -> found symfony/browser-kit[v4.4.0-BETA1, ..., 4.4.x-dev] but these were not loaded, likely because it conflicts with another require.
contrib.social Blog FAQ Discussions
Production build 0.71.5 2024