-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Error when uploading a Transactional Emails logo #20091
Comments
Hi @chaplynsky. Thank you for your report.
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:
where @chaplynsky do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?
|
@magento-engcom-team give me 2.3-develop instance |
Hi @chaplynsky. Thank you for your request. I'm working on Magento 2.3-develop instance for you |
Hi @shikhamis11. Thank you for working on this issue.
|
@magento-engcom-team give me 2.3-develop instance |
Hi @shikhamis11. Thank you for your request. I'm working on Magento 2.3-develop instance for you |
A technical problem with the server created an error. Try again to continue what you were doing. If the problem persists, try again later. #19681 #19474 #19883 #19687 #19615 #19474... Always the same problem I have an new clean install with I think it's time to really focus on this problem, thanks |
@shikhamis11 Thank you for verifying the issue. Based on the provided information internal tickets |
Hi @engcom-backlog-nazar. Thank you for working on this issue.
|
Hi @chaplynsky. Thank you for your report. The fix will be available with the upcoming release. |
Preconditions (*)
Steps to reproduce (*)
Expected result (*)
Actual result (*)
Logo is NOT uploaded and the following error is displayed:
"A technical problem with the server created an error. Try again to continue what you were doing. If the problem persists, try again later."
The text was updated successfully, but these errors were encountered: