Skip to content

when saving a page in magento 2.2.1, 'Modified' date field is not getting updated #12625

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

Closed
mahmood537 opened this issue Dec 11, 2017 · 4 comments
Assignees
Labels
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

@mahmood537
Copy link

Preconditions

  1. Magento version 2.2.1

Steps to reproduce

  1. Login to magento admin
  2. Go to Content > Pages
  3. In Action column, click select > edit
  4. Make changes to that page and click 'Save Page'

Expected result

  1. The 'Modified' value for the edited page should be current timestamp

Actual result

  1. 'Modified' value for the edit page did not change. It's still the same as 'Created' value

This happens in Magento version 2.2.1
pages1
pages2

@magento-engcom-team magento-engcom-team added Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed labels Dec 11, 2017
@osrecio osrecio self-assigned this Dec 11, 2017
@magento-engcom-team
Copy link
Contributor

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

@magento-engcom-team magento-engcom-team added 2.2.x Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed 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 Dec 11, 2017
@osrecio
Copy link
Member

osrecio commented Dec 11, 2017

Working on it!
The same thing happens for static blocks. I will fix for both

magento-team pushed a commit that referenced this issue Dec 20, 2017
… Field for Block and Pages #12637

 - Merge Pull Request #12637 from osrecio/magento2:PR#12625_2.3
 - Merged commits:
   1. 5cce625
magento-team pushed a commit that referenced this issue Dec 20, 2017
@okorshenko okorshenko added the Fixed in 2.3.x The issue has been fixed in 2.3 release line label Dec 20, 2017
@okorshenko
Copy link
Contributor

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

The fix will be available with the upcoming patch release.

@okorshenko okorshenko added the Fixed in 2.2.x The issue has been fixed in 2.2 release line label Dec 22, 2017
magento-team pushed a commit that referenced this issue Dec 22, 2017
…k and Pages #12636

 - Merge Pull Request #12636 from osrecio/magento2:PR#12625_2.2
 - Merged commits:
   1. 22f454d
@stephansteiner
Copy link

Still is still an issue in Magento 2.2.3. This error can be reproduced on a blank installation of magento 2. Error occurs when saving cms pages and blocks, other entities
Steps to reproduce:

  • create new cms block
  • reopen newly created cms block, modify text/and or title and save again
  • modification date remains unchanged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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

5 participants