Hi, ich arbeite gerade an eine eMail Notification für antville. Die idee: - Der Admin soll entscheiden werde eMails bekommen soll nach bestimmten ereignissen, zB new online stories, new comments etc.

Bin gerade etwas ducheinander, ich möchte das nach einem Comment alle Admis u. Contribs ein eMail bekommen. Hab folgendes gemacht:

• bei .../story/objectFunctions.js eine mail funktion gecht, wie die bei new user+passwrd.
• in comment.hac mus ich meine mail funktion aufrufen oder?
• wie soll es weiter gehen? Any ideas? Danke! Jes.

If you disable the comments, you still can read "place your comment!" under the story.

Beispiel für einen Eintrag ohne Kommentarmöglichkeit, aber mit automatischer Aufforderung zum Kommentieren: irene.antville.org

I just saw such a cool Featureino over at Textism; check this: The PHP script (which could easily be re-implemented in Helma-ish ECMA) checks if the referrer is Google (one could extend this to other search engines), and if appropriate extracts the query string from the referrer URL, so it knows what the user is looking for at your site. Nothing groovy so far, that's what your vanilla eXTReMe tracker does, but now comes the clever bit: It marks up all occurences of the search terms in the response so they'll be highlighted with a little help from Mr. Stylesheet!

Antville needs this (or maybe it should be implemented at Helma level?)! Okay, maybe not now, with all the effort being put into getting a fine 1.0. But at some point, we've got to catch up with the competition. Maybe I'll even have a shot at it myself once I've got some spare time again.

More ideas: If there are a lot of search engine queries in the backlinks, you have a long list of links that start like "www.google.com..." and are cut off from there anyway. See the frist comment for an example of how silly this looks. We could replace the texts of those links with just the actual search terms and display this list of queries in a block instead above each other (to make it less bloated). Then we'd have the individual keywords extracted anyway and could use those for highlighting, if an apropriate option is turned on.

I figured out that using <% story id="..." %> you can easily make editable boxes in your template for linklists, desktop wallpapers, current readings etc. Here is little explanation in German. It only works because I'm using the story.display skin in a way it is not intended. A nicer solution would be an additional skin, say story.include.

It's just a new skin and tiny modifications in the skin manager (additional field) and the <% story %> macro (new default value for the skin). If you agree I can make the changes.

Is there a feature that lists all weblogs I wrote a comment to ? I usually end up with the same weblogs some other people read (gHack, katatonik cloud) and would like to play with this.

actually, i didn't want to implement the weblog on the frontpage feature. i was thinking about improving the static version.

but while thinking of it, i had the following idea: we use a regular weblog, say site.antville.org, which is displayed on the frontpage by using a yet to created macro. i.e. the page www.antville.org looks exactly like site.antville.org. the comments, image, file, stories and skin managers can remain on site.antville.org. i suppose this means there is no need to define all weblog functions for the main site.

Maybe a nice idea to increase individual weblog stickyness to:

Make it possible for registered users to select if they want to be notified by email is there is a reply to their comments on stories. With a direct link in the message to that story. Same feature as a lot of forums and messageboards have.

GreetZ, Peter Lunk