| Age | Commit message (Collapse) | Author |
|---|
|
correctly
|
|
|
|
|
|
|
|
|
|
|
|
|
|
name of page
Also:
* decide comment page name sooner
* set permalink on it
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Not compacting whitespace is the most important one: now that we run
sanitize hooks on individual posted comments in the comments plugin,
whitespace that is significant to Markdown (but not HTML) is lost.
|
|
Now that posts are individually sanitized, that should be safe.
|
|
|
|
|
|
This should ensure that users can't "break out" from the enclosing
<div>, making it impossible to forge comments (assuming htmlscrubber
is enabled, and so is either htmlbalance or htmltidy).
|
|
|
|
The PageSpec is still called "postcomment" since that's what it means.
|
|
|
|
|
|
|
|
Also put "posting comments disabled" in [], and change "Page preview"
to "Comment preview".
|
|
better
|
|
commenting on pages where comments have never been allowed
|
|
|
|
|
|
wikilinks are harmless, so we might as well allow them.
Access control for this plugin is a bit odd, since we specifically
don't want to allow comments to be edited - so the check is whether the
user is allowed to edit a deliberately invalid page name,
page/commented/on[smcvpostcomment]. You can put smcvpostcomment(*)
or smcvpostcomment(some/subdir/*) in $config{anonok_pagespec}
or the opposite in $config{locked_pages} to allow "editing" (really
just posting) comments.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
.inlineheader
In the initial template for blog-style comments, I don't want the author
name to be quite as large and prominent as the author of a blog post - I
expect that comments will be rather short, so the author name stands out
better for a given font size.
|
|
smcvpostcomment)
|
|
|
|
|
|
|
