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

Meta Keywords/Meta Description are input field in product form while they are defined as textarea #20555

Closed
amitvishvakarma opened this issue Jan 24, 2019 · 7 comments
Assignees
Labels
Component: Catalog Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@amitvishvakarma
Copy link
Contributor

Preconditions

In Magento 2.2.x and Magento 2.3.x, the Meta Keywords, Meta Description are of Textarea defined in product attributes, but they are showing input [type = text ] in product form.

Steps to reproduce

  1. Go to Store->Attributes->Product.
  2. Search for Meta Keywords/Meta description.
  3. View them, you will able to see their 'Catalog Input Type for Store Owner' is Textarea.
  4. Now go to Catalog->Product
  5. Click on 'Add Product button' Or Edit Product.
  6. Go to Search engine optimization tab.
  7. You will see Meta Keywords/Meta description are showing text field instead of textarea.

Expected result

They must show <textarea>

Actual result

They are showing of input [type="text"]

Images
meta_description
meta_keywords
meta frontend input in database
input field in product form

@magento-engcom-team
Copy link
Contributor

Hi @amitcedcoss. 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.

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

  • yes
  • no

Sorry, something went wrong.

@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Jan 24, 2019
@jitendra-cedcoss jitendra-cedcoss self-assigned this Jan 24, 2019
@magento-engcom-team
Copy link
Contributor

magento-engcom-team commented Jan 24, 2019

Hi @jitendra-cedcoss. 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.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.

Sorry, something went wrong.

@jitendra-cedcoss jitendra-cedcoss added Component: Catalog Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed labels Jan 24, 2019
@magento-engcom-team magento-engcom-team added the Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development label Jan 24, 2019
@magento-engcom-team
Copy link
Contributor

@jitendra-cedcoss Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-97903, MAGETWO-97904 were created

@amol2jcommerce
Copy link
Contributor

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

@magento-engcom-team
Copy link
Contributor

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

@magento-engcom-team
Copy link
Contributor

Hi @amitcedcoss. Thank you for your report.
The issue has been fixed in #20556 by @amitcedcoss in 2.3-develop branch
Related commit(s):

The fix will be available with the upcoming release.

magento-engcom-team added a commit that referenced this issue Feb 13, 2019
…put field in product form while they are defined as textarea #20556

 - Merge Pull Request #20556 from amitcedcoss/magento2:2.3developpr1
 - Merged commits:
   1. a5dfa0d
magento-engcom-team pushed a commit that referenced this issue Feb 13, 2019

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
…put field in product form while they are defined as textarea #20556
@magento-engcom-team
Copy link
Contributor

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

The fix will be available with the upcoming 2.2.9 release.

@magento-engcom-team magento-engcom-team added the Fixed in 2.2.x The issue has been fixed in 2.2 release line label Feb 14, 2019
magento-engcom-team added a commit that referenced this issue Feb 14, 2019
…tion are input field in product form while they are defined as textarea #21199

 - Merge Pull Request #21199 from amol2jcommerce/magento2:2.2-develop-PR-port-20556
 - Merged commits:
   1. b86a394
magento-engcom-team pushed a commit that referenced this issue Feb 14, 2019
…tion are input field in product form while they are defined as textarea #21199
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Catalog Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.2.x The issue has been reproduced on latest 2.2 release Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

No branches or pull requests

4 participants