Just try quoting a post that contains other quotes. Gives a "message body empty" error.
FF17, W7.
w/o the full editor test
ETA worked fine
some stuff going on with da full .... but it still worked OK?
qr -preview -post test ... worked fine? confused :P
Sorta... but:
- You can't make embedded quotes
- preview isn't working the first time you click 'preview': it displays nothing
- [trivial"'The message has the following error or errors that must be corrected before continuing: Warning - while you were typing 2 new' - this message is too worrying for a poor update notice...
Okay the second two have nothing to do with this topic.
Save another draft... if you can.
Update: it replaces the old, when you keep writing. Okay, but then, the section 'Load drafts' ... wait.
On a different note,
Is it only me or the icons in quick reply (full editor) are far too big? Same for standard post page. (ignore if it's only me)
Lesse if it does it again.
// Show information about events, birthdays, and holidays on the calendar.
if ($context['show_calendar'])
{
echo '
<li class="smalltext">';
Aha! Ok, reproduced it. Try quoting the post above this. The one with quote followed by code followed by quote. ;)
Oh and also note that the quoteheader links are broken. Formatting is up the poo and the link aint linked.
It's only you. They're a pretty good size IMO. FFS, http://en.wikipedia.org/wiki/Fitts%27s_law
- Buttons and other GUI controls should be a reasonable size; it is relatively difficult to click on small ones.
The current icons and buttons should not be made any smaller. If any change was going to be made, I would make them bigger. In fact for general usability there is much to be said for padding out the smileys to match the size of the toolbar buttons. This can be done with a visible background, or just by adding css padding to the images themselves.
The quoteheaader link is a problem with sceditor.
I've put a temp patch in place but the official fix from Sam will be a couple of days out. Basically when you swapped in and out of source->wizzy->source the attributes would get wrapped in quotes. So author=Antechinus would become author="Antechinus" and so on with all the attributes. Then parse_bbc would not know what to do cuz its parse_bbc you see.
I'll work on the preview not working first time next :)
Thank you! :D
Surprise from 1.4.0 looks like 8)
That was not "working" since the Remove nested quotes when quoting option was set, so it was doing what it was supposed to do, strip quotes inside the quote .... almost seems like that option should be level N+1 or something ... oh well turned it off to make this post
That option's behavior is so non-intuitive and bewildering. Yeah it could be argued it "simplifies" posts sometimes, but it misses information you could always edit out if you don't want it.
/me knows Ant will disagree.
I strip nested quotes on the site I run. It's a good option IMO. Most users simply will not clean up things when the quotes start building to ridiculous levels. Stripping it all down to one level is much better in practice, even though it's sometimes inconvenient for people who are responsible enough to not just blindly keep hitting "Quote".
IMO, we should keep that option. Although if an N+1 option can be made bug-free easily then that would be great too, but it may be more difficult than some people think.
/me hates quote altogether.
/me quotes emanuele for posterity.
It's only me or quotes are completely broken now?
You know for someone who works on bug reports as much as you do, you sure write some crappy descriptions of what you are experiencing :P :D :P
This was done as a quote to QR with full editor on and shown by default ... seemed to be fine?
mmm...something is not working (something badly processed by parse_bbc? or something not properly escaped?) when non-admins posts.
ETA: no, it's also others:
http://www.spudsdesign.com/dialogo/index.php?topic=12.msg34#msg34
Take a look at my post with the image and the url: the image is working properly, the closing tag of the url is ignored and the entire post is linked.
You know that looks like a bug :o I would suspect its something to do with the editor script ... well the extensions that is ... remember bug hunting is fun for the entire family!
I thought the same with js disabled.
You are teh best!