Join our Folding@Home team:
Main F@H site
Our team page
Covers transactions:
2020-01-01 00:00:00 ..
2020-06-30 21:00:33 UTC
(SPIDs: [1207..1407])
Last Update:
2020-07-01 02:02:58 UTC
--martyb
Support us: Subscribe Here
and buy SoylentNews Swag
We always have a place for talented people, visit the Get Involved section on the wiki to see how you can make SoylentNews better.
Covers transactions:
2020-01-01 00:00:00 ..
2020-01-31 06:46:05 UTC
(SPIDs: [1207..1216])
Last Update:
2020-01-31 12:48:47 UTC
--martyb
So the Dev Team has been hard at work fixing up issues with with the 17_02 release. We compiled all of your comments from the 17_02 Meta stories into a large bug and feature request list. We have been working on getting these issues fixed as soon as we can.
You may have noticed some changes over the last week that went out to fix some issues, and we just released some more fixes today.
Here is a list of the major fixes since the last story:
Continuation of:
Site Update 17_2
Comments Redux
Site Update: The Next Episode
Site Update - Taking a Breather
Outstanding Issues
So if you see any new bugs that you think are related to these changes, or just want to let us know about an ongoing issue, please feel free to comment below.
Here are the currently known bugs that we are working on:
And here are the feature requests:
At the moment, no matter what Breakthrough/Threshold setting I choose, every Top Level Comment (TLC) is displayed fully expanded.
Consider what the "Deuteronomy child bride", "Penis Bird", and "Cheap Canadian V14gra" users would make of knowing that they can make sure that their TLC will always appear in full.
For the following "T:" denotes setting for Threshold and "B:" denotes a setting for Breakthrough.
Am I missing something or shouldn't: (T:-1, B:5) produce the same result as: (T:5, B:-1)
Under Threaded-TOS, I'm seeing different results on: https://dev.soylentnews.org/article.pl?sid=17/02/16/0222248 where the highest score for a comment is: 2.
T:-1, B:5 -- https://dev.soylentnews.org/article.pl?sid=17/02/16/0222248&threshold=-1&highlightthresh=5&commentsort=0&mode=threadtos&page=1&noupdate=1#commentwrap
T:5, B:-1 -- https://dev.soylentnews.org/article.pl?sid=17/02/16/0222248&threshold=5&highlightthresh=-1&commentsort=0&mode=threadtos&page=1&noupdate=1#commentwrap
Based on what I understand, T:-1, B:5 Says show me everything (scoring -1 or better) in full (oh, and boost visibility of those scoring 5 or better) -- but we are already selecting to show everything anyway
OTOH, T:5, B:-1 Says show me only those scoring 5 or better (there are none for that story), but boost all those scoring -1 or better, which is ALL of the comments, so it again selects to display everything.
It would be helpful for the user to have a label to explain what the seemingly barren "(1)" that appears in two places on a story actually means. Granted, on stories with enough comments, and that actually spills over onto additional pages, there is a bit more of an indication, but it could be made explicitly clear by adding just two lines to one template.
Extended copy has the updated version of the template. The two lines which contain only "Page:" are all it takes.
[% IF !((total < user.commentlimit) || (user.commentlimit < 1)) && (legacy == "yes") %]
[% pages = total / user.commentlimit %]
<div class="linkCommentPage">
Page:
[% FOREACH p = [1 .. pages] %]
[% start = user.commentlimit * p %]
[% IF p != 0 %] | [% END %]
[% IF start == form.startat || (!form.startat && p == 0) %]
<b>([% p %])</b>
[% ELSE %]
[% Slash.linkComment({
sid => sid,
pid => pid,
cid => cid,
threshold => threshold,
highlightthresh = highlightthresh,
subject => p,
subject_only => 1,
startat => (start ? start : 0),
}) %]
[% END %]
[% END %]
[% IF user.breaking %]
([% constants.sitename %] Overload: CommentLimit [% user.commentlimit %])
[% END %]
</div>
[% ELSIF (legacy == "no") %]
<div class="linkCommentPage">
Page:
[% form.page = (form.page || 1) %]
[% FOREACH p = [1 .. tpages] %]
[% IF p != form.page %]
[% Slash.linkComment({
sid => sid,
pid => pid,
cid => cid,
threshold => threshold,
highlightthresh = highlightthresh,
subject => (p),
subject_only => 1,
page => (p),
}) %]
[% ELSE %]
<b>([% p %])</b>
[% END %]
[% END %]
</div>
[% END %]
This story is for you. Feel free to play around with the new features, post comments, and moderate to your heart's content. If you find anything amiss or wish to discuss a feature or provide feedback, please comment here and/or leave a comment on the #dev channel on IRC.
20170215e - Test Story - Please DO NOT Moderate and DO NOT Post Comments - Comment Score Testing
The comment structure AND the comment scores have been carefully crafted - please do not touch. --martyb
There is one top-level comment (TLC); it has score: -1
That TLC has 4 children, respectively scored: -1, 0, 1, and 2.
EACH of those children has 4 children, respectively scored: -1, 0, 1, and 2.
-1 -1 -1
0
1
2
0 -1
0
1
2
1 -1
0
1
2
2 -1
0
1
2
Have a few issues with the new "[Continues...]" item which is automatically added to stories that have a non-empty "Extended Copy" section.
1) When editing a story, the "[Continues...]" text does not appear when I click on the "Preview" button.
2) Accidentally discovered it is implemented as a link, not just plain text, when I somehow clicked on it on the main page and saw the extended copy text suddenly appear... this is confusing. It looks exactly like the text we editors previously inserted into stories manually, but has a different effect -- need to visually distinguish it from the old-style, text-only version (e.g. one couldunderline the link but see next item).
3) Once I click on the "[Continues...]" link on the main page and see the expanded text, I see no way to re-collapse it. :(
4) May I suggest reusing the "Expand/Collapse comment" single-chevron that is employed in the new threaded comment code?
5) For completeness' sake, the prior 4 items were in the "Intro Copy" text box, and this item is at the top of the "Extended Copy" text box.