antville mod-filter (last resort)
problem:
you want to disable postings from certain users
(but do not want your blog go private at the same time)

solution:
create a css style-rule that renders posts from distinct users "hidden"

technical how-to: preparation
inside your stylesheet add a rule:
.mod__ {display: none; }

inside your story-skin add a div-element arround the actual skin-content:
{...}.antville.org
or comment-skin:
{...}.antville.org

<div class="mod<% story.creator %>">
... your current skin content ...
</div>

technical how-to: execution
as you want to hide posts from certain people,
you change the style-rule inside your stylesheet

from
.mod__ {display: none; }
to
.modusername {display: none; }
or mod several users at once
.modusername1, .modusername2, .modusername3 {display: none}

could also be used with forms display...


comment    
 
On 2004.05.06, 22:39, meisterkoechin wrote:
Hmm.. too complicated.
:-(((

Can you give me your email please or send me one at cuoca AT gmx DOT net

Thx.

link  

... comment
 
On 2004.05.06, 23:14, dieguteseite wrote:
as i see you changed {display: hidden} to {display: none}
now it works. although the entry in the recently modified is still visible.

maybe you should also point out that if someone wants to use this for the comments it has to be the comment.creator which shall be blocked.

nice idea!

link  

... comment
 
On 2004.05.06, 23:23, kinomu wrote:
i guess you can't do that with the "recently modified".

link  

... comment
 
On 2004.05.06, 23:25, dm42 wrote:
hmm, let me see...

update: no problem - it works all the same way

look at this pages source > recently modified > there is an entry from "popme" that is hidden now

formatting for my recently modified item skin (your skin may look different):

<div class="statusdark mod<% comment.creator %>"><% comment.content part="title" as="link" %></div>

nb: sure you can use more than one class in the class definition of an element

link  

... comment
 
On 2004.05.06, 23:31, popme wrote:
test: you cant see me ;)
you cant see me ;)

link  

... comment
 
On 2004.05.06, 23:36, dieguteseite wrote:
it's also possible to ban it from the recently modified. i just tried.
so the only thing left is that the comments are counted and it can be seen in the sourcecode.
but that shouldn't be the problem.

link  

... comment
 
On 2004.05.06, 23:41, dieguteseite wrote:
you forgot to close the div-tag in the comments. so all the postings after the blocked one can't be seen at the moment. :-)

but really cool. thanks a lot!
i hope i won't need this.

link  

... comment
 
On 2004.05.06, 23:47, meisterkoechin wrote:
Har har har
Dream on, Mr. dgs ;)

link  

... comment
 
On 2004.05.06, 23:53, dm42 wrote:
ok, so this
is really some sort of last resort method. i never needed it - but it always gave me a feeling to be "the admin" of my blog.

i like antville security settings a lot, but also hope that the developers will come up with a bit more "selective" security mechanism in the next releases (besides multiple topics, selectable skins, etc. ;)

link  

... comment
 
On 2004.05.06, 23:57, dm42 wrote:
hell, one knows
why this post is of interest to
hirnverbr.antville.org
?

link  

... comment
 
On 2004.05.07, 13:17, kohlehydrat wrote:
funny thing is that if you mark the whole thread with your mouse and copypaste all the hidden texts become visible.

link  

... comment
 
On 2004.05.07, 13:30, dm42 wrote:
it is, because the text is not removed from the html-source, but parts of it are not rendered by the browser (display: none)

copy/paste functionality transforms the html-source into a textformat regardless of stylesheet settings...

link  

... comment
 
On 2004.05.07, 13:34, kohlehydrat wrote:
true. i'd never considered that one is actually marking html, not just visible text bits.

link  

... comment
 
On 2005.03.15, 08:22, dm42 wrote:
observation 1:
CSS class names are case-sensitive, so
.modescguest, ... {display: none} does not 'work'
but
.modESCguest, ... {display: none} will do.

link  

... comment
 
On 2005.03.15, 08:30, dm42 wrote:
observation 2:
i decided to disable the display of <form ...>s for moded users altogether.

Story editor form / Comments editor
<form method="post" action="<% response.action %>">
gets replaced by
<form class="mod<% username %>" method="post" action="<% response.action %>">

You might have to adjust that to your own customizations.

link  

... comment
 
On 2005.03.15, 09:50, dieguteseite wrote:
wow! thank you for the updates.
do you also have a workaround for nicknames containing spaces?

link  

... comment
 
On 2005.03.15, 10:00, dm42 wrote:
my workaround is to use only the first part of the nickname

like: .modzittas will certainly catch 'zittas kind', as the macro renders this
<div class="modzittas kind">...
(using more than one class name inside a css-class assigment is valid)

link  

... comment

 
Online for 2588 days
Last update: 2008.05.09, 08:12
»Preparing for sodium amytal«
Youre not logged in ... Login
mks @ 25k posts     hohoo - looks like [mks] will see its 25.000th...
by KenoshaKid (2007.12.11, 15:53)
'redirect' switch Say, after creating a new story you want to redirect the user to...
by KenoshaKid (2007.12.02, 12:54)
Ich lass mich überraschen.
by kristof (2007.11.29, 10:33)
im endeffekt wirds nur ein JSON dataset geben, das dann mit scripts frei formatierbar...
by dm42 (2007.11.29, 09:51)
Ach, jetzt auch als "today". Wieviele Clouds wird's denn geben? (Ah, "Yesterday"!)
by kristof (2007.11.29, 09:15)

Juli 2009
MoDiMiDoFrSaSo
12345
6789101112
13141516171819
20212223242526
2728293031
Dezember
... home
... topics
... Home
... Tags


... antville home

XML version of this page

Made with Antville
powered by
Helma Object Publisher