Magento 2.2.6 Terms and Conditions are Not visible in Admin

[Ctucker9233]

Preconditions (*)

Magento 2.2.6 fresh install

Steps to reproduce (*)

1. Go to admin
2. Go to Store -> Terms and Conditions.
3. Add a New Condition
4. Save Condition

Expected result (*)

1. New Condition should show up in the list of terms and conditions.

Actual result (*)

1. No conditions, old or new, show up on the list.

[magento-engcom-team]

Hi @Ctucker9233. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

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

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me $VERSION instance

where $VERSION is version tags (starting from 2.2.0+) or develop branches (for example: 2.3-develop).
For more details, please, review the Magento Contributor Assistant documentation.

@Ctucker9233 do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[Ctucker9233]

@magento-engcom-team give me 2.2.6 instance

[magento-engcom-team]

Hi @Ctucker9233. Thank you for your request. I'm working on Magento 2.2.6 instance for you

[magento-engcom-team]

Hi @Ctucker9233, here is your Magento instance.
Admin access: http://ec2-34-228-235-121.compute-1.amazonaws.com/i-18954-2-2-6//admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[magento-engcom-team]

Hi @Alex-Lunkov. 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).

  Details

  If 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.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

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

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

[oleksii-lunkov]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @Alex-Lunkov. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @Alex-Lunkov, here is your Magento instance.
Admin access: http://ec2-34-228-235-121.compute-1.amazonaws.com/i-18954-2-3-develop//admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[oleksii-lunkov]

@magento-engcom-team give me 2.2-develop instance

[magento-engcom-team]

Hi @Alex-Lunkov. Thank you for your request. I'm working on Magento 2.2-develop instance for you

[magento-engcom-team]

Hi @Alex-Lunkov, here is your Magento instance.
Admin access: http://ec2-34-228-235-121.compute-1.amazonaws.com/i-18954-2-2-develop//admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[oleksii-lunkov]

The issue can't be reproduced on 2.3-develop and on 2.2-develop. Closing this issue.

[ghost]

working fine at my end also.

[ghost]

I was able to reproduce this issue. Issue comes when the prefix is added in table name. Reopening the issue.

[magento-engcom-team]

Hi @ayazwebkul. 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).

  Details

  If 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.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.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. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

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

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

[ghost]

#squashtoberfest

[magento-engcom-team]

@ayazwebkul Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-96023 were created

[gwharton]

This is a duplicate of #18357 and has already had both 2.2 and 2.3 PR's produced.

Here is the 2.3 PR #18412

Here is the 2.2 PR #18866

The 2.2 change has yet to be merged.

[magento-engcom-team]

Hi @Ctucker9233. Thank you for your report.
The issue has been fixed in #18866 by @gelanivishal in 2.2-develop branch
Related commit(s):

• 2a6f8340de5fd6fd96c4d0848ba84e9e64cc1cf0

The fix will be available with the upcoming 2.2.9 release.