Psst... We're working on the next generation of Chowhound! View >
HOME > Chowhound > Site Talk >
Jan 28, 2013 03:07 PM

Functionality Changes Released Monday, Jan 28

We released four changes to the way discussions work today that I wanted to describe to you here. These are not huge changes, but they may be slightly confusing initially for users, especially those of you who are used to the way "already read" has worked historically.

1. As a logged-in user, when you've read an entire discussion, that discussion will now be in a fully collapsed state. In the past, it was in a fully expanded state. We have changed this in order to make it clear that collapse works to help distinguish what you've read. You can expand a fully collapsed discussion by clicking on the + button at the top of the page.

2. We have added a new feature that allows users to hide nested replies if they choose to. You can do this by clicking the > next to the number of replies at the top of the discussion. Logged-in users will have "show all nested replies" as their default. If you would like to have a "hide nested replies" as your default view, you can set that yourself in your profile. Go to Profile, then click Settings, then click Chowhound. On that tab, you will have a choice about your "Default View."

3. When you reply to the original post on a discussion, your reply will now show up to you at the top of the page. If you view the page again, it will appear in chronological order with the other replies. This is only for replies to the original poster.

4. We have moved the login to a stand-alone page which is secured. This is as added security measure to protect user e-mail addresses and passwords.

Thanks for your continued feedback, and for being loyal users of Chowhound,


  1. Click to Upload a photo (10 MB limit)
  1. Feature 1 seems to work. Now if you would just replace "+" with "-" after expanding, so that I can collapse it manually, I'll be happy with that aspect of the implementation.

    1. PROBLEM:

      An issue seems to have cropped up. In two separate threads, I've wanted to expand *just* the comment to which someone was replying, and it won't expand. You used to be able to click on the first line showing in the nested reply, and it would expand.

      For instance, for *this* particular post where mariacarmen is responding to something I had written earlier (and was now collapsed....

      I clicked on the text in my reply - and nothing happens. NONE of the collapsed *individual* comments will expand. I don't want to expand the entire thread. I just want to expand one or two on an as-needed basis. I hit refresh, and all posts are now collapsed. And *nothing* will open up. That makes no sense.

      19 Replies
      1. re: LindaWhit

        Linda- I just noticed that too. I thought there was something wrong and kept trying to refresh, etc. Agree that does not make sense at all!!!

        1. re: foodieX2

          And it JUST seemed to happen - no problem when I was at work an hour earlier. When I tried to log on this evening at home, there were problems. I'm assuming they were firing up the new log-on screen and the entire site was "on hold" while they added the changes.

          But mudaba, this is a *really* serious issue to not be able to expand an individual comment. In threads that get to 200 to 400 posts long, I most certainly would never expand the entire thread to read just ONE post. It would be impossible to find in such a long thread.

          1. re: LindaWhit

            Hi LindaWhit,

            I just saw this. It seems to happen when there is a #first_unread in the URL. We're looking into it.

            1. re: meshane

              Yup, that's showing for your post (I clicked at the # showing for the # of posts in the thread, and that's in the URL).

              Thanks so much for checking it out.

              1. re: LindaWhit

                For now, I recommend clicking on the thread title from a category page instead of number of replies or last replies column. We'll get a fix out as soon as we can. Sorry for the inconvenience.

                1. re: meshane

                  Sounds good. That's the way I *used* to access the threads and then hit the PgDn button to quickly scan through to find new comments.

                  Much appreciated for the quick responses, meshane.

        2. re: LindaWhit

          Strange, LindaWhit. I'm not seeing that at all. When I go to a partially read discussion, or a fully read discussion, I can click any of the collapsed posts and they open, just as they always have. Which browser are you on? We can test for exactly what you're experiencing. Thanks,


          1. re: mudaba

            I'm on Chrome, whatever the latest version is.

            AND - something else just happened. I posted a reply to chowser here:


            And when I hit the button to post...EVERY post above chowser's post expanded on that thread. And same thing just happened in this thread - the entire thread has expanded.

          2. re: LindaWhit

            Expansion of individual posts should now be fixed. Thank you for the quick report, and please let us know if anything else is awry.

            1. re: Engineering

              It wont let me open the individual posts in this thread. I am using safari.

              1. re: Engineering

                Thanks, Engineering - it does seem to be fixed!

                1. re: LindaWhit

                  Thanks LindaWhit,

                  We hope to fix the 2nd issue you reported later this week.

                2. re: Engineering

                  HOWEVER....are all posts above the one a user posts supposed to then expand when a user hits Save? That continues to happen - the screen bounces around a bit as they're all expanding and then it settles back on the post I left.

                  1. re: Engineering

                    I'm not able to open individual posts either.

                    Firefox/Mac OS

                    1. re: Melanie Wong

                      After testing more than a dozen threads before posting the bug, 18 minutes later, the next five threads I open work fine for opening individual posts, including this thread.

                      ETA: No, still not working when opening threads for first unread post.

                    2. re: Engineering

                      foodieX2 and Melanie Wong,

                      We just released another update. There is a slight chance that this will fix the issue you're seeing, although I'm a little surprised you are still seeing it at all. We're not able to reproduce it here. It's worth taking another look, and if you are still seeing it, please report back with your OS and browser (I know you've already done this mostly), the full url where you are seeing it, and the steps you take to reproduce it. It sounds Melanie Wong like you're seeing this only when you click on the reply count field for an updated discussion and have "#first_unread" in the url, which is what I was seeing previously? Is that correct?

                      1. re: meshane

                        Seems to be working as intended now, thank you. Yes, it was only a problem for threads with "#first_unread" in the url, and I tried with threads I participated in and those I'd not across a few boards.

                        1. re: meshane

                          Sorry for the delay. Yes it is working now, It seemed to be an issue when I clicked on the new thread option

                    3. Showing my ignorance, but I don't know what a "nested reply" is.

                      1 Reply
                      1. re: c oliver

                        I assume they mean an indented reply to a comment posted to someone other than the OP -- like this repy to your comment. And, if someone replies to me, it will indent -- i.e., "nest" -- even further.

                      2. we'll all need to learn how to hit and use faithfully the addition of a # replies button on the side of any individual comment in order to read every reply.

                        For instance, Linda has 4 replies in this thread and before I hit her nested 4 replies I couldn't follow the entire understand a) what was going on and b) what had already been said.

                        7 Replies
                        1. re: HillJ

                          If you're a logged-in user, you have a choice of viewing discussions in two ways:

                          1) Only show top-level responses to the original post. If you choose this option, you'll need to press the expand button to see the nested responses, as HillJ describes.

                          2) Show all responses. If you choose this option, you'll always see every response displayed. This means that the view you'll have of discussions won't be changed in this release.

                          You can access your settings in Profile > Settings > Chowhound.

                          As mudaba mentions above, all non-logged in users will see View #1. All logged-in users who joined the site before January 28th will have a default of View #2, though they can change it if they'd like.

                          1. re: Dave MP

                            The improvements/new features to My Profile, tab and subtabs, (including a Chowhound subtab to adjust personal preferences) is terrific and the start of a whole new way to read threads I imagine.

                            1. re: Dave MP

                              wondering why would anyone not want to see all nested replies as a first preference? much of the time the response location of thread participants is fairly arbitrary with folks getting activated to jump in to discussions and provide their content at random locations. especially when there is no "reply to original post" option right there. To me, this is a refinement without a real rationale for new users which will reduce what they see when they dont refine their site access. For example, I wouldnot have a clue what was happening unless I read this thread.. So maybe we should be keeping it simple and have the open all the default setting for everyone.

                              1. re: jen kalb

                                Here's a further complication: This post shows <16 replies in the lower right corner. I can toggle to show no replies or 8 replies currently. Where do I find the full 16? Or should I only be counting the 2 replies that are in direct response to that post? If that's the case, why state that there are 16?

                                1. re: Melanie Wong

                                  I'm seeing 16 replies nested under that post- nine in the branch that starts with Ipsedixit, and seven in the branch that starts with violatp. Are you seeing something different on your end?

                                  1. re: Engineering

                                    The branch that starts with ipsedixit was missing, all but this one from greygarious. Since it was in reply to mike2401, I tried clicking on "mike2401" and the cursor shot up to the top of the replies and not to a post by mike2401, which implies that that post had been removed.

                                    Looking at it today, the branch has been restored. But I checked it three times before posting the bug two days ago, and it was not there that I could find.

                                    1. re: Melanie Wong

                                      Sounds like a bug in the new feature that we fixed yesterday. It shouldn't happen again- sorry for the confusion in the interrim.

                          2. I love #3, thank you!

                            Today I'm not seeing the "reply to original post" link at the bottom of the thread. has that been removed?


                            2 Replies
                            1. re: jujuthomas

                              juju, that's been missing since the larger reformat. Not sure if they're going to have it return, although it makes a LOT of sense. You have to click "To the Top" and *then* reply.

                              1. re: LindaWhit

                                Thanks Linda, I guess that just sank in this morning, LOL.