magento / magento/community-features

Improves cms page options in the adminhtml configuration

Open
#18 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

moved from magento2 Priority: P3 Requires PO triage
Dominant language
No language data
Stars
46
Forks
14
PR merge metrics
No merged PRs in 30d

Description

This issue was originally raised in https://github.com/magento/magento2/pull/10426 by @hostep but unfortunately he cannot continue at the current time. The aim is to improve the admin usability for multiple store setups and the selection of cms pages in the store configuration.

Preconditions
  1. PHP 7.*
  2. Magento 2.*
Steps to reproduce
  1. Login to the Magento Admin with a multiple store setup,
  2. Create multiple CMS pages with the same name, e.g. a Home Page for each of your stores,
  3. Visit the configuration settings for "Default Pages",
  4. See multiple "Home Pages"
Expected result
  1. On the default store you will see only CMS pages attached to all store views and on a specific store you will see only CMS pages attached to that store.

end-results-aim

  1. Result should us UI component see https://github.com/okorshenko/magento2/pull/4/files for an example build.
Actual result
  1. Hard to read simple drop down.
cms-before

Original Report: https://github.com/magento/magento2/issues/11416 by @dmanners

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the Magento Admin configuration for "Default Pages" and review the original pull request 10426 and the linked example UI component. Confirm how CMS pages are selected for the default store versus a specific store view, then verify that duplicate page names are readable and limited to the applicable store scope.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.