Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hidden custom Shipping Policy in Admin Store View scope #36425

Closed
1 of 5 tasks
angelo983 opened this issue Nov 6, 2022 · 13 comments
Closed
1 of 5 tasks

Hidden custom Shipping Policy in Admin Store View scope #36425

angelo983 opened this issue Nov 6, 2022 · 13 comments
Assignees
Labels
Area: Admin UI Component: Shipping Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: done Reported on 2.4.x Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch

Comments

@angelo983
Copy link
Member

angelo983 commented Nov 6, 2022

Preconditions and environment

  • Magento version 2.4-develop
  • PHP 8.1
  • Apply Shipping Policy.

Steps to reproduce

  1. Go to Stores => Settings => Configuration => Sales => Shipping Settings => Shipping Policy Parameters
  2. Set 'Apply custom Shipping Policy' to Yes
  3. Fill Shipping Policy field with text
  4. Switch in Store View scope in admin.

Expected result

Shipping Policy field visible in Store View scope

Actual result

Shipping Policy field is not visible in Store View scope

Additional information

1.Set 'Apply custom Shipping Policy' to No
2. Switch in Store View scope in admin.

Shipping Policy field visible in Store View scope

Screenshot 2022-11-10 at 4 57 02 PM

Release note

No response

Triage and priority

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
@m2-assistant
Copy link

m2-assistant bot commented Nov 6, 2022

Hi @angelo983. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

  • Summary of the issue
  • Information on your environment
  • Steps to reproduce
  • Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.


⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@m2-assistant
Copy link

m2-assistant bot commented Nov 7, 2022

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

  • 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

    DetailsIf the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

  • 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

  • 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

  • 4. Verify that the issue is reproducible on 2.4-develop branch

    Details- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
    - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
    - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

  • 5. Add label Issue: Confirmed once verification is complete.

  • 6. Make sure that automatic system confirms that report has been added to the backlog.

@engcom-Bravo engcom-Bravo added the Reported on 2.4.x Indicates original Magento version for the Issue report. label Nov 7, 2022
@engcom-Bravo
Copy link
Contributor

Hi @angelo983,

Thank you for reporting and collaboration.
Verified the issue on Magento 2.4-develop instance and the issue is not reproducible.Shipping Policy field visible in Store View scope.Kindly refer the screenshots.

Steps to reproduce :

1.Go to Stores => Settings => Configuration => Sales => Shipping Settings => Shipping Policy Parameters
2.Set 'Apply custom Shipping Policy' to Yes
3.Fill Shipping Policy field with text
4.Switch in Store View scope

Screenshot 2022-11-07 at 1 54 16 PM

Screenshot 2022-11-07 at 1 54 21 PM

Kindly recheck the issue on Magento 2.4-develop instance and check if any 3rd party extensions / modules enabled is causing this issue.

Thanks.

@engcom-Bravo engcom-Bravo added Issue: needs update Additional information is require, waiting for response Issue: Cannot Reproduce Cannot reproduce the issue on the latest `2.4-develop` branch labels Nov 7, 2022
@m2-community-project m2-community-project bot moved this from Ready for Confirmation to Needs Update in Issue Confirmation and Triage Board Nov 7, 2022
@angelo983
Copy link
Member Author

angelo983 commented Nov 7, 2022

@engcom-Bravo read better the steps and follow them to the letter, according also to the issue title.

Switch ADMIN setup in store view scope
image

Thanks.

@engcom-Bravo
Copy link
Contributor

@magento give me 2.4-develop instance

@magento-deployment-service
Copy link

Hi @engcom-Bravo. Thank you for your request. I'm working on Magento instance for you.

@magento-deployment-service
Copy link

@engcom-Bravo
Copy link
Contributor

Hi @angelo983,

Thanks for quick Update.

Store Views are mostly used to handle different languages on your website as per magento devdocs.We Cannot configure Shipping Policy.When we Configure Shipping Policy initially from Default store view it will not reflected in the Frontend.

Kindly let us know if you are still facing any issue.

Thanks.

@angelo983
Copy link
Member Author

Sorry but I cannot understand what you wrote. The issue is still present, example try to write a shipping policy for a specific language different from the default one.

@engcom-Bravo
Copy link
Contributor

Hi @angelo983,

Thank you for reporting and collaboration.
Verified the issue on Magento 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

Steps to Reproduce :

1.Go to Stores => Settings => Configuration => Sales => Shipping Settings => Shipping Policy Parameters
2.Set 'Apply custom Shipping Policy' to Yes.
3.Fill Shipping Policy field with text.
4.Switch in Store View scope in admin.

Shipping Policy field is not visible in Store View scope.

Screenshot 2022-11-10 at 1 03 15 PM

When 'Apply custom Shipping Policy' to No.
Switch in Store View scope in admin.

Shipping Policy field visible in Store View scope

Screenshot 2022-11-10 at 4 57 02 PM.

Hence confirming the issue.

Thanks.

@engcom-Bravo engcom-Bravo removed Issue: Cannot Reproduce Cannot reproduce the issue on the latest `2.4-develop` branch Issue: needs update Additional information is require, waiting for response labels Nov 10, 2022
@m2-community-project m2-community-project bot moved this from Needs Update to Ready for Confirmation in Issue Confirmation and Triage Board Nov 10, 2022
@engcom-Bravo engcom-Bravo added Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch and removed Issue: ready for confirmation labels Nov 10, 2022
@m2-community-project m2-community-project bot moved this from Pull Request In Progress to Dev In Progress in High Priority Backlog Nov 30, 2022
@m2-community-project m2-community-project bot moved this from Dev In Progress to Pull Request In Progress in High Priority Backlog Dec 7, 2022
@m2-community-project m2-community-project bot moved this from Pull Request In Progress to Dev In Progress in High Priority Backlog Feb 28, 2023
@github-jira-sync-bot github-jira-sync-bot added Progress: PR Created Indicates that Pull Request has been created to fix issue and removed Progress: dev in progress labels Mar 10, 2023
@engcom-Bravo
Copy link
Contributor

Hello,

As I can see this issue got fixed in the scope of the internal Jira ticket AC-7003 by the internal team
Related commits:https://github.com/search?q=repo%3Amagento%2Fmagento2+AC-7003&type=commits

Based on the Jira ticket, the target version is 2.4.7-beta1.

Thanks

@m2-community-project m2-community-project bot moved this from Dev In Progress to Done in High Priority Backlog May 15, 2023
@m2-community-project m2-community-project bot added Progress: done and removed Progress: PR Created Indicates that Pull Request has been created to fix issue Progress: PR in progress labels May 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Admin UI Component: Shipping Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: done Reported on 2.4.x Indicates original Magento version for the Issue report. Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch
Projects
Development

Successfully merging a pull request may close this issue.

4 participants