SoylentNews is people
SoylentNews is powered by your submissions, so send in your scoop. Only 17 submissions in the queue.
SoylentNews
posted by
paulej72
on Sunday March 19 2017, @12:15PM
from the kill-one-bug-find-another-must-be-cockroaches dept.
from the kill-one-bug-find-another-must-be-cockroaches dept.
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:
- Comment titles now act to trigger actions as well as the buttons.
- New icons for the buttons that are bigger and spaced out a bit more.
- Removed extra spacing for some of the modes when buttons are hidden. (Still needs some more work, but much better than before.)
- Changed how we set states for hidden threads so that the individual comments are not set hidden as well. This will lessen the number of clicks needed to open a comment in this case.
- Flat comment mode will now show a comment's children when look at comment (cid is set).
- Temp fix for Content Security Policy eating CSS when not on https://soylentnews.org.
- Domain Tags now show in comments.
- Fixed broken messages when looking at them from messages.pl.
- Fixed for @user: shortcut links that would eat a character after the ":".
And here are the latest updates:
- Editor fixes: added new lines to story editor and fixed topic tree popup issue.
- Fix for black on black text boxes in Grayscale theme
- Added SVG icons for buttons and CSS fixes to enhance look.
- Mod Points now back to UTC 00:10.
- Add # of children to collapsed thread title.
- Fix comment details to bring in the correct data which broke email and journal links.
- Add time to collapsed comment title.
- Fix select all button in messages.pl.
- Redirect returns to correct article.pl page after moderating.
- Updated CSP to fix issues. We still need to search for some inline JS that may need to be purged or rewritten to work correctly.
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:
- FIXED: When viewing the list of messages you have received, the "Select All" checkbox has stopped working because we removed Javascript.
- There are still features of the old "Nested" display mode that are not reproduced in the new "Threaded-TOS" / "Threaded-TNG" display modes.
- TESTING ON DEV: Issues with Expand/Collapse comment tree versus Hide/Show comment tree. New expand all in tree button.
- MOSTLY FIXED: We are aware of issues with our (stricter) Comment Security Policy (CSP) support; especially accessing the site from TOR/Onion and from the deprecated https://www.soylentnews.org/ URL — one should use: https://soylentnews.org/ instead, but we are still trying to handle that automatically.
- Pagination and Redirects; there are known issues with implementation of the "&page=" parameter in the URL, especially when "&cid=" is also specified. For example, I have my page size set to 20 comments, someone else has the default of 100 comments, and I refer to a comment on my page 4, which is still on page 1 for the other person.
- In URLs, we currently use "&noupdate=" to toggle when the "*NEW*" flag and comment dimming take effect. has knock-on side effects that were not anticipated. Are planning to change to the reverse sense: "&update=", instead.
- Lost functionality during upgrade: Sort order by comment score.
- FIXED: User Journal link missing in details bar
- Pick sane default for AC mode and for Threshold/Breakthrough
- Some people are still having issues with previously-seen comments' dimming. Not so much that they are dimmed, but in how they are dimmed. Maybe dim the only the title? Maybe change the color?
- Spoiler tag needs to be triggered by text.
- Buttons on phones might still be too small since mobile browsers like to resize the text larger making everything else too small
- SOMEWHAT FIXED: Bug chrome/android phone when previewing comment messes up text size in edit box -- actually, slashboxes on RHS disappear after submitting comment or performing comment moderation. Resulting display area is much wider, so displayed font size is reduced by approximately 40%.
- FIXED: Possibly add date and time to collapsed comment title.
And here are the feature requests:
- Create moderation feedback as a modal dialog box via CSS (med term project).
- <code> tag support and styling.
- Edit after post (with limits).
- Markdown support for comments. (long term project)
- Button to reset all comments to unread (should be a quickie).
- New tags should not display for the first time a story is shown (may be a complicated issue to resolve).
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
There are three things I always forget. Names, faces -- the third I
can't remember.
-- Italo Svevo
(Score: 0) by Anonymous Coward on Tuesday March 14 2017, @09:27PM (8 children)
Someone seems to have moved UTC back by 5 hours, at least as far as mod point distribution time is concerned. Anyone else seeing this?
(Score: 2) by paulej72 on Tuesday March 14 2017, @11:56PM (7 children)
When we upgraded to 16_02 last year, the mod points were handed out at 00:10 UTC, but I felt this should have been closer to midnight EST. So one of the first changes I added was to make this mod points be handed out at 05:10. This was merged to master in March of 16. One of the first merges for what is now 17_02. Little did I expect that this would be a one year in the making change.
So now the new norm is 0510, and everyone should become used to it at some point.
Team Leader for SN Development
(Score: 3, Informative) by paulej72 on Wednesday March 15 2017, @12:28AM (6 children)
Well after discussing this with martyb we decided to change it back for now to UTC 00:10. After we get some of the other issues worked out we discuss it with everyone and see if we should change it.
Team Leader for SN Development
(Score: 3, Funny) by aristarchus on Wednesday March 15 2017, @04:24AM (3 children)
Noticed. For some reason, as much as I respect and admire the dev team here at SoylentNews, even including the Might Fuzz, I am not quite comfortable with you all messing with the space-time continuum!! UTC should be Universal Time Coordinates, so you can't just go switching it back and forth like it was some Nintendo Switch. . . . oh, excuse me, there has been a terrible disturbance in the Farce.
But seriously: There is no reason for the reset on mod points to be 12am EDT, unless SoylentNews is just some punk American site. And we know it is not. Think about the Australians, just waking up and having to deal with drop-bears and Bufo-toads, again! Think about the Chinese, and all the tea in China, and cell phones! Think about the Silk Roaders in Samarkarand! And think about the Turks, Bulgarians, Hungarians, and the Gariangarians, and the Czechs. So I say, let the chips fall where they may! If god did not want UTC to be Greenwich Mean Time, he would not have put England at the center of the world. Just saying. Bloody Brits!
(Score: 2) by aristarchus on Thursday March 16 2017, @03:17AM (2 children)
Hmm, modded flamebait? Well, it is conceivable. But point remains, that yesterday, GMT and UTC were where they were supposed to be. And today? I presume +5? Or are you just playing with me? This has all the marks of a Mighty Buzz practical joke. It's just like that time when we put a fish on his hook, just to make him think he actually caught something!!! Ha! That was sooooo funny! The look on his face! But then he saw the price tag from the grocery store that we forgot to take off. Damn.
(Score: 2) by aristarchus on Thursday March 16 2017, @05:06AM (1 child)
Watching! UTC 5:06! This is not a big thing.
(Score: 2) by aristarchus on Thursday March 16 2017, @05:12AM
UTC 5:10: internal server error, but upon refresh, I have five freshly minted mod points. So we are going with this? Or is it just me?
(Score: 0) by Anonymous Coward on Wednesday March 15 2017, @03:11PM
What about setting the maximal number of mod points to 6, and handing out a new one every 4 hours for any account that is below 6 points at that time? That would evenly spread it out across the time zones.
Note also that calculation of mod points could be done lazy (assuming that isn't already done anyway): Only when someone accesses the page from his account, he can see and use the mod points; so the code could just fetch the mod points and time of last update from the database (it has to fetch the mod points anyway, and if the time stamp is in the same table, it should not require any additional database lookups), check if any new points have been handed out in between, and if necessary update the points accordingly. At the time of giving out mod points, nothing special would need to happen.
Indeed, the update of stored mod points in the data base would only be required when actually moderating.
(Score: 2) by paulej72 on Friday March 17 2017, @01:51AM
Well I thought I changed this, but the change did not take. I restarted the backend service and I hope that point will go out at 00:10 UTC. I just manually run the update now so you should all see your points now.
Team Leader for SN Development