Re: Click to expand quote
Reply #30 –
Have you given any thought to allowing a limitation on nested quotes? That's one of the things that gets me about SMF and Elk: You can disable nested quotes entirely, but often in a discussion it is useful to allow at least one level of nested quotes.
The problem is that if you allow nested quotes you will inevitably get people who just keep hitting the quote button, so the number of nested quotes starts going sky high. You can deal with the presentation in the thread, by using CSS to hide any quotes past any level you want, but that doesn't work in the editor. So if you want to edit a post, or reply to it, you're back to having stacks of redundant nested quotes to deal with. Not only is this a PITA for posting, it also bloats the db.
One thing phpBB did right is to allow the admin to set a limit on the number of nested quotes. Anything further down the stack gets dropped before the post is saved in the db. This solves all the problems, while keeping the good points.
Arranging this should be easier now. The new markup should mean you only have to look for quote tags, and don't have to deal with quoteheader tags as a separate issue.
Re: Click to expand quote
Reply #31 –
Had not thought about that, but its a good idea, I kind of hate anything more than one quote anyway.
Would you drop the inner quotes or the outer quotes when over the limit? So say you set a limit of 2 levels deep and you have original Quote -> Quote 1 -> Quote 2 Do you leave Quote -> Quote 1 or Quote 1 -> Quote 2 ?? I guess its what do we think the reply is in reference to, the original or the latest ? Any idea what PHPBB does in this regard (yes that is lazy of me, but WTH)
Re: Click to expand quote
Reply #33 –
I have what I think will work on my local.
Have to do more testing to be sure, because quotes really bite the big one. Basically it will change the remove nested quotes option to a allowed number, 0 = the current remove all, 1 = ummm one nested ...etc etc. This change will change what is actually saved in the DB or sent to the post page, which will save some space in the DB.
An alternative is to simply hide nested quotes, over a the limit. The benefit here is that it is, not destructive, meaning if the admin changed their mind, and increased allowed quotes depth, they would simply show up as normal. The downside is no saving in the DB, which is kind of how it is today if you allow nested quotes.
Preferences / Thoughts ?
Re: Click to expand quote
Reply #35 –
That should now be implemented and live.
I set it at a level 2. Of course it will only effect quotes going forward, previous deeply nested quotes would still show, although those could be hidden via CSS if really wanted.
Re: Click to expand quote
Reply #38 –
Interesting, that blew right through the tag ... to investigate! Thanks for the report.
Re: Click to expand quote
Reply #39 –
I’d argue not a bug… how could it possibly know that [/code] is on this one occasion is different to [/code] to indicate “I’m done with the code now”?
The only way around this would be to assume that the end of a code block must start on a new line which will play hell with converters, not to mention making the code tag even more of a special case than it already is (and behave differently to everything else, e.g. quote where the end tag doesn’t have to be the only thing on the line)
Re: Click to expand quote
Reply #44 –
Indeed I reused the string, providing a unique one is a good idea.
We can just add a new $txt['quote_expand'] = '???; to the same file. Expand Quote, Show More, Show Entire Quote, Read More or Click to expand all seem like good choices.