![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Opened 2 years ago
Last modified 10 months ago
#61084 new defect (bug)
getDate JS error when opening post
| Reported by: | nicknoordijk | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Awaiting Review |
| Component: | Editor | Version: | 6.5 |
| Severity: | major | Keywords: | close |
| Cc: | Focuses: | javascript |
Description
See error below which I was able to copy from the modal showing when opening the post - i've replaced my URL.
Seems to be a core thing? When I copy the text to a new page the issue is gone but it's happening every once in a while.
TypeError: Cannot read properties of undefined (reading 'getDate')
at ge (####/wp-includes/js/dist/editor.min.js?ver=6497dd814badef65e728:12:25478)
at Object.r [as isEditedPostBeingScheduled] (####/wp-includes/js/dist/data.min.js?ver=e6595ba1a7cd34429f66:2:16637)
at ####/wp-includes/js/dist/edit-post.min.js?ver=82b743695f8ef1673753:7:53893
at ####/wp-includes/js/dist/data.min.js?ver=e6595ba1a7cd34429f66:9:3293
at ####/wp-includes/js/dist/data.min.js?ver=e6595ba1a7cd34429f66:9:2061
at __unstableMarkListeningStores (####/wp-includes/js/dist/data.min.js?ver=e6595ba1a7cd34429f66:2:21866)
at Object.__unstableMarkListeningStores (####/wp-includes/js/dist/data.min.js?ver=e6595ba1a7cd34429f66:2:22124)
at p (####/wp-includes/js/dist/data.min.js?ver=e6595ba1a7cd34429f66:9:2026)
at ####/wp-includes/js/dist/data.min.js?ver=e6595ba1a7cd34429f66:9:2628
at Qe (####/wp-includes/js/dist/data.min.js?ver=e6595ba1a7cd34429f66:9:2840)
Note:
See TracTickets
for help on using tickets.
This seems to be some Gutenberg trouble.
If this is still happening, please open a ticket in the Gutenberg repository and provide more info there
Ideally you should be trying to set up an environment to test it consistently. Those "happens once in a while" are not any good for helping solve a problem. If you cannot reproduce this consistently it will never be resolved.
Also this should be tested in a clean environment. For example use the WordPress Playground, and if you can reproduce it there, then you can write up the steps and send a report. Only in that case a solution might arrive soon.
If you happen to open the ticket in Gutenberg, send the link to the ticket here, please
I setting this as
closefor potentialreported-upstream.