#dev | Logs for 2017-12-21

« return
[15:10:59] SoyGuest50158 is now known as cosurgi
[15:11:02] -!- cosurgi has quit [Changing host]
[15:11:02] -!- cosurgi [cosurgi!~cosurgi@Soylent/Staff/Misc/cosurgi] has joined #dev
[17:28:29] -!- exec has quit [Ping timeout: 246 seconds]
[22:43:26] <Bytram> I'm responding to this comment on the Meta: site update story: https://soylentnews.org
[22:43:27] <upstart> ^ 03SoylentNews Comments | Meta: A Quick December Update ( https://soylentnews.org )
[22:44:08] <Bytram> ISTM that we need only change the "50" to "46" in template: edit_comment;comments;default as follows:
[22:44:11] <Bytram> change:
[22:44:22] <Bytram> <input type="text" name="postersubj" value="[% form.postersubj | strip_subject %]" size="50" maxlength="50">
[22:44:24] <Bytram> to be:
[22:44:33] <Bytram> <input type="text" name="postersubj" value="[% form.postersubj | strip_subject %]" size="46" maxlength="46">
[22:45:08] <Bytram> Then, when a user replies to a comment, the prepending of "Re: " to the parent comment will still fit in the 50-char field.
[22:45:28] <Bytram> have implemented this directly using the template editor on Dev.
[22:46:13] <Bytram> just hit "Save" for the changes on Dev. I think I need to bounce something for it to take effect.
[22:52:49] <Bytram> just ssh'ed to dev (lithium) and bounced the server using: /home/bob/bin/bounce
[23:06:02] <Bytram> hmmm....
[23:06:29] <Bytram> might another template need nudging to handle Top-Level Comments to: (1) Journals and/or (2) Polls ??
[23:38:26] <Bytram> made a quick journal entry, submitted a Top-Level Comment (TLC) and a reply to the TLC. TLC subject was restricted to 46 chars, had full 50 chars available for the subject of the reply to the TLC.
[23:39:11] <Bytram> Did same wrt Poll; created a new poll, submitted a TLC and a reply to the TLC... saw Subject field length restrictions of 46 and 50 chars, respectively.
[23:39:17] <Bytram> break time