magento / magento/architecture

Scope management for 'web/url/use_store' config value

Open
#514 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
278
Forks
146
PR merge metrics
No merged PRs in 30d

Description

Hi,

I wonder why Plugin/RouteParamsResolver getValue scope by store then that impossible to set store_view scope for field id="`use_store`" value ?

https://github.com/magento/magento2/blob/a947b306335294f61ab633ef75d9047c29988a9b/app/code/Magento/Backend/etc/adminhtml/system.xml#L511
``

https://github.com/magento/magento2/blob/a947b306335294f61ab633ef75d9047c29988a9b/app/code/Magento/Store/Url/Plugin/RouteParamsResolver.php#L77
```
$useStoreInUrl = $this->scopeConfig->getValue(
Store::XML_PATH_STORE_IN_URL,
--> StoreScopeInterface::SCOPE_STORE,
$storeCode
);
```
(since 2014 at https://github.com/magento/magento2/blob/9c2b633621e69bf2ea0480c1759c4d66739af29b/app/code/Magento/Core/Model/Url/RouteParamsResolver.php#L130 )

---
This is not a completely selfless request because I would need a website with the store_code in the URL and another website with no store_code in the URL. And this on the same Magento instance.

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 with app/code/Magento/Backend/etc/adminhtml/system.xml around the use_store field and app/code/Magento/Store/Url/Plugin/RouteParamsResolver.php around the scopeConfig lookup. Compare the configured scope with the requested website and store-view behavior, then determine the expected result for one website with store codes and another without them.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.