Posted By: SlackmasterK | Jul 11th @ 7:56 PM
page 1 of 1
Comments: 6 | Views: 672
SlackmasterK
SlackmasterK
I write my OWN blogging engines

CSS in general seems to be disabled (Possibly due to the W00terz incident).  Would it be possible to add some basic formatting such as padding, background-color, etc?  I don't know if the [quote] system has been replaced with something useful, so I've been trying to use divs.  Unfortunately, my formatting gets lost in the process, so there's no way to tell the quoted text from the actual content of the reply.

Being able to quote manually in this manner is important for inline quotes (i.e. responding to one para at a time) and for quoting articles, other sites, etc.

CannotResolveSymbol
CannotResolveSymbol
{insert caption here}
SlackmasterK said:
Being able to quote manually in this manner is important for inline quotes (i.e. responding to one para at a time) and for quoting articles, other sites, etc.

Like this?

Syntax is the same as the old c9, removing the dash before quote:

[-quote user="Username"]Quoted text[/quote]
Duncanma
Duncanma
Just Coding for Fun...
I see that CannotResolveSymbol has answered your question around quoting, but thanks for pointing me to that thread... I liked this quote by littleguru

littleguru said:
One thing I don't understand about Channel9 is why they allow HTML anyway... They should just enable a few tags and that's it... Not disable tags, just enable a few and all others don't work.

Another thing is why are the posts saved as HTML in the database. If you look at older posts they have still the old quote symbol in there. I mean they have replaced that a while ago: if the forums would be designed in a way that those stuff is parsed before send to the client they would look have the new symbol. This means this stuff is stored in the database. It's not a clean design in my eyes.


Since we now enabled only a few tags, and we don't save our quote, smileys or other bbcode-generated html into the database... I like hearing that this was all discussed (and requested) before Smiley
Duncanma
Duncanma
Just Coding for Fun...
That is a good idea about the preview, we are using the built-in preview of the editor, to show a true preview we'd need to send your content back to the server and then display the results... definitely would be more clear about what is going to happen when you post though.

Not sure what you mean about editing... do you mean that via edit you can use these formats (in which case that it is a bug), or that you see the formatting that you originally entered ... even though we strip that formatting when we display the post?

If it is the second, that is by design to cover three scenarios:

  1. If we change our output formatting in the future (to format quotes differently, add/remove words from our censor list, add/remove html tags and attributes ... ) then your content will get reformatted correctly... if we formatted it and saved the formatted version then we lose that ability
  2. If you see the formatted output and decide to edit it... you get exactly the content you entered ... so if you created some malformed html and don't like the result when we *fix* it ... then you go back in, touch up the markup or content and our formatting gets applied again. (obviously, a better preview would help for this one)
  3. If we have a bug in our formatting (like we did a few weeks ago with images, or like we do right now around smilies at the end of lines) and then fix it... all past posts will get fixed at the same time. This is really just #1, but for a different reason.

 

Duncanma
Duncanma
Just Coding for Fun...
Yep, we do a certain amount of filtering during input (whatever the edit control does plus little else), then we do the major filtering during output... that way we leave your source alone... if we have a bug or we if are being overzealous with our filtering, it isn't a permanent issue.
page 1 of 1
Comments: 6 | Views: 672