Owdy Posted January 3 Posted January 3 I publish article at 6.00 am. Later I found a typo, and change one letter in 5pm. After that, article says its published at 5pm. Why I can't choose orginal publish time? Article is published at 6am, not 5pm.
Marc Posted January 4 Posted January 4 I should say its edited at that time, not published. Unless of course it wasnt visible before you made the edit?
Owdy Posted January 4 Author Posted January 4 (edited) That field name is Published, not Edited. IMO this is a bug, but you say its a feature. Edited January 4 by Owdy Ibai 1
Marc Posted January 4 Posted January 4 2 hours ago, Owdy said: That field name is Published, not Edited. IMO this is a bug, but you say its a feature. Im not sure I get your point there. I'm saying that published field shouldn't be edited. Only the edited data should be. I was asking if it was previously visible to people, or hadnt yet been published?
Owdy Posted January 4 Author Posted January 4 (edited) It was visible. It was scheculed to open in morning. That field changes in every edit. Edited January 4 by Owdy
Marc Posted January 4 Posted January 4 I will add that as a bug, rather than feedback. Indeed you cant put a past date in, but if its one where its already been published and you edit it afterward, it really shouldnt then be changing that date
Owdy Posted January 4 Author Posted January 4 2 minutes ago, Marc Stridgen said: I will add that as a bug, rather than feedback. Indeed you cant put a past date in, but if its one where its already been published and you edit it afterward, it really shouldnt then be changing that date Yeah, mee too. https://invisioncommunity.com/forums/topic/476685-database-article-date-issue/#comment-2961349
Solution Marc Posted January 4 Solution Posted January 4 Yeah Ive seen it there. I think there were wires crossed there. 🙂 Its been added as a bug Owdy and SeNioR- 1 1
Kirill Gromov Posted January 15 Posted January 15 (edited) @Marc Stridgen, will this bug be fixed in the next release? Edited January 15 by Kirill Gromov
Jim M Posted January 15 Posted January 15 1 hour ago, Kirill Gromov said: @Marc Stridgen, will this bug be fixed in the next release? This is still an open issue. I'm afraid, we cannot provide an ETA of the resolution to this at this time.
Recommended Posts