thanks for the patch - sorry i have not replied earlier. i have been quite busy
i'm wondering - since all i do is basically checking roughly through the patches to see if they make sense and fit into SCT and then commit your patches.. how about i also give you commit rights? i can watch the SVN history anyway.. maybe you could mail me.
i appreciate your effort to contribute back very much, sorry it takes a while for me to commit the patches

i think it would be cool to have this whole string as configuration setting . or at least the attributes of the tag..
because i could imagine that some message board want to open links in new windows, while others don't.. and again others might want to add a rel="nofollow"..

--- Last Edited by Herbert Poul at 2010-02-01 11:50:14 ---

that would be a really cool feature to have in the profile.. although i'm not sure if it's better to use signals to embed it right into it, or just create a second view?

hi,
thanks for using SCT - you are right with the template error - it is a bug since the templates in the community applications must not extend the template of the sphboard app. i have committed a fix into the trunk version in subversion of SCT.

as for the second error - maybe you could post a stacktrace along with the error? it seems like the 'example' group has been added a second time.. whyever this happened.. you could try simply deleting it by hand from the database (try a select * from community_group; - if you see two 'example' groups you can try to delete the one which was created later.. hopefully nothing has a reference to it)

ah ok .. just read haystack is just an abstraction over other search engines.. that makes sense.. maybe it would be worth changing the current djapian specific implementation to haystack.. although it then has another dependency .. well i'll take a look, if it doesn't make things more complicated it would be a good idea to not depend on a specific search engine.

hi,
well.. i only briefly evaluated search engines before using djapian - do you know the advantages of haystack?
since the components handling search are external anyway.. i guess it doesn't really matter, you can always create search applications using another search engine let me know if you do so.. maybe i can add it to SCT (almost certainly if it doesn't destroy the current search )

thanks for giving sct a try, let me know how your evaluation goes and if you need any further assistance

yep, wiki snips are recursive.. which means if you have a snip called 'Documentation' and assign permissions to it .. they also apply to 'Documentation/Tutorial' for example.. (only if Documentation/Tutorial has no permissions on it's own). there is also a "special snip" you can create which will be used as the root permission when no others apply - simply call a snip called 'ROOT' and assign permissions to it.

great.. let me know how it goes and if you need any further help

hi,
that shouldn't be a problem.. SCT completely relies on the django User object and authentication .. so simply create and use your own registration view.

oh.. that could be a problem.. you should definitively use at least django 1.0
you could try SCT 0.3 or SCT 0.4 and enable backward compatibility in the settings.py:

SPH_SETTINGS = {
    'django096compatibility': True,
}

maybe you are lucky.. but unfortunately i can't remember.. let me know if you really try it out..