Most changes are bug fixes with the exception of allowing users to create and delete (soft) their own disc apps. Oh also if you're attempting to access an admin page and are not logged in, you will be given a second login box to enter the admin password for the disc app. This account is auto created at disc app creation with the password the user picks. It has access only to view forums and the related admin page. You cannot post any messages with these accounts.
Changes in this version:
* Password reset should not display if request creation was successful to user. bug needed
* Set User Model's Info/Error Message Property Correctly. bug
* Move account application config to it's own page. enhancement
* Imports still not working! bug spike
* Login Email Input Form Element should be of type "email" instead of "text". bug
* Redirect Url Cookie needs to be redone bug
* Add admin password for disc app maintenance. enhancement needed
* Allow Users To Delete Disc Apps enhancement
* Allow users to create multiple Disc Apps. enhancement nice to have
* Set Cache Duration At Application Start From Configuration enhancement needed
* Link Text on Maintenance Page Doesn't Show Full URL bug
* Implement limitation on posts per second. enhancement
I have a to-do ticket in GitHub to replace all image assets copied from the original site to change them to my own. All code is me though.
Dunno if you know, but it's a whole clone of the disc app service, not just this board. The admin site and everything.
You can check out the other test boa... more
I currently have it in the next release. It might get pushed out as I have a lot of original features to implement before the end of the month.
Link to bug ticket: https://github.com/shamrice/discapp/issues/133
Still haven't gotten to #133. :)
It probably also helps that I'm the only one creating and reporting tickets besides #133 so far.
We'll see what happens if that other forum jumps on but you're right, it's really not that bad considering this is from scratch started in July.
I guess it can't be too terrible seeing that it seems to be pretty stable but there are some real programming horrors in the recursive functions that traverse the thread trees to generate the HTML. (Which still manage to render surprising quickly)