WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #44975, comment 33


Ignore:
Timestamp:
09/23/2019 03:38:24 PM (2 years ago)
Author:
adamsilverstein
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #44975, comment 33

    initial v1  
    1 [attachment:"44975.5.diff"] worked for null in my testing - sending a null value for date_gmt reset the date correctly. Screencast - https://cl.ly/e8bb21e13ac3 - note I did have to reload to show the correct date, this is like a gutenberg issue though and might already be resolved in the plugin/5.3.
     1[attachment:"44975.5.diff"] worked for `null` in my testing - sending a`null` value for `date_gmt` reset the date correctly. Screencast - https://cl.ly/e8bb21e13ac3 - note I did have to reload to show the correct date, this is like a gutenberg issue though and might already be resolved in the plugin/5.3.
    22
    3 Checking the database, i see the expected 0 values for the post - https://cl.ly/8968c001c517/MySQL_5.7.26_wpdev.localhostdevelopwordpresswp_posts_2019-09-23_08-13-24.jpg
     3Checking the database, i see the expected `0`values for the post - https://cl.ly/8968c001c517/MySQL_5.7.26_wpdev.localhostdevelopwordpresswp_posts_2019-09-23_08-13-24.jpg
    44
    5 One question: is the intention to also allow an empty string to reset or only null? when I tested with empty strings the save was rejected with the error "Updating failed. Error message: Invalid parameter(s): date_gmt" - https://cl.ly/7d968427a5ff
     5One question: is the intention to also allow an empty string to reset or only `null`? when I tested with empty string the save was rejected with the error "Updating failed. Error message: Invalid parameter(s): date_gmt" - https://cl.ly/7d968427a5ff