Users are reporting issues with the quoting feature in Discourse 2.6.0 beta versions, where the quote button sometimes fails to appear, especially when selecting text across different HTML elements like code blocks or headers. The problem seems inconsistent, occurring on some sites but not others, and may be related to theme or plugin customizations. Some users, like Andro, initially experienced the issue but found it resolved after updates, while others, such as francislavoie and jesus2099, continue to face it on specific sites like caddy.community and community.metabrainz.org. Suggestions include checking for outdated plugins, testing on a minimal instance like try.discourse.org, and updating to newer versions. The issue may stem from browser behavior, site-specific configurations, or a Content Security Policy (CSP) error on certain platforms. pfaffman advises removing unupdated plugins, and RGJ clarifies that 2.6.0 and 2.7.0 beta 1 are functionally similar, so waiting for updates may not help. Ultimately, the problem appears to be intermittent and potentially tied to site-specific setups.
On any browser, quoting seems to have become completely random - on some material it works, on others, no quote button is displayed. I can’t see any pattern in it. Using Discourse 2.6.0 beta5.
What am I missing? Is there some setting to adjust? But it just seems buggy.
Hey Andrew, is this an issue you’re having with the Discourse Wordpress Plugin, or just with Discourse? If it’s just with Discourse, please change the category of your post to Support (it’s currently Support > WordPress).
As to the issue itself, could you talk us through some steps to reproduce the issue you’re having, for example:
More testing shows that it is the case that I cant quote text that occurs after a quote. That can’t be desired behaviour, can it? Text before a quote I can quote.
Ah, Ignore all this. It’s a poster who puts in manual line breaks (hard to see at first) and when you select what looks like a paragraph, quoting does not work. So it’s not really an issue. I was wondering why this suddenly started happening - it’s just posts from one erratic user. Most likely posts submitted by email that has wrapped the lines.
It seems to happen when the selection crosses the boundary of HTML elements.
For example, if I select text that is totally contained within its own <p> with no <code> elements, it works fine, but as soon as I start also selecting the <code> bit, it doesn’t show the Quote button.
If I select a whole header (see any help post on the forums, which use a template for OP, with headers) then quote appears, but if selecting a header line plus the next line which is a <p>, then there’s no quote.
I’m not certain this is the cause, but it seems to be. This all used to work before, I could select anything I wanted to quote it. It’s been broken for idk, maybe a month? Hard to say when it started being a problem. We’re using 2.6.0.beta5 right now.
It’s not theme related. I tried several themes. I don’t know how to show this here, but as mentioned, some of my users submit by email, and email clients do all sorts of unmanageable things with line wrapping and hard returns. On the particular page where I noticed this, what looks like a coherent paragraph is a set of lines separated by in the HTML. You can quote the lines, but not the whole paragraph. Here is an attempt to show this:
This just a test. Seems you can't quote whole
paragraphs wherelines
are separated by br tags, like
this.
[Now having posted this, it works on this Discourse Meta site, but not on my instance, 2.6.0.beta5 latest update, standard Dark theme.]