Unfortunately I had to pull the plug

I’m not insulted in the slightest, and this isn’t uncommon. From time to time people post about how much better Discourse would be if it emulated feature X from product Y, whose roots are ~15 years in the past.

The thing which drew me to work with Discourse initially was that it’s not trying to be any of those things. If it was then half of the communities I work with wouldn’t be able to do the things Discourse enables.


I suppose there might be one case where auto-quoting makes sense: when replying to a post which occurs mid-way through a long topic.

Without the quote, it’s hard to see the context, as there may be many posts between the “source” and reply post.

Perhaps it would make sense for Discourse to automatically quote (but only in this case)

1 Like

Great that you did not take it as an insult, I really think you guys are a step ahead from the other softwares (and I’ve tested plenty). I spent more than 1h per day here trying to learning more and more. The possibilities here seem endless.

I have no complaints at all. Team/staff also is so helpful.

Just the quote-think that are getting some members confused and I’m trying to listen all of them and make it comfortable for everyone… seeing the possible to replicate it with a plugin on marketplace and make it a option. Do you think its possible?

Isn’t that what this button is for? It’s automatically generated for any reply made where posts sit between the post and a response.


When clicked it shows an embedded version of the post being responded to, without losing place in the topic. There’s an arrow in the embed to take you back to the reply in question too.


I agree with you. But not the whole thing (multiple quotes in one) as i said.

On mobile it take you to the post. If you reading post #88 per example, and that person replied post #33 without quoting, you click on it to see the reply and get redirected. Then you need to scroll back or click on “BACK” button to continue reading. If you do this several times, it can be exhausting.

1 Like

Yes, those features are very useful. But they require a) the user to be aware of them and b) clicking to reveal the context

Late replies without quoting can make a topic can look confusing to the layman. Example (the “yes me” in the below topic, which references a post made earlier in the topic):

I’d suggest Discourse should have auto-quoted the “yes me” post, but avoided auto-quoting the “count me in too Chris”, as this reply came soon after its target post.


This catches me out frequently. You really have to be alert and cross check the avatar to make sure you’re reading it correctly.


Lol, reading this post I made I now understand why @codinghorror get annoyed

Fortunately @ChrisBeach show up to explain in a more intuitive way

Auto-quoting just early replies (the text, not quotes on it) would be great. Just want to know if it’s possible with a plugin too.


@eesty thank you so much for posting feedback here, it certainly helps us.

I did want to quickly address the various points here:

This pops up from time to time. A very strong position we have held ever since the project started is that “we will not add pagination”. At a fundamental level, if pagination is a must then Discourse is not a good fit.

Improving the experience though is on the table, things like allowing users to see bookmarks in the timeline, and fancier timeline controls are things we think about.

Though we will certainly not be adding this to core, amending post actions is completely doable in a theme component if you must. But keep in mind there is an aspect of “we must have MacDonalds” OK… “here is your unhealthy hamburger” to this.

This is something we do work on a lot (and did work on for our current release). It is hard to provide the huge amount of features Discourse has on offer with a very tight performance budget. We try to though, and we definitely made some improvements in the “user with tons of posts” department. @tgxworld even worked on the “giant topic” problem a bit a few month back.

There is a fundamental issue though, to get all the features Discourse has you are going to need more server resources than traditional dead simple php forums.

@neil recently spent a fair amount of time on this ad problems, I would be very curious for any specific reproducible issues. We want to improve this.


Glad to hear it, there are some really pathological quoting behaviors on old platforms and those were absolutely enabled by bad tooling.

So for someone to say, “hey man, we really need those bad quoting tools again…” I’m like … uhhh… no? No you don’t?


Yes, I agree with you.

What are your thoughts on this post? Do you think It be possible to replicate it with a custom plugin?

What is there to replicate? Click the in-reply-to, and that will expand the post that it was in reply to.

Hard agree - the automatic removal of an entire previous post alone has probably saved me many hours.


I know, its a cool feature, but if the quote automatically goes on post that are replying old/early posts on the topic, clicking it would be needed, its right there on you face, its seems more fluid for some. Getting redirected on mobile to the reply by clicking on member’s avatars wouldn’t be needed too.

Anyway, sorry for bothering you guys. :sweat_smile:

1 Like

Right, on mobile it’s kinda bad because we don’t offer that functionality cc @sam but maybe we should start…


I would like us to experiment with “collapse stream” implementation for mobile that shows “11 hidden posts” and then the reply you are digging up on click.


That would be so good

This bug should be fixed as of today. Fix here. The fix is in discourse, not the plugin.

As for the problem of AdSense showing blank ads, it’s hard to diagnose this problem. When you watch the network requests in the browser dev tools, do you see a lot of failed requests to a google domain (status 400)? If you see the requests, then the plugin is doing its job. The bad response from Google can mean that an ad unit defined in AdSense hasn’t become “live” yet. Or maybe these are units you had live on a different site, and aren’t happy being reused on a different site? Or ad units you used in your Discourse settings aren’t defined in your AdSense account. If you’re using Ad Manager, there’s a debug mode you can enable to see more info about each ad unit.


It’s two when you click the quote button though, maybe if you could hold a key and select to quote on release that would feel faster to some?

1 Like

Just to provide a counter-point, for any future readers of this thread:

When we moved our community to Discourse in November of 2016, we had ~110,000 registered users and close to 2 million posts. The old forum was at that point exactly 20 years old, and had been running on the same home-grown software the whole time (with incremental fixes as we went along, of course).

Our community is one of Jaguar car enthusiasts. The type that will argue for months over the correct color of the sticker inside the factory tool kit bag for a 1961 E-Type OTS. You know, people who care about the important things in life.

Needless to say, the differences between our 20 year old cottage industry forum software and Discourse were dramatic. Of course we had complaints, and yes, contributions slowed for a while (we’re based on voluntary contributions, not ads). But it wasn’t as bad as it could have been.

One of the things we did was to set up a “demo” Discourse site in parallel with the old site, and import about a month’s worth of traffic into it, so it didn’t look too much like an empty mockup. Then we invited our users to log on to the demo site, play around with it, and give us feedback. I think that step alone saved us a lot of misery.

We also had a volunteer (now one of our moderators) play around with Discourse before we went live, and then be on hand to answer questions from those who just couldn’t figure out how to use the new software. Lo and behold, after a few months, the complaints had ceased and the contributions were back up to their old level.

Of course, your community could be very different from mine, I have no idea. I’m just saying that it is possible to get a community of mostly grumpy old men, all of whom are averse to change, and most of whom wouldn’t know the difference between a modem and a modal dialog box, to get comfortable with Discourse. In fact, I think now they enjoy it. Not only that, but we’re growing again as a community, after having stagnated for years.

So, it is possible to have a successful transition to Discourse, but it may require some planning. Also, getting feedback from the community before making the plunge can be crucial.