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

Product Custom Option Value is cut off in /admin/sales/order/view/ #4680

Closed
wq9 opened this issue May 24, 2016 · 10 comments
Closed

Product Custom Option Value is cut off in /admin/sales/order/view/ #4680

wq9 opened this issue May 24, 2016 · 10 comments
Labels
bug report Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release 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 triage wanted

Comments

@wq9
Copy link

wq9 commented May 24, 2016

Steps to reproduce

  1. Create a product with Custom Option, Input Type = Field
  2. Enter a string longer than 55 characters, for example https://media.example.com/2c013ce0c4c207e8cf648d55f054bdd3.jpg
  3. Order the item.
  4. View the order in the admin interface

Expected result

In the Items Ordered section, the custom option value should display in full, or at least display in full when you hover on the value.

Actual result

In the Items Ordered section, the custom option value is cut off to 55 characters and does not show the full value.

https://github.com/magento/magento2/blob/develop/app/code/Magento/Sales/view/adminhtml/templates/items/column/name.phtml

@vil11
Copy link

vil11 commented May 30, 2016

Looks like a reproducible bug. Internal ticket MAGETWO-53668.

☀️ dvilchynskyi, M2 QA engineer.

@NadiyaS NadiyaS added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development CS bug report labels Jun 2, 2016
@NadiyaS NadiyaS self-assigned this Jun 2, 2016
@vkorotun vkorotun removed the CS label Aug 4, 2016
@NadiyaS NadiyaS removed their assignment Mar 22, 2017
@galahadl
Copy link

galahadl commented Jun 6, 2017

Any progress on this? We have a client currently experiencing major fulfilment issues due to this

@magento-engcom-team magento-engcom-team added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development bug report Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed labels Sep 11, 2017
@magento-engcom-team magento-engcom-team added 2.1.x Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release 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 labels Oct 11, 2017
@magento-engcom-team
Copy link
Contributor

@wq9, thank you for your report.
We've created internal ticket(s) MAGETWO-53668 to track progress on the issue.

@magento-engcom-team
Copy link
Contributor

@wq9, thank you for your report.

Unfortunately, we are archiving this ticket now as it did not get much attention from both Magento Community and Core developers for an extended period. This is done in an effort to create a quality, community-driven backlog which will allow us to allocate the required attention more easily.

You may learn more about this initiative following this link.

Please feel free to comment or reopen the ticket if you think it should be reviewed once more. Thank you for collaboration.

@shibey
Copy link

shibey commented May 10, 2018

So is magento not fixing this one? we have been waiting for a fix on this one.

@korostii
Copy link
Contributor

Apparently not.
I wonder if they could clarify their criteria for "much attention" though
IMO right now the dialogue I'm seeing in these "triaged" issues looks a bit comical if not absurd:

Users: Here's a bug in your software, please fix it.
Magento: Oh yeah, it's a bug, I've reproduced it.

------< one year later >-------

Users: Any progress on this?

------< one year later >-------

Magento: Hmm, it doesn't seem like you really want us to fix this bug. 
         We will just close this ticket now. 
         Thank you for collaboration.

@tonyr101
Copy link

I'm also affected by this BUG but I am using "textarea" not "field" - the fact is that customers are entering text into a textarea when ordering a product and although all their text is recorded in the DB it's cut off in the admin and emails so it's useless...

PLEASE FIX THIS

@adamstapley
Copy link

Did anybody ever find a fix for this or work around? We have a site that personalises gifts and can't see what text people want on items if they enter more than 50 characters.

@akssaiyad
Copy link

akssaiyad commented Feb 27, 2019

I have solved it

In the Items Ordered section, the custom option value is cut off to 55 characters and does not show the full value.

https://github.com/magento/magento2/blob/develop/app/code/Magento/Sales/view/adminhtml/templates/items/column/name.phtml

You have to need comment below code in line no. 34

<?php //$_option = $block->getFormattedOption($_option['value']); ?>

After All content display in admin also

@adamstapley
Copy link

Thanks, seemed to work for me on Magento 2.3. It was line 33 in my file.

magento-cicd2 pushed a commit that referenced this issue Jan 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Reproduced on 2.1.x The issue has been reproduced on latest 2.1 release 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 triage wanted
Projects
None yet
Development

No branches or pull requests