Vanilla 1.2 is going to be a great, significant release. There will be plenty of new features, many of which will be included as new extensions, allowing them to be easily disabled and enabled easily.
Some new features are:
About 1. from @Tudor. I've got a small update of the extension by Jazzman, to add a counter of download. I can provide it so you can enhance it for vanilla 1.2 if you like.
Because it was done when I had absolutely no knowledge of php (not that it had greatly improved since :)).
About extensions for 1.2, I'd say:
Attachments
Quoting
Comments permalinks
Account Pictures
More prepkg'd extensions would be nice. But I would prefer more work being done to finalize and refine the codebase. I would also like pagelist and sqlbuilder components to be more robust, as in ability for sqlbuilder to do nested selects, and for pagelist to be able to exist multiple times on one page. I would also like to see an established method for creating custom root .php pages, and a basic set of base classes to build extensions from, like manager/model classes and controls. The lack of standards with a lot of extensions is really alarming. AJAX support for extensions is also something that would be very beneficial for everyone. These base components are not hard to DIY, but it makes more sense to have a standard set. Most importantly, the documentation in the dokuwiki must expand to cover more than the 30% of Vanilla that it currently covers. I think for Vanilla 1 to keep going these issues must be addressed. Other than that, Vanilla 1 has been a mature product that is mostly very easy to work off of. Speaking of minify, has there been/will there be any solutions for caching the sql results?
Attachments, Inline Images, Quoting, comment permalinking, Category Permissions.
Also, a robust WYSIWYG editor to work well with HTML Formatter - this doesn't exist yet AFAIK.
Does the Minify extension have anything to do with http://code.google.com/p/minify/ ?
@Stash Yes, it is exactly that. There are some very cool improvements coming for Minify as well, the best of which is it will read the CSS/JS files straight from the HTTPd, which gets around the PHP overhead, making the file serving roughly 10x faster
@glow Vanilla 1 and Vanilla 2 are very different, and some people might prefer to continue using Vanilla 1 instead of changing to Vanilla 2. Vanilla 2 isn't a replacement for Vanilla 1, it is just different. They will be developed alongside eachother.
These extensions I think should be considered to be packaged, although I'm not sure which of these are stable enough to be considered to be added. Also, some of these have been requested.
• User Fields + Account Pictures
• TagThis
• Page Manager
In addition I think it would be great if users could carry multiple roles. This I think would be able to grant a lot more flexibility, not really sure how it would slam the database though. As opposed to a hierarchy like unauth, member, mod, admin from least power to most power it's more like a bunch of skill sets. More of a symbiosis, which I think helps drive a community.
^^^ yes. standards, please.
We will add any add-on (including themes ad styles) that is stable (doesn't need major changes) and maintained enough. It can be maintained by someone else than the original author as long as he understand the extension and can test it with the current version of Vanilla 1 in the repository trunk.
So far only Klaus (aka Subjunk) has added some extensions (Notifi, Whisperfi and Sirnot's HtmlFormatter).
I can't believe I forgot this, but for the love of god, PLEASE include Set List in the Vanilla 1.2 release. If this is in the core then plugin developers will start using it more often and we'll get generally better options for plugins!
-
1. Attachments (needs some stability work - I'll be working on this soon.)
2. Notifi (and RSS)
3. Category permissions
4. Comment formatting buttons (html pref) and HTML Formatter
5. Polls (needs some work)
6. Quoting
While I think this is a really cool idea - I'm a bit worried of inclusion of extensions into the core. I've had to fix several small bugs and deal with quirky functionality in many of the extensions I've used. I'd be more in favor of some kind of top-10 list. The community would get direction as to which extensions are the most popular without sacrificing the stability of the core forum.
@sonofanickel: what kind of work on attachments?
I've been using it for years without issue.
@bean I added a post to the Attachments extension page explaining. http://www.vanillaforums.org/addon/153/attachments/150/50/ (at the bottom).
Why this focus on another version of 1 when 2 is in beta? Shouldn't this effort be directed at it?
i agree, feature freeze 1 and work on 2
update: it looks like V2 will be vanilla with garden included.. so vanilla forums "no matter the version" will continue dev as is.. i think
hopefully some clarification from the naming of garden/vanilla will come from the other thread to clear things up.
@Tudor: I don't think it will be long until it is released officially, we just have a couple more things to do. You can always just get the latest build from the repository and see if you like it, since that is ~90% of 1.2, if you don't like the latest SVN build you won't like 1.2 :)
Or you can use 1.1.10 in the meantime, it will be an easy upgrade to 1.2 from that.
Just depends if you feel adventurous for a non-official build or not :)
So far, there are only Squirrel and Subjunk who volunteered to include theirs or others' extension to Vanilla. Here is the list:
http://lussumo-vanilla.googlecode.com/svn/trunk/src/extensions/
Crazy thought, but since this is a pretty major release for Vanilla 1, how about simplyfying the terminology and renaming "Extensions" and all references to it (including the directory structure) to "plugins" in order to match the addons site?
It would possibly help prevent people getting confused...
Assuming I get more feedback and widespread testing on it, I wouldn't mind ImageResizer to be included. Though it looks like HtmlFormatter does a similar thing with a few less features.
Permissions for categories so that you can, for example, have an Announcements category in which only Admin can create new discussions and members may only read and comment. This is a showstopper for me at the moment. I've tried CategoryRoles but it doesn't stop discussions being moved into "Admin only" categories.
@SubJunk I didn't know that. Still, I stand by my suggestion that it would be a good idea to change it - afterall, my link to the conversation pretty much was a complaint ;)
I guess the reason to not do it is it would be a lot of work checking it doesn't break stuff and asking for translations to be updated?
It looks like you're new here. If you want to get involved, click one of these buttons!