Stories
Slash Boxes
Comments

Dev.SN ♥ developers

Dev.SN is powered by your submissions, so send in your scoop. Only 6 submissions in the queue.

Log In

Log In

Create Account  |  Retrieve Password


Site News


Funding Goal
Base Goal: $3000
Progress So Far: $116
4%
Stretch Goal: $2,000
Progress So Far: $0
0%

Updated: 2017-01-14 --martyb


Support us: Subscribe Here


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.

Poll

How many days are left before Christmas?

  • less than 20 but more than 10
  • 10 or fewer but more than 5
  • 5 or fewer

[ Results | Polls ]
Comments:3 | Votes:4

posted by martyb on Wednesday February 15, @10:14PM   Printer-friendly

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

posted by paulej72 on Wednesday February 15, @10:12PM   Printer-friendly
Getting hash instead of preview. Are we not using the hard coded generation? Do we need to keep the templates so this works?
posted by martyb on Wednesday February 15, @05:03PM   Printer-friendly

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.

posted by The Mighty Buzzard on Wednesday February 15, @03:23PM   Printer-friendly
Need user-preference for dimming/badge. Need badge graphic. Need code/css reworked to put the appropriate one into the page.
posted by The Mighty Buzzard on Wednesday February 15, @03:18PM   Printer-friendly
Behaving how I wrote it to but not accurately reflecting Threaded on Live.
posted by The Mighty Buzzard on Wednesday February 15, @03:15PM   Printer-friendly
Page 2 on https://dev.soylentnews.org/comments.pl?noupdate=1&sid=1344&mode=threadtng&page=2 does not properly collapse comments.
posted by martyb on Wednesday February 15, @01:11PM   Printer-friendly

20170215d - clone of 20170215b - Please Moderate but post no comments

[cONTINUES...]

:: Specify cookie first, otherwise, the chain of invocations ends up defaulting to martyb:
CALL SN_API_cookies "cookies.martyb.txt"

:: This is the story we want to post comments to:
CALL SN_API_story_URL "https://dev.soylentnews.org/article.pl?sid=17/02/15/1622227"

:: Non-subscribers need to wait 10s after getting reskey before they can post a comment;
:: Subscribers do not need to wait:
CALL SN_API_comment_sleep 0s

SET sn
PAUSE

CALL comment 0000
SET sn
PAUSE
   CALL comment 0001 --reply-to 0000
      CALL comment 0002 --reply-to 0001
         CALL comment 0003 --reply-to 0002
         CALL comment 0004 --reply-to 0002
      CALL comment 0005 --reply-to 0001
         CALL comment 0006 --reply-to 0005
         CALL comment 0007 --reply-to 0005
   CALL comment 0008 --reply-to 0000
      CALL comment 0009 --reply-to 0008
         CALL comment 0010 --reply-to 0009
         CALL comment 0011 --reply-to 0009
      CALL comment 0012 --reply-to 0008
         CALL comment 0013 --reply-to 0012
         CALL comment 0014 --reply-to 0012

CALL comment 0015
   CALL comment 0016 --reply-to 0015
      CALL comment 0017 --reply-to 0016
         CALL comment 0018 --reply-to 0017
         CALL comment 0019 --reply-to 0017
      CALL comment 0020 --reply-to 0016
         CALL comment 0021 --reply-to 0020
         CALL comment 0022 --reply-to 0020
   CALL comment 0023 --reply-to 0015
      CALL comment 0024 --reply-to 0023
         CALL comment 0025 --reply-to 0024
         CALL comment 0026 --reply-to 0024
      CALL comment 0027 --reply-to 0023
         CALL comment 0028 --reply-to 0027
         CALL comment 0029 --reply-to 0027

posted by martyb on Wednesday February 15, @01:01PM   Printer-friendly

20170215c - Test Story - Please Moderate but Post No Comments - Bifurcation Breadth-First

This story and its comments is intended to be a clone of 20170215a -- please post no comments, but DO feel free to moderate! --martyb

:: Specify cookie first, otherwise, the chain of invocations ends up defaulting to martyb:
CALL SN_API_cookies "cookies.martyb.txt"

:: This is the story we want to post comments to:
CALL SN_API_story_URL "https://dev.soylentnews.org/article.pl?sid=17/02/15/175202"

:: Non-subscribers need to wait 10s after getting reskey before they can post a comment;
:: Subscribers do not need to wait:
CALL SN_API_comment_sleep 0s

SET sn
PAUSE

:: Create 2 top-level comments
CALL comment 0000
SET sn
PAUSE
CALL comment 0001

:: Create replies (2nd-level comments) for each of those TLCs:
CALL comment 0002 --reply-to 0000
CALL comment 0003 --reply-to 0000

CALL comment 0004 --reply-to 0001
CALL comment 0005 --reply-to 0001

:: Create replies (3rd level comments) for each of the 2nd-level comments:
CALL comment 0006 --reply-to 0002
CALL comment 0007 --reply-to 0002

CALL comment 0008 --reply-to 0003
CALL comment 0009 --reply-to 0003

CALL comment 0010 --reply-to 0004
CALL comment 0011 --reply-to 0004

CALL comment 0012 --reply-to 0005
CALL comment 0013 --reply-to 0005

:: Create replies (4th level comments) for each of the 3rd-level comments:
CALL comment 0014 --reply-to 0006
CALL comment 0015 --reply-to 0006

CALL comment 0016 --reply-to 0007
CALL comment 0017 --reply-to 0007

CALL comment 0018 --reply-to 0008
CALL comment 0019 --reply-to 0008

CALL comment 0020 --reply-to 0009
CALL comment 0021 --reply-to 0009

CALL comment 0022 --reply-to 0010
CALL comment 0023 --reply-to 0010

CALL comment 0024 --reply-to 0011
CALL comment 0025 --reply-to 0011

CALL comment 0026 --reply-to 0012
CALL comment 0027 --reply-to 0012

CALL comment 0028 --reply-to 0013
CALL comment 0029 --reply-to 0013

posted by martyb on Wednesday February 15, @12:20PM   Printer-friendly
from the please-do-not-touch dept.

20170215b - Test Story - Please Make NO Changes - Bifurcation Depth-First

Carefully crafted comment structure here, please post no comments, and perform no moderations. THANKS! --martyb"

[Continues...]

:: Specify cookie first, otherwise, the chain of invocations ends up defaulting to martyb:
CALL SN_API_cookies "cookies.martyb.txt"

:: This is the story we want to post comments to:
CALL SN_API_story_URL "https://dev.soylentnews.org/article.pl?sid=17/02/15/1622227"

:: Non-subscribers need to wait 10s after getting reskey before they can post a comment;
:: Subscribers do not need to wait:
CALL SN_API_comment_sleep 0s

SET sn
PAUSE

CALL comment 0000
   CALL comment 0001 --reply-to 0000
      CALL comment 0002 --reply-to 0001
         CALL comment 0003 --reply-to 0002
         CALL comment 0004 --reply-to 0002
      CALL comment 0005 --reply-to 0001
         CALL comment 0006 --reply-to 0005
         CALL comment 0007 --reply-to 0005
   CALL comment 0008 --reply-to 0000
      CALL comment 0009 --reply-to 0008
         CALL comment 0010 --reply-to 0009
         CALL comment 0011 --reply-to 0009
      CALL comment 0012 --reply-to 0008
         CALL comment 0013 --reply-to 0012
         CALL comment 0014 --reply-to 0012

CALL comment 0015
   CALL comment 0016 --reply-to 0015
      CALL comment 0017 --reply-to 0016
         CALL comment 0018 --reply-to 0017
         CALL comment 0019 --reply-to 0017
      CALL comment 0020 --reply-to 0016
         CALL comment 0021 --reply-to 0020
         CALL comment 0022 --reply-to 0020
   CALL comment 0023 --reply-to 0015
      CALL comment 0024 --reply-to 0023
         CALL comment 0025 --reply-to 0024
         CALL comment 0026 --reply-to 0024
      CALL comment 0027 --reply-to 0023
         CALL comment 0028 --reply-to 0027
         CALL comment 0029 --reply-to 0027

posted by martyb on Wednesday February 15, @11:33AM   Printer-friendly
from the please-do-not-touch dept.

20170215a - Test Story - Please Make NO Changes - Bifurcation Breadth-First

Carefully crafted comment structure here, please post no comments, and perform no moderations. THANKS! --martyb"

[Continues...]

:: Specify cookie first, otherwise, the chain of invocations ends up defaulting to martyb:
CALL SN_API_cookies "cookies.martyb.txt"

:: This is the story we want to post comments to:
CALL SN_API_story_URL "https://dev.soylentnews.org/article.pl?sid=17/02/15/1536203"

:: Non-subscribers need to wait 10s after getting reskey before they can post a comment;
:: Subscribers do not need to wait:
CALL SN_API_comment_sleep 0s

SET sn
PAUSE

:: Create 2 top-level comments
CALL comment 0000
SET sn
PAUSE
CALL comment 0001

:: Create replies (2nd-level comments) for each of those TLCs:
CALL comment 0002 --reply-to 0000
CALL comment 0003 --reply-to 0000

CALL comment 0004 --reply-to 0001
CALL comment 0005 --reply-to 0001

:: Create replies (3rd level comments) for each of the 2nd-level comments:
CALL comment 0006 --reply-to 0002
CALL comment 0007 --reply-to 0002

CALL comment 0008 --reply-to 0003
CALL comment 0009 --reply-to 0003

CALL comment 0010 --reply-to 0004
CALL comment 0011 --reply-to 0004

CALL comment 0012 --reply-to 0005
CALL comment 0013 --reply-to 0005

:: Create replies (4th level comments) for each of the 3rd-level comments:
CALL comment 0014 --reply-to 0006
CALL comment 0015 --reply-to 0006

CALL comment 0016 --reply-to 0007
CALL comment 0017 --reply-to 0007

CALL comment 0018 --reply-to 0008
CALL comment 0019 --reply-to 0008

CALL comment 0020 --reply-to 0009
CALL comment 0021 --reply-to 0009

CALL comment 0022 --reply-to 0010
CALL comment 0023 --reply-to 0010

CALL comment 0024 --reply-to 0011
CALL comment 0025 --reply-to 0011

CALL comment 0026 --reply-to 0012
CALL comment 0027 --reply-to 0012

CALL comment 0028 --reply-to 0013
CALL comment 0029 --reply-to 0013