CCCP testing page

A thread especially for those sorting through Musrum’s immensely appreciated efforts with his CCCP browser bolt-ons.

For Firefox, install in order:

Firefox
Greasemonkey
cccp

For Chrome:

Google Chrome
Tampermonkey
cccp

Author: William Bowe

William Bowe is a Perth-based election analyst and occasional teacher of political science. His blog, The Poll Bludger, has existed in one form or another since 2004, and is one of the most heavily trafficked websites on Australian politics.

346 comments on “CCCP testing page”

Comments Page 5 of 7
1 … 4 5 6 7

  8. So you are just leaving the response box at the bottom now? If not, an option in the config to choose whether the response dialog is at the top or bottom would be nice.

  14. Preview doesn’t work, and can’t post comments, since updating to 4.02.

    That is with Firefox on a Mac. (Posting this with Safari.)

  17. New version of cccp is now in Production (PRD)

    // Ver 4.03 (inc 4.00 – 4.02)
    // New major version to deal with Crikey fixing their numbering mess up
    // Only one comment box
    // Redirects back to current page (instead of first page) after posting.
    // Clean up for JSLint

    All other previous functionality has been restored.

  22. Hey Guys

    You’re doing a great job – I’m using Firefox with Ubuntu – couple of things. Is it possible to stay logged in??? And when you first go to the current thread I get the numbers

    1 2 3 … 58

    Which is a little annoying in that you might know you were up to page 56 but to go there you need to go to page 58 first so that you can see pages 56 and 57 – ideally it would be the opposite to how it is now – i.e. page 1 …. 56 57 58

    Just my 2 cents worth and nice to haves rather than must haves – once again thanks for your efforts looks to be working fine

  24. Sorry Musrum, slight bug in 4.03 with an ‘e’ missing from the blockquote line:

    elem.innerHTML = elem.innerHTML.replace(/<\/blockquot>[^<][^\/][^i]/g, ”);

  25. Actually, just puttin g the ‘e’ back in doesnt seem to fix it and printing a ‘>’ in blockquote sections. I’ll leave it to you to sort out.

  26. [Actually, just puttin g the ‘e’ back in doesnt seem to fix it and printing a ‘>’ in blockquote sections. I’ll leave it to you to sort out.]

    OK

  30. I get the red 4 on Tampermonkey too. The only scripts it shows are the uat_ version of cccp 4.04 and the wip_ version of stfu 1.03.

    Your “stfu Settings” is working a treat.

  31. The red 4 means you have a few scripts active.

    I think that because the latest versions of cccp and stfu both use an external script for the config functionality they each count a 2.

    My current setup shows as 2:

  32. Musrum,

    That makes a lot of sense.

    I can’t see any of the scripts in the processes in task manager. I take it they are some of the many chrome.exe *32 processes.

  33. [Dario: I have put your version of stfu into the original script.]

    Sweet!

    [I think that because the latest versions of cccp and stfu both use an external script for the config functionality they each count a 2.]

    Yep, that would do it

  34. I have disabled tampermonkey. The colour is green and I can now post a comment. Is it me or have I got the wrong settings? By disable I mean right click and tick disable. Also have the preveiw box. Which is working. There is no tampermonkey icon on the screen

  36. Ian@234


    I have disabled tampermonkey. The colour is green and I can now post a comment. Is it me or have I got the wrong settings? By disable I mean right click and tick disable. Also have the preveiw box. Which is working. There is no tampermonkey icon on the screen

    You may have an old version of cccp installed. If you participated in any of the testing in this thread you may also have wip_CrikeyClearCommentPreview or uat_CrikeyClearCommentPreview running (which you can disable individually in Tampermonkey)

  37. Musrum and Dario, you are the best.

    The whole thing is looking great.

    A very, very minor improvement, and I’m not sure if I can articulate it clearly, is the colour of a followed link, and maybe I’m the only one who notices it.

    The links stand out well, but once followed they disappear a bit into the general colour scheme, where often I want to find the link again and post it to friends (and enemies!)

    Is there a possibility of making a followed link obvious that it has been followed, but still stand out from the general scheme of things?

    If not, not a problem.

  40. For Chrome:

    Google Chrome
    Tampermonkey
    cccp

    I already run chrome. Do I re-install it? or do I just install tampermonkey? and how do I know whether or not cccp is installed?
    How about some basic children type instructions for those of us who competer language literate.

  42. I’m no expert, Ian, but make sure you install the cccp onto tampermonkey, not native on chrome, which doesn’t work on my machine at least. Doesn’t hurt anything, but doesn’t work either.

    PS Musrum, I should have said tampermonkey not greasemonkey, I guess.

  44. don: yes, you are right. Ian: install into Tampermonkey.

    Also, don: the current link behaviour is the default for browsers.
    On a Mac you should be able to change this default behaviour by editing this file:

    ~/Library/Application\ Support/Google/Chrome/Default/User\ StyleSheets/Custom.css

    And add this rule:
    a:visited { color: red ! important }

    (change the colour to taste)

  45. A suggestion for cccp.

    On posting a comment you are returned to the top of the page where you entered the post.

    Any chance of returning to the last post visible when you posted? If not, to where your post appears?

  46. If you are posting on the last page (and your post doesn’t go over onto a new page) it should work as per your last scenario.

    If you are on an earlier page then it will act as you describe. What is happening here is that because Crikey wants to put you on Page 1, cccp overrides this and puts you on the current page.

    However the server side script also appends a section like this: #comment-1428924 to the URL to force the “go to by fresh post” behaviour.

    When you are on the older pages, your new post will never appear there, and so you are pushed back up to the top.

    I have thought about what I need to do to always go to the new post, and it can get complicated.

    The difficulty is that you can never know with certainty what the number of the last post will be. For example, if you have read 48 messages on the last page you don’t know if your new post will be #50 of the same page or (because someone has posted beforehand) #1 or more of the next page.

    It gets even harder to predict when you are on an older page: the script has no way of knowing the size of the last page. An additional edge case is when William mod-prunes between your page load and your post: you might end up posting to the page before.

    If the script gets it wrong, you will either end up at the top of a page (like now) or back to page 1 (if the page does not exist).

    So it’s a bit of work for a dodgy outcome. I’m hoping Crikey will fix their Page 1 issue before I have to do anything.

    William: if you’re still watching tell them that there is some code in their:
    wp-comments-post.php file that needs to be fixed up to reflect the reverted pagination scheme.

Comments Page 5 of 7
1 … 4 5 6 7

Leave a Reply

Your email address will not be published. Required fields are marked *