5
I Use This!
Activity Not Available

News

Analyzed 2 months ago. based on code collected 6 months ago.
Posted almost 8 years ago
I have created a release, since it has been quite some time My goal is to make SCT compatible with django 1.4 (which it should be already). Once I'm convinced i probably rename the release to 1.0
Posted almost 8 years ago
I have started to migrate the subversion repository into a github account. In the process i am also trying to support django 1.4 The code is available at https://github.com/hpoul/sct-communitytools
Posted over 9 years ago
Because there were just too many spam posts lately I have (temporarily) disabled anonymous posts. I'm not yet sure why the captcha's are not effective any more, but I try to find other ways to prevent spam (akismet filter, post limits, etc.)Hey, we have Signatures !!! Great, isn't it ?
Posted about 10 years ago
SCT 0.6 has been released and contains many improvements to the django forum as well as many bugfixes and additional translations. Forum improvements include support for quick reply, moving of individual posts instead of the whole thread and nice ... [More] sluggified URLs for threads. See the Changelog for more details or grab this version from the Downloads section. [Less]
Posted about 10 years ago
SCT 0.6 has been released and contains many improvements to the django forum as well as many bugfixes and additional translations. Forum improvements include support for quick reply, moving of individual posts instead of the whole thread and nice ... [More] sluggified URLs for threads. See the Changelog for more details or grab this version from the Downloads section.Hey, we have Signatures !!! Great, isn't it ? [Less]
Posted about 10 years ago
Because of a hard drive failure i had to move the website and subversion repository. (This was the reason for the ~2 day down time ). Anyway, now everything should be up and running again - the subversion repository has moved to ... [More] http://source.sphene.net/svn/root/django/communitytools/ (although the old URL will simply do a 301 redirect, so if you checked out from the old URL, it is still valid). For committers: For those who had commit rights (ie. shell accounts) - i had no backup of those just mail me and i will recreate them.Hey, we have Signatures !!! Great, isn't it ? [Less]
Posted over 10 years ago
As promised I have prepared a SCT 0.6 release. Now it is time for testing and it would be nice if any of you could help me with that! Either download the release candidate or update to the latest trunk and test with your setup and django 1.1 or ... [More] later. (Or test by going through the basic Tutorial or the CommunityDraft installation). You might also try having your groupName in the URL - this requires the new setting: SPH_SETTINGS['community_groups_in_url'] = True (it is still not documented, I'm working on it ). For a list of changes check the Issue Tracker for now (I haven't had time yet to update the Changelog). [Less]
Posted over 10 years ago
As promised I have prepared a SCT 0.6 release. Now it is time for testing and it would be nice if any of you could help me with that! Either download the release candidate or update to the latest trunk and test with your setup and django 1.1 or ... [More] later. (Or test by going through the basic Tutorial or the CommunityDraft installation). You might also try having your groupName in the URL - this requires the new setting: SPH_SETTINGS['community_groups_in_url'] = True (it is still not documented, I'm working on it ). For a list of changes check the Issue Tracker for now (I haven't had time yet to update the Changelog). Hey, we have Signatures !!! Great, isn't it ? [Less]
Posted over 10 years ago
Lately i had a bit less time for SCT so development and response in the forum has slowed down a bit. But since reports are increasing about problems with setup and especially URL lookups, I plan to get a new release out ASAP, since it has been a ... [More] while since SCT 0.5 was released and there are already a couple of fixes in the trunk which should get out. So here is my plan: 0.6 - As soon as in 2 weeks: should contain all bugfixes and features in the current trunk (obviously) - the only thing left to do is stabilize everything (especially the new ability to have the groupName in the URL instead of the hostname. - it should be compatible with the latest django trunk and django 1.1 beta release (if there is a difference) - if people would test it against 1.0.2 - even better 0.9 - In 3-4 months: The most important thing for me right now is the WYSIWYG editor for the wiki and forum with features like image resizing, including of attachments, etc. It should also contain further stabilizing, cleanup (no dependency between the wiki and the forum) as well as easier installation and integration. (I still have to think about a way to convert an existing forum/wiki to a WYSIWYG forum/wiki - any ideas? ) 1.0 - Once the featureset of 0.9 has been proven to work, i will bump it to 1.0 In addition to this, the documentation has to be improved and adopted for the latest version. Please let me know what you think about this plan, what your current problems are when using SCT, and if you would be willing to contribute time and code. Either testing, writing documentation or providing code patches would significantly help me obviously (Even providing feedback helps to motivate me to invest more time into SCT) If you would be interested to help, but don't know how just leave a comment or write me an email.--- Last Edited by Herbert Poul at 2009-07-16 09:11:05 ---Hey, we have Signatures !!! Great, isn't it ? [Less]
Posted about 11 years ago
Thanks to the great work of lootgoal there is now a WYSIWYG editor for SCT forum posts! It is still deactivated by default, but i would appreciate testers and feedback! Feel free to test it out in the Sandbox forum! (Simply appending the GET parameter 'wysiwyg=1' enables it) Hey, we have Signatures !!! Great, isn't it ?