Publish date for our modern page (which is set as the homepage) does not equal the modified date

%3CLINGO-SUB%20id%3D%22lingo-sub-308757%22%20slang%3D%22en-US%22%3EPublish%20date%20for%20our%20modern%20page%20(which%20is%20set%20as%20the%20homepage)%20does%20not%20equal%20the%20modified%20date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-308757%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20classic%20team%20site%20collection%20(which%20is%20the%20root%20site%20collection)%2C%20and%20i%20have%20a%20modern%20page%20which%20is%20set%20as%20the%20home%20page%20of%20the%20site.%20now%20today%20as%20of%20%3CSTRONG%3E3%20January%20%40%2017%3A33%3C%2FSTRONG%3E%20i%20modified%20and%20publish%20the%20page%2C%20where%20the%20published%20date%20for%20the%20modern%20page%20was%2003%2F01%2F2019%20which%20is%20correct.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ebut%20later%20on%2C%20mainly%20on%20%3CSTRONG%3E04%2F01%2F2019%20%40%2000%3A15%3C%2FSTRONG%3E%20i%20access%20the%20page%2C%20but%20i%20have%20noted%20that%20the%20publish%20date%20for%20the%20modern%20page%20is%2004%2F01%2F2019%20as%20follow%2C%20although%20the%20latest%20publish%20date%20should%20be%2003%2F01%2F2019%3A-%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F64648i98AC448958421EDA%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%220401.png%22%20title%3D%220401.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eso%20i%20checked%20the%20%22site%20pages%22%20library%20and%20i%20can%20see%20that%20the%20modified%20date%20for%20the%20page%20is%2003%2F01%2F2019%20%40%2017%3A33%20which%20is%20correct%2C%20as%20follow%3A-%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F64649i8860AB2F52A23FDA%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%220301.png%22%20title%3D%220301.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eso%20my%20question%20is%20why%20the%20publish%20date%20for%20the%20modern%20home%20page%20does%20not%20equal%20the%20modified%20date%20(the%20correct%20date)%3F%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-308757%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309746%22%20slang%3D%22en-US%22%3ERe%3A%20Publish%20date%20for%20our%20modern%20page%20(which%20is%20set%20as%20the%20homepage)%20does%20not%20equal%20the%20modified%20date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309746%22%20slang%3D%22en-US%22%3EI%20assume%20because%20if%20you%20don't%20make%20any%20modifications%20but%20hit%20publish%20it%20will%20show%20the%20publish%20date%2C%20even%20thou%20you%20made%20the%20changes%20and%20%22saved%22%20them%20a%20day%20earlier.%20Publishing%20doesn't%20%22modify%22%20the%20document%20basically.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309638%22%20slang%3D%22en-US%22%3ERe%3A%20Publish%20date%20for%20our%20modern%20page%20(which%20is%20set%20as%20the%20homepage)%20does%20not%20equal%20the%20modified%20date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309638%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3EIt%E2%80%99s%20two%20different%20dates%20being%20called%20that.%20The%20one%20on%20the%20edit%20page%20is%20just%20basically%20last%20time%20it%E2%80%99s%20been%20checked%20in%20in%20an%20edit.%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20actual%20column%20published%20date%20is%20first%20time.%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%3C%2FP%3E%3CP%3Eok%20thanks%20for%20the%20reply.%20so%20this%20return%20me%20back%20to%20my%20original%20question%2C%20why%20the%20publish%20date%20on%20the%20page%20does%20not%20equal%20the%20modified%20date%20then%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309517%22%20slang%3D%22en-US%22%3ERe%3A%20Publish%20date%20for%20our%20modern%20page%20(which%20is%20set%20as%20the%20homepage)%20does%20not%20equal%20the%20modified%20date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309517%22%20slang%3D%22en-US%22%3EIt%E2%80%99s%20two%20different%20dates%20being%20called%20that.%20The%20one%20on%20the%20edit%20page%20is%20just%20basically%20last%20time%20it%E2%80%99s%20been%20checked%20in%20in%20an%20edit.%20%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20actual%20column%20published%20date%20is%20first%20time.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309515%22%20slang%3D%22en-US%22%3ERe%3A%20Publish%20date%20for%20our%20modern%20page%20(which%20is%20set%20as%20the%20homepage)%20does%20not%20equal%20the%20modified%20date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309515%22%20slang%3D%22en-US%22%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%26nbsp%3Bwrote%3A%3CBR%20%2F%3EPublished%20date%20is%20the%20first%20time%20it%E2%80%99s%20published.%20Modifications%20do%20not%20use%20this%20date%20field%20only%20modified%20column.%20It%E2%80%99s%20basically%20used%20for%20ordering%20of%20news%20articles%20on%20the%20news%20web%20part%20and%20if%20you%20update%20it%20will%20change%20the%20order%20of%20that.%20Otherwise%20each%20modification%20of%20a%20page%20would%20put%20it%20as%20new%20news%20each%20time.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%3C%2FP%3E%3CP%3Ethanks%20for%20your%20reply%2C%20but%20I%20do%20not%20think%20publish%20date%20represents%20the%20date%20when%20the%20page%20was%20first%20time%20published%2C%20as%20you%20can%20see%20from%20the%20picture%20the%20page%20version%20is%20219%20and%20it%20has%20been%20publish%20for%20the%20first%20time%20at-least%206%20monts%20ago..%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309507%22%20slang%3D%22en-US%22%3ERe%3A%20Publish%20date%20for%20our%20modern%20page%20(which%20is%20set%20as%20the%20homepage)%20does%20not%20equal%20the%20modified%20date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309507%22%20slang%3D%22en-US%22%3EPublished%20date%20is%20the%20first%20time%20it%E2%80%99s%20published.%20Modifications%20do%20not%20use%20this%20date%20field%20only%20modified%20column.%20It%E2%80%99s%20basically%20used%20for%20ordering%20of%20news%20articles%20on%20the%20news%20web%20part%20and%20if%20you%20update%20it%20will%20change%20the%20order%20of%20that.%20Otherwise%20each%20modification%20of%20a%20page%20would%20put%20it%20as%20new%20news%20each%20time.%20%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-481676%22%20slang%3D%22en-US%22%3ERe%3A%20Publish%20date%20for%20our%20modern%20page%20(which%20is%20set%20as%20the%20homepage)%20does%20not%20equal%20the%20modified%20date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481676%22%20slang%3D%22en-US%22%3EI%20dont%20think%20this%20is%20correct.%20when%20we%20publish%20(after%20making%20changes)%20the%20publish%20date%20is%20correct%20until%20you%20refresh%20the%20page%20and%20the%20date%20is%20changed%20to%20the%20next%20day.%20There%20is%20no%20world%20timezone%20that%20is%20one%20day%20ahead.%20this%20is%20a%20SP%20and%20MS%20bug%20-%20end%20of%20story%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-534398%22%20slang%3D%22en-US%22%3ERe%3A%20Publish%20date%20for%20our%20modern%20page%20(which%20is%20set%20as%20the%20homepage)%20does%20not%20equal%20the%20modified%20date%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-534398%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20seeing%20the%20same%20error%20(Danish%20settings)%20-%20If%20you%20select%20Page%20Details%2C%20then%20the%20incorrect%20date%20is%20shown%20very%20nicely%20(whereas%20the%20site%20contents%20page%20shows%20the%20correct%20date)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20seems%20to%20use%20a%20US%20time%20zone%20for%20calculation%2C%20which%20in%20our%20case%20give%20a%209%20hour%20difference%20(everything%20published%20after%203PM%20is%20referenced%20in%20the%20page%20as%20published%20the%20next%20day).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Super Contributor

I have a classic team site collection (which is the root site collection), and i have a modern page which is set as the home page of the site. now today as of 3 January @ 17:33 i modified and publish the page, where the published date for the modern page was 03/01/2019 which is correct.

 

but later on, mainly on 04/01/2019 @ 00:15 i access the page, but i have noted that the publish date for the modern page is 04/01/2019 as follow, although the latest publish date should be 03/01/2019:-

 

0401.png

 

so i checked the "site pages" library and i can see that the modified date for the page is 03/01/2019 @ 17:33 which is correct, as follow:-

 

0301.png

 

so my question is why the publish date for the modern home page does not equal the modified date (the correct date)??

7 Replies
Highlighted
Published date is the first time it’s published. Modifications do not use this date field only modified column. It’s basically used for ordering of news articles on the news web part and if you update it will change the order of that. Otherwise each modification of a page would put it as new news each time.


Highlighted



@Chris Webb wrote:
Published date is the first time it’s published. Modifications do not use this date field only modified column. It’s basically used for ordering of news articles on the news web part and if you update it will change the order of that. Otherwise each modification of a page would put it as new news each time.



@Chris Webb

thanks for your reply, but I do not think publish date represents the date when the page was first time published, as you can see from the picture the page version is 219 and it has been publish for the first time at-least 6 monts ago..

Highlighted
It’s two different dates being called that. The one on the edit page is just basically last time it’s been checked in in an edit.

The actual column published date is first time.
Highlighted

@Chris Webb wrote:
It’s two different dates being called that. The one on the edit page is just basically last time it’s been checked in in an edit.

The actual column published date is first time.

@Chris Webb

ok thanks for the reply. so this return me back to my original question, why the publish date on the page does not equal the modified date then?

Highlighted
I assume because if you don't make any modifications but hit publish it will show the publish date, even thou you made the changes and "saved" them a day earlier. Publishing doesn't "modify" the document basically.
Highlighted
I dont think this is correct. when we publish (after making changes) the publish date is correct until you refresh the page and the date is changed to the next day. There is no world timezone that is one day ahead. this is a SP and MS bug - end of story
Highlighted

We are seeing the same error (Danish settings) - If you select Page Details, then the incorrect date is shown very nicely (whereas the site contents page shows the correct date)

 

It seems to use a US time zone for calculation, which in our case give a 9 hour difference (everything published after 3PM is referenced in the page as published the next day).