#known 2019-04-04

2019-04-04 UTC
#
[kenbauer] But that leads me to think that Diagnostics page doesn't check fully/completely what "version" I am on.
[tantek], [kenbauer], [Rose], [xavierroy], mapkyca, [kevinmarks], [jgmac1106], [grantcodes] and [davidmead] joined the channel
#
[davidmead] morning all - is there a way to change the ‘post date’ for something in Known?
[schmarty] and [jgmac1106] joined the channel
#
[jgmac1106] how I dream that was easy. i would manually start publishing old post
[kimberlyhirsh], [kenbauer], [eddie], [schmarty] and [davidmead] joined the channel
#
[davidmead] I guess it’ll be a difference between `created date` and `published date`, thinking back to WP implementations
#
[davidmead] I don’t know if Known has that difference
seekr joined the channel
#
mapkyca Known has a created and update timestamp, no explicit published timestamp, but that could be added by a plugin
[jgmac1106] and [kenbauer] joined the channel
#
[kenbauer] that is a nice idea for a plugin.
[Rose], [tantek], [jgmac1106] and [davidmead] joined the channel
#
[davidmead] So mapkyca, we could take Known’s `created` timestamp and make that editable as a plugin. You could then default it to the time you create, but timeshift it to change it’s place in your own timeline. The `update` timestamp should be left alone I feel.
#
[jgmac1106] please [davidmead] crank that out
#
[davidmead] i think that’s well beyond my technical expertise [jgmac1106]
[eddie], [kevinmarks] and [schmarty] joined the channel
#
mapkyca Most (all?) content types actually accept a "created" input variable, but that's generally left as default. Might just be a matter of adding a field to the input form.
[dougbeal], [fluffy], [tantek], [jgmac1106] and [kenbauer] joined the channel