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

Error when uploading a Transactional Emails logo #20091

Closed
chaplynsky opened this issue Jan 6, 2019 · 11 comments
Closed

Error when uploading a Transactional Emails logo #20091

chaplynsky opened this issue Jan 6, 2019 · 11 comments
Labels
Component: Email Fixed in 2.3.x The issue has been fixed in 2.3 release line 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 Progress: accept Progress: PR Created Indicates that Pull Request has been created to fix issue Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release

Comments

@chaplynsky
Copy link
Contributor

Preconditions (*)

  1. Magento 2.3
  2. PHP 7.1

Steps to reproduce (*)

  1. Go to Content>Configuration>edit theme>Transactional Emails
  2. Upload logo

Expected result (*)

  1. Logo gets uploaded and is visible

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."

@magento-engcom-team
Copy link
Contributor

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

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

  • yes
  • no

@magento-engcom-team magento-engcom-team added the Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed label Jan 6, 2019
@chaplynsky
Copy link
Contributor Author

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

@magento-engcom-team
Copy link
Contributor

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

@shikhamis11 shikhamis11 self-assigned this Jan 6, 2019
@magento-engcom-team
Copy link
Contributor

magento-engcom-team commented Jan 6, 2019

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

@shikhamis11
Copy link
Member

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

@magento-engcom-team
Copy link
Contributor

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

@cotiga
Copy link

cotiga commented Jan 6, 2019

A technical problem with the server created an error. Try again to continue what you were doing. If the problem persists, try again later.
IN CONSOL
JQMIGRATE: deferred.pipe() is deprecated

#19681 #19474 #19883 #19687 #19615 #19474...

Always the same problem

I have an new clean install with
Magento 2.3 (composer instal)
ON
Ubuntu 18.04
PHP 7.2
MySQL 5.7
Nginx

I think it's time to really focus on this problem, thanks

@chaplynsky
Copy link
Contributor Author

chaplynsky commented Jan 6, 2019

@cotiga yeah, this seems to be an issue that keeps coming back anywhere a logo is being uploaded. You can take a look at my fix for the Transactional Emails logo upload. After you apply and run upgrade, compile, static deploy, reindex, cache clean - you'll be able to upload the logo.

And here is the fix for the header logo upload .

@davidverholen davidverholen added Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release Progress: PR Created Indicates that Pull Request has been created to fix issue Component: Email Progress: accept labels Jan 6, 2019
@shikhamis11 shikhamis11 added the Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed label Jan 7, 2019
@magento-engcom-team
Copy link
Contributor

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

@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 7, 2019
@shikhamis11 shikhamis11 removed their assignment Jan 7, 2019
@ghost ghost self-assigned this Jan 24, 2019
@magento-engcom-team
Copy link
Contributor

Hi @engcom-backlog-nazar. Thank you for working on this issue.
Looks like this issue is already verified and confirmed. But if your want to validate it one more time, please, go though the following instruction:

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

  • 2. 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!

  • 3. 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

  • 4. If the issue is not relevant or is not reproducible any more, feel free to close it.

@magento-engcom-team
Copy link
Contributor

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

The fix will be available with the upcoming release.

@magento-engcom-team magento-engcom-team added the Fixed in 2.3.x The issue has been fixed in 2.3 release line label Feb 13, 2019
magento-engcom-team added a commit that referenced this issue Feb 13, 2019
#20092

 - Merge Pull Request #20092 from chaplynsky/magento2:patch-1
 - Merged commits:
   1. ba32513
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Email Fixed in 2.3.x The issue has been fixed in 2.3 release line 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 Progress: accept Progress: PR Created Indicates that Pull Request has been created to fix issue Reproduced on 2.3.x The issue has been reproduced on latest 2.3 release
Projects
None yet
Development

No branches or pull requests

5 participants