Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Reset date of draft after publishing
Just noticed that Textpattern uses the date of the first draft as the publishing date. Expected behavior in my opinion would be: Using the date when the status is changed to “live”. (But maybe I’m missing a good reason?)
“HaHa. Your medium is dying.” –Nelson Muntz, Springfield.
Offline
Re: Reset date of draft after publishing
I think that is the standard setting, probably because you can also set a future date to prepublish an article and that shouldn’t accidentally get reset to now.
As you probably know, you can put a checkmark by “reset time to now” to quickly achieve what you want, but you do have to remember to do that.
TXP Builders – finely-crafted code, design and txp
Offline
Re: Reset date of draft after publishing
jakob wrote #337450:
I think that is the standard setting, probably because you can also set a future date to prepublish an article and that shouldn’t accidentally get reset to now.
Makes sense.
As you probably know, you can put a checkmark by “reset time to now” to quickly achieve what you want, but you do have to remember to do that.
Yep. Not a big deal. Just not the behavior I’m used to from other CMS.
By the way: E-Mail notifications from the forum seem to be broken (for me) 🤔
“HaHa. Your medium is dying.” –Nelson Muntz, Springfield.
Offline
Re: Reset date of draft after publishing
dos wrote #337451:
By the way: E-Mail notifications from the forum seem to be broken (for me) 🤔
I’ll investigate – thanks for the report.
Offline
Re: Reset date of draft after publishing
dos wrote #337451:
By the way: E-Mail notifications from the forum seem to be broken (for me) 🤔
In the logs:
Jul 30 20:09:45 turtle postfix/pickup[53931]: 0288813B731: uid=33 from=<www-data>
Jul 30 20:09:45 turtle postfix/cleanup[54986]: 0288813B731: message-id=<20240730200945.0288813B731@turtle.textpattern.net>
Jul 30 20:09:45 turtle postfix/qmgr[12171]: 0288813B731: from=<www-data@turtle.textpattern.net>, size=1432, nrcpt=1 (queue active)
Jul 30 20:09:45 turtle postfix/smtp[54993]: warning: [YOURDOMAIN]: dane configured with dnssec lookups disabled
Jul 30 20:09:48 turtle postfix/smtp[54993]: 0288813B731: to=<YOU@YOURDOMAIN>, relay=mx02.mail.icloud.com[17.56.9.31]:25, delay=3.5, delays=0.01/0.02/0.56/2.9, dsn=5.7.0, status=bounced (host mx02.mail.icloud.com[17.56.9.31] said: 554 5.7.0 Blocked - see https://support.proofpoint.com/dnsbl-lookup.cgi?ip=159.65.240.144 (in reply to RCPT TO command))
Jul 30 20:09:48 turtle postfix/smtp[54993]: 0288813B731: lost connection with mx02.mail.icloud.com[17.56.9.31] while sending DATA command
Jul 30 20:09:48 turtle postfix/bounce[54994]: 0288813B731: sender non-delivery notification: 71AA613B76B
Jul 30 20:09:48 turtle postfix/qmgr[12171]: 0288813B731: removedWe’ve had this before regarding emails to iCloud, unfortunately. Proofpoint is often quite twitchy and blocks some senders.
I’ll start the unblocking process. I will post here when it’s underway, though you’re unlikely to get email notification since…you know…yeah.
Thanks for you patience, dos.
Offline