Just so happens I am setting up Mailman for someone today so was busy thinking about digests

Wouldn't it be easier to have a digest flag on SCT which users could select. Then at a point during the day all posts could be mailed out that have been created since the last cron job.

Iain.

Ah yes, I have suffered from that kind of misfortune too Though, as you said yourself, the reload was because of noscript.

jens said @ 2008-11-18 16:03:21:

You can add something like this:

<noscript><strong>For this page you need JavaScript.</strong><noscript>

This Text are only visible if JavaScript is off.

If you mean for your own site I guess something could be added where the lack of javascript is detected. Depending on the site permissions a statement could be added to the registration page, for example. The interface might get a bit cluttered if you felt compelled to warn about javascript usage (and maybe cookies too). Reading the noscript site it would seem that you get a javascript warning in your panel/taskbar already.

If you mean specifically for this site I am not the maintainer.

Regards,
Iain.

Posting/preview is created without a page reload - a good reason for having javascript to my mind. I don't use noscript but I believe it is possible to have a whitelist for trusted sites.

jens said @ 2008-11-18 14:57:42:

but there are not exist a <noscript> info

Not sure I understand this part of your question. Does noscript work by intercepting the HTML and enclosing any javascript with <noscript> tags?

Regards,
Iain.

Hello Tim,

Flatpages are a Django concept. read all about it here
http://docs.djangoproject.com/en/dev/ref/contrib/flatpages/

Regards,
Iain.

Easiest way to do it is to run the CommunityDraft example website which looks just like this one (minus the content ) You will be up and running in less than 10 minutes including the download!

Instructions are here http://sct.sphene.net/wiki/show/CommunityDraft/

Dive in the water is warm.

Iain.

Smart thinking Herbert

A javascript show/hide button where the text is included in the page (and therefore spidered) but doesn't clutter. Sounds good to me. Solves this problem, I think, and pretty neat feature for general use.

Tim: I understand the advantages of dpaste and the code formatting is nice. I quite frequently search using relevant sections of tracebacks yet I don't remember ever finding a paste bin in the results. Even when I sometimes only get 10 hits.

Iain.

Hello Tim,

just a (OT) thought...

I have used the SCT forum several times recently sometimes looking at posts going back 3-4 months. I understand the advantages of dpaste.com but the one big disadvantage is "This item will be deleted in 29 days"

I know that dpaste is commonly used by the Django community and that your post was probably short-term in nature, but, I think that it might reduce the value of the forum in the long-term.

I am not "having a go" specifically at you just raising it as a concern.

Iain.

I just looked at that bug you linked to and guess what

Affects Version/s: 3.2.10, 3.3.x

Here goes wsgi then... except...

Herbert Poul said @ 2008-10-20 21:26:03:

(the most annoying thing is, that the postgresql driver and a couple of other debian etch packages aren't compatible with python 2.5 so it's a real hassle to get it up and running )

The Etch package of libapache2-mod-wsgi only works with python2.4 too. I only use postgresql so I will need to look into this.

Herbert Poul said @ 2008-10-20 21:26:03:

well ... if you have the CommunityDraft in your PYTHON_PATH this would import all settings from the default community draft settings ..

OK got you now.

Herbert Poul said @ 2008-10-20 21:26:03:

i'm eager to see your site online i hope it will be public on the internet ?

It will certainly be online but I am not the site owner. Some fora will be private, and by invitation only, as the subject matter is about personal finance. That was why I was interested in https in another thread. I will certainly post to the forum when the site goes live (though that might be a wee bit longer than planned for - sorting through all the stuff above )

Thanks for the reply.

Herbert Poul said @ 2008-10-20 17:28:34:

i personally am using apache 2 with mod_wsgi - the reason is quite simple.. mod_python didn't work well together with the python xapian libraries (for the forum search functionality) - so if you need search you need mod_wsgi ...

The search facility is of interest. I saw the warning in the SCT docs for search however the server I was going to use (Debian Etch) is using mod_python 3.2 and thought I might be OK.

Herbert Poul said @ 2008-10-20 17:28:34:

another important thing to consider is.. if you have multi byte characters (ie. non-ascii characters) in the wiki you should use python2.5 otherwise the 'diff' between wiki snips will not work..

Oh! Like accented characters. Everything is currently on python2.4 bummer.

Herbert Poul said @ 2008-10-20 17:28:34:

well.. i would actually just symlink it into site-packages instead of moving it there.. (this way the sources and the static css & co could still be in one place)

Just to be clear are you suggesting something like

mkdir /home/iain/src
cd /home/iain/src
svn co http://..communitytools communitytools
svn co http://..communitydraft communitydraft
ln -s /u/l/p/site-packages/communitytools communitytools
ln -s /u/l/p/site-packages/communitydraft communitydraft

I can see that would make upgrading much easier. The different sites would still have different css, images and possibly templates.

Herbert Poul said @ 2008-10-20 17:28:34:

hmm.. yes.. sounds good.. are you also using the CommunityDraft project as a base ?

Yes.

Herbert Poul said @ 2008-10-20 17:28:34:

on my installation i have a simple dummy project which includes the CommunityDraft configuration in it's settings.py and then builds upon it:

from community.settings import *

I don't understand what you mean here.

Herbert Poul said @ 2008-10-20 17:28:34:

you mean you copied these statements like:
(r'^community/', include('sphene.community.urls'), defaultdict),

Yes.

Herbert Poul said @ 2008-10-20 17:28:34:

? i guess this makes sense.. another way would be to have CommunityDraft in your PYTHON_PATH and just include it like ..

from community.urlconfs import community_urls
urlpatterns = patterns( '', ... *patterns for your application* )
urlpatterns += community_urls.urlpatterns

(ie. just append the original urlconfs to yours) .. but i gues it doesn't really matter to ahve 1 line per SCT application you are using ..

Not every site would use every app so I thought it would be a good reminder of which site used which apps.

Herbert Poul said @ 2008-10-20 17:28:34:

let me know if i can help you in any way

Thanks

Sorry for being so verbose but I intend to write-up every step taken.

Thanks for the reply.

Herbert Poul said @ 2008-10-20 17:54:40:

hmm.. i'm not even sure why the content scrolls in the thread you've linked.

My mistake it is actually a line in the last post on that page (I have broken the line in two so as not to break this thread too )

ROOT_PATH/communitytools/sphenecoll/sphene/
<application>/templates/<path-provided-by-extend>

Herbert Poul said @ 2008-10-20 17:54:40:

i don't think limiting the width in the posts is a good idea.. you would need to limit a word length because in "normal" text the words are wrapped anyway .. so there wouldn't be scroll bars ?

I think URLs and some code can be the problem. There is also a correlation between available width and text size. A possible problem for people with sight issues, think WAI, and people with smaller devices, think PDA.

Herbert Poul said @ 2008-10-20 17:54:40:

maybe the best way would be really to have every post surrounded by a overflow:scroll div .. this way at least only one post is hard to read, instead of the whole thread..

I'll maybe think of moving the user information to the top, as well, to increase available width. This is not an issue limited to SCT I often see it with wikis and blogs.