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

[Backport] Remove timestap from current date when saving product special price from date #23152

Conversation

krishprakash
Copy link

Original Pull Request

#21966

Description (*)

Full timestamp is saved when creating a new product with a special price but without a special price from value.

With this fix, the time is reset so only the date will be saved. This is also in line with the UI where only a date can be selected.

Fixed Issues (if relevant)

  1. None I could find.

Manual testing scenarios (*)

  1. Set configuration on global scope general/locale/timezone > Europe/Amsterdam.
  2. Set configuration on en_US scope general/locale/timezone > America/New_York.
  3. Create new simple product with special price (leave special price from date empty).
  4. Product will be saved with a current timestamp using the Europe/Amsterdam timezone.
  5. Navigate to product on frontend (en_US store), no special price is shown. This is because special price from date is checked against the America/New_York timezone. This isn't the case for another five hours.

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds on Travis CI are green)

@m2-assistant
Copy link

m2-assistant bot commented Jun 6, 2019

Hi @krishprakash. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.2-develop instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

Copy link
Contributor

@orlangur orlangur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@krishprakash original commit author must be preserved

@ghost ghost assigned orlangur Jun 6, 2019
@krishprakash krishprakash force-pushed the 2.2-develop-PR-port-21966 branch from 457a2a3 to 6bb5167 Compare June 6, 2019 11:04
@magento-cicd2
Copy link
Contributor

CLA assistant check
Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.


Prakash Prajapati seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.

@krishprakash
Copy link
Author

@orlangur I have updated the PR as suggested by you.
Please have a look and update the PR.
Thank you.

@orlangur
Copy link
Contributor

orlangur commented Jun 7, 2019

@krishprakash please sign CLA.

@krishprakash
Copy link
Author

krishprakash commented Jun 10, 2019

@krishprakash please sign CLA.

@orlangur Signed the CLA.

@ghost
Copy link

ghost commented Jun 10, 2019

@krishprakash unfortunately, only members of the maintainers team are allowed to remove progress related labels to the pull request

@krishprakash
Copy link
Author

krishprakash commented Jun 13, 2019

@orlangur
Is there anything remaining from my end ?
If any please let me know.
Otherwise please update the status of PR.
Thanks.

@magento-engcom-team
Copy link
Contributor

Hi @orlangur, thank you for the review.
ENGCOM-5341 has been created to process this Pull Request
✳️ @orlangur, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

@orlangur orlangur added the Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests label Jun 22, 2019
@engcom-Alfa engcom-Alfa self-assigned this Jun 24, 2019
@engcom-Alfa
Copy link
Contributor

✔️ QA Passed

@sidolov sidolov added the Port label Jun 24, 2019
@magento-engcom-team magento-engcom-team merged commit 6bb5167 into magento:2.2-develop Jun 26, 2019
@m2-assistant
Copy link

m2-assistant bot commented Jun 26, 2019

Hi @krishprakash, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

magento-engcom-team pushed a commit that referenced this pull request Jun 26, 2019
@magento-engcom-team magento-engcom-team added this to the Release: 2.2.10 milestone Jun 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests Component: Catalog Partner: Krish TechnoLabs partners-contribution Pull Request is created by Magento Partner Progress: accept Release Line: 2.2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants