Vanilla Forums Documentation | Theme Boilerplatehttps://docs.vanillaforums.com/developer/theme-boilerplate/
Vanilla Forums, create an online community that your customers will love
Vanilla 2.8.1 contains multiple security and bug fixes. Please upgrade immediately.
If you are upgrading from a release prior to 2.8, read the 2.8 release notes first and follow those steps to upgrade. If you were not aware of the additional upgrade step (clearing the
/dist folder and additional files from 2.6, please be sure to do all of the steps with this update.)
A few notes to repeat from the last release notes:
Release notes follow.
7 medium-severity security issues were patched. Details are included below, but the linked issues with their details are currently still private. It is recommend to upgrade immediately.
NewFlyoutsfeature flag not directly tied to the theme being enabled.
ThemeHooksremoved. No longer necessary.
Previously these post formats were being sent out "raw" in notifications & emails. This looked particularly bad for the Rich format.
First a couple notes:
Without further ado.
Rich Editor is now the default editor for Vanilla.
The Rich Text Editor features a number of significant upgrades:
Vanilla 2.8 ships with a new, fully responsive theme
Keystone ships as the default desktop and mobile themes on new installations and can be enabled on existing installations through the themes page.
Theme Options Keystone ships with 6 preset theme options. Covering a different variety of stylistic choices and colour palettes.
settings/swaggerin your site to see API documentation accurate to the addons currently installed.
This is a rather minor fix on our end, but it may have an impact on your set up if you are using API V2 anywhere on your side and you have a call set up with a limit parameter set higher than 100.
This has always been our suggested limit; however, we were not properly validating that limit parameter. This meant that you could use an API call with a higher limit parameter, and your calls would be successful. The call would only start to return errors once the community had grown to a point where these API calls they set up would then start pulling so may records that it would exacerbate the API and return an error with little to no helpful information.
Vanilla has implemented proper validation of the parameter so that we can return a valid error explaining that the limit should be lower than 100.
Vanilla is transitioning away from the use of global functions. They are being slowly phased out in each release. If you are an addon developer it is recommended that you update your usages of these methods.
With 2.8 the following functions are deprecated and will be removed in a future release:
Most notable of these is
val which had over 5000+ usages removed from vanilla since the last release.
The following events have been deprecated and will be removed in a future release.
categoryModel_categoryWatch- Category watching has been replace with category following. See the
Over the past few weeks I've been working on this new theme. I solicited the community's feedback, and am finally deploying it today.
It's based off of 2.8's new default theme
I originally asked for feedback over at
Even though theme is deployed improvements can still be made. Feel free to leave suggestions.
If you're looking to make a similar Vanilla theme, our
@vanillaforums/theme-boilerplate package is the perfect place to get started. It starts you off with some good defaults and a large variable sheet to start modifying. It also makes it easy to add extra custom CSS on top and bundle it all together using our build tool.
See our documentation for details.
Discussion Extender 1.2
This version Upgraded to work with vanilla version 2.8
Do not forget to delete " cache " before use it .
Sorry my English is bad.
my users keep asking me about the above features. "Mark all read" seems to have disappeared entirely, whereas quoting has become quite cumbersome and inconvenient, especially when threads with arguments on religious and political issues grow exponentially in size with every new post.
I'm aware of the workaround.
Now for a post with short to medium length that works okay. But a long post, to which three or four people have already contributed, building the above structure becomes a bit complicated, whereas before it was possible to just quote the entire post, just write in between the lines, and the quotes wold be attributed the the appropriate user automatically.
>> @user1 said:
>> quote 1
> @user2 said:
> quote 2
user3's response goes here
Bottom line: inline quotes are a feature greatly missed in the otherwise quite awesome new editor