Schedule
- Staging: Tuesday, February 23rd
- Production: Monday, March 1st
- Enterprise Clients: Monday, March 8th
OAuth 2 Updates
This release introduces multi-connection support for OAuth2, allowing you to connect multiple identity providers to your Vanilla forum. This has also brought some updates to our OAuth2 settings UI to allow you to more easily configure and manage your connection.
Edit Custom Profile Fields via API
Release 2021.001 included an update allowing you to fetch custom profile information via API. Release 2021.004 introduces the ability to edit these fields using a new /users/{id}/extended endpoint for PATCH actions.
New Zapier Templates
Over the last few weeks we have published a few new Zapier templates to help you and your teams get started with our integration. Our newest templates include:
- Add new Vanilla users to your Hubspot contacts
- Create Github issues when new discussions are posted in Vanilla
If these templates don't speak to you, not to worry, we've got more on the way. You can also explore our available triggers & actions on Zapier to start creating your own. We've got a community post going on the subject. You can get some ideas here, or share your use cases to help us plan out future updates.
Check out our Zapier page for more details on our integration, templates and all available triggrs & actions
Theming Changes
This release included numerous improvements to the foundation theming engine. Here are the highlights:
User Card Layout Improvements
The initial implementation of user cards was problematic because it significantly modified the HTML element that would trigger the user card. This also wasn't something that theme's could accommodate easily because even in the same theme the HTML could be quite different between someone with permission to view user profiles (and had user cards) and someone who did not.
In this release, user cards no longer modify the HMTL of the trigger they appear from. From a theming compatibility standpoint the most notable difference here is that if you were targeting the .userCardWrapper-link
or .userCardWrapper-photo
classes, they no longer exist. We've remove that extra wrapper that had been appearing.
If you did have CSS targeting this selector, your theme likely had layout issues for users that did not have permission to see user cards.
Consistency in Metas and Tags
We've significantly improved the layout and styles for the meta items on categories, discussions, and comments in this release.
- Spacing between meta items is now consistent.
- Tags and labels now have the same height as other meta items.
- Links are now clearly distinguished from items that are not links. By default this is done by applying a semi-bold font-weight on the links.
- A bunch of new variables for styling meta items are now available. These will make it significantly easier to uniformly style your meta items.
New Variables
This release brings more more than 200 new variables for theming.
The variable documentation reference will be updated on the day of the release.
- These are variables for an upcoming widget for future releases. They may change before the widget is made publicly available.
list.*
- These variables affect various list items throughout vanilla. These should be the starting point before going into specific lists like discussionList.*
or categoryList.*
variables. Note, as of the this release these are not universally applied, but will be a future release.metas.*
- Style meta items in lists and other locations. (This supplants the previously inconsistently applied global.meta.*
variables).breadcrumbs.*
- Adjust breadcrumb styles.global.links.linkDecorationType
- Setting this to always
(as opposed to the default of auto
) will cause various links in the application to have an underline.global.panelBoxes.*
- Apply box variables of 3 depths to the panel. We've applied these to some of our most common panel widgets and more will respect these variables in future releases.global.panelHeadingBox.*
- Adjust spacing of box headings in the panel.
Bug Fixes