Vanilla is a powerfully simple discussion forum you can easily customize to make as unique as your community.
Switch branches/tags
Clone or download
slafleche Merge pull request #7940 from vanilla/fix/editor-layout-spacing
Editor Form - Spacing adjustments (KB)
Latest commit 6ad8ebc Oct 18, 2018
Permalink
Failed to load latest commit information.
.github/ISSUE_TEMPLATE Add first issue template Oct 2, 2018
applications Added rich editor form styles Oct 16, 2018
build Update crud redux to return response Sep 26, 2018
cache undelete cache/.htaccess May 1, 2018
conf Update additional license declarations Sep 12, 2018
js Remove stripping index.php in embed.js. Sep 24, 2018
library Reset input text size Oct 18, 2018
locales Remove execute permissions on all files (chmod -x) Jun 4, 2015
plugins Set editor form input to be same size as post Oct 17, 2018
resources Allow react components to mount on pages Mar 27, 2018
tests Fix tests Oct 16, 2018
themes Update additional license declarations Sep 12, 2018
uploads Remove execute permissions on all files (chmod -x) Jun 4, 2015
.browserslistrc Implement building and dispatching of knowledge controller Aug 27, 2018
.editorconfig Test tweaked build matrix Sep 12, 2018
.gitattributes Implement building and dispatching of knowledge controller Aug 27, 2018
.gitignore Merge master Sep 19, 2018
.htaccess.dist Fix htaccess to work correctly with subdirectory Jan 8, 2018
.npmrc Add npmrc May 28, 2018
.travis.yml Merge master Sep 12, 2018
CODE_OF_CONDUCT.md Add code of conduct, per GitHub suggestion Oct 2, 2018
CONTRIBUTING.md Fix typo Oct 9, 2018
LICENSE.md Remove execute permissions on all files (chmod -x) Jun 4, 2015
PULL_REQUEST_TEMPLATE.md Add a PR template Oct 2, 2018
README.md Remove 'Contributing' from README. Oct 2, 2018
bootstrap.php Update additional license declarations Sep 12, 2018
composer.json Merge master Sep 17, 2018
composer.lock vanilla/garden-password update to composer.lock file Sep 17, 2018
container.html Drop attribute "type" for style tags Nov 16, 2016
environment.php Merge pull request #7786 from vanilla/feature/alias-autoload Sep 20, 2018
index.php Update additional license declarations Sep 12, 2018
package.json Bump tslint-config version Oct 15, 2018
phpunit.xml.dist Remove rogue text from phpunit.xml.dist Oct 25, 2017
prettier.config.js Fix prettier config May 28, 2018
tsconfig.json Update javascript test setup Sep 13, 2018
tslint.json Fix broken tslint config Jun 7, 2018
yarn.lock Bump tslint-config version Oct 15, 2018

README.md

Vanilla uses Composer and NPM! You cannot clone this repo right into a web directory - it requires a build step. Learn more or just download the latest stable build instead.

Vanilla

Howdy, Stranger!

Vanilla was born out of the desire to create flexible, customizable, and downright entertaining community solutions. Vanilla has been used to power tens of thousands of community forums around the world and we couldn't be happier if you've decided to use Vanilla to grow yours.

Every community is unique. Vanilla is a finely-crafted platform on which designers and developers can build a custom-tailored environment that meets your community's particular needs.

5 reasons Vanilla is the sweetest forum

  1. We've reimagined traditional forums for mass-appeal.
  2. Our theming flexibility is second-to-none.
  3. Impossibly good integration options with single sign-ons and embedding.
  4. The best tools available for community management.
  5. Curated features with great plugin options, not the kitchen sink.

Open Source

Vanilla is free, open source software distributed under the GNU GPL2. We accept and encourage contributions from our community and sometimes give hugs in return. You can join us on the Vanilla Community Forums to be part of that discussion.

The latest stable release is always listed here. Currently, it is the release/2.5 branch.

New plugins and themes can be listed in the Official Addon Directory. We encourage addon developers to release their code under the GPL as well, but do not require it.

Cloud Solution

Vanilla Forums provides an official cloud hosting solution at vanillaforums.com with a 1-click install, automatic upgrades, amazing professional support, incredible scalability, integration assistance, theming and migration services, and exclusive features. For the very best Vanilla forum experience, you can skip the rest of this technical stuff and go there directly.

If you professionally run a large community or enterprise forum, our cloud solution will make the best technical and economic sense by far.

Self-Hosting Requirements

We strongly recommend:

  • PHP 7.1 or higher.
  • MySQL 5.6 or higher (or Percona/MariaDB equivalent).

If your server is not running PHP 7.1 or higher, you should address this soon. While PHP 7.0 will receive security patches until December 2018, Vanilla may end support for it prior to that.

Our minimum requirements are now:

  • PHP 7.0 or newer.
  • PHP extensions mbstring (--enable-mbstring), cURL (--with-curl), and PDO (on by default).
  • To import into Vanilla you need MySQLi (--with-mysqli).
  • To use our social plugins you need OpenSSL.
  • MySQL 5.0 or newer (or Percona/MariaDB equivalent).
  • MySQL strict mode disabled.

Vanilla ships with a .htaccess file required for Apache support. Using nginx or IIS may require additional configuration.

On the client side, Vanilla should run & look good in just about any modern browser. Still using IE? How exotic. You'll want IE11 or greater. IE8 might work if you squint hard and click gently, but we make no promises.

We've been natively mobile since before it was cool. Vanilla ships with a mobile-optimized theme enabled by default for all smartphones & tablets. Heck, it even works on the PlayStation Vita.

Installation

Vanilla is built to be simple, and its installation is no exception.

  1. Upload Vanilla's pre-built version to your server.
  2. Using nginx? See our nginx guide.
  3. Confirm the cache, conf, and uploads folders are writable by PHP.
  4. Navigate to the folder where you uploaded Vanilla in your web browser.
  5. Follow the instructions on screen.

If you run into a problem, see Getting Help below.

Upgrading

Follow these steps to upgrade Vanilla when a new stable release is announced. These instructions assume you're using SFTP to manually copy files to a server.

Please consider using maintenance mode before running database updates if your database is very large (millions of users or comments).

  1. Backup your database, .htaccess and conf/config.php file somewhere safe.
  2. Upload the new release's files so they overwrite the old ones.
  3. Delete all files in /cache (except .htaccess if you use Apache).
  4. Follow all version-specific instructions below. It is critcal you delete the listed files.
  5. Go to example.com/utility/update to run any database updates needed. (404? See next paragraph.) If it fails, try it a second time by refreshing the page.

If you run into a problem, see Getting Help below.

From Vanilla 2.5 or earlier:

  • Delete plugins/HtmLawed. (This is now in core.)
  • Delete plugins/Tagging. (This is now in core.)

From Vanilla 2.3 or earlier:

  • Delete /applications/vanilla/controllers/class.settingscontroller.php.

If your forum still uses URLs including ?p=, support for this URL structure has ended. Follow these steps to switch to the simpler format:

  1. Confirm your server is setup to handle rewrites. On Apache, using the .htaccess file provided will accomplish this. Additional setup is required on nginx and other platforms.
  2. Test whether it is working by visiting /discussions - if you see a discussions list (rather than a 404), it is likely setup correctly.
  3. Open /conf/config.php and find the line with $Configuration['Garden']['RewriteUrls'] = false; and delete the entire line.

Your site should immediately switch to "pretty" URL paths instead of using the 'p' parameter. If there is a problem, re-add the line to your config and do further troubleshooting.

From Vanilla 2.1 or earlier:

  • Update ALL locales you have installed (in /locales).
  • Apache users must update their .htaccess file.
  • Delete /themes/mobile/views/discussions/helper_functions.php
  • Delete /applications/dashboard/views/default.master.php

From Vanilla 1.0:

Upgrading from 1.0 (any version) requires a full migration (see next section). Themes and plugins are not compatible. Backup your Vanilla 1 data and files completely, then delete them from your server before attempting to install Vanilla 2.

Migrating to Vanilla

  1. Get Vanilla Porter and verify it supports your platform.
  2. Read the Advanced Uses notes on that page.
  3. Upload it to your current server.
  4. Navigate to the file in your web browser & run it.
  5. Take the file it produces and import it to Vanilla via the Dashboard's "Import" option.

If you run into a problem, see Getting Help below.

Using Maintenance Mode

You can temporarily halt all access to your forum by putting it into maintenance mode. Users currently signed in with owner privileges (the user who created the forum) will still be able to use the site.

To put your site in maintenance mode, add this to /conf/config.php and save it:

$Configuration['Garden']['UpdateMode'] = true;

To end maintenance mode, delete it and save.

Getting Help

Building with Phing

Vanilla includes a buildfile for Phing, a build system for PHP, in the build directory. Running the phing command from the build directory will create a deploy-ready copy of Vanilla. This process automatically fetches dependencies with Composer, filters out any unnecessary developer files (Git files/directories, .editorconfig, unit tests, etc.) and compresses the result into an archive.

The phing build requires NodeJS and yarn to build frontend assets for packaging. See build tool documentation for installation instructions.

Version Control Strategy

We've adopted the git flow branching model in our projects. The creators of git flow released a short intro video to explain the model.

The master branch is production-ready for our cloud product but is not yet vetted for open source release (alternate platforms & configurations). Reviewed, stable changes land against master via pull-request.

Our open source release branches are named by version number, e.g. release/2.5. We begin release branches with a beta (b1) designation and progress them thru release candidate to stable. All open source releases (included pre-releases) are tagged.

Reporting Security Issues

Please disclose security issues responsibly by emailing support@vanillaforums.com with a full description. We'll work on releasing an updated version as quickly as possible. Please do not email non-security issues; use the issue tracker instead.

Legal Stuff

Copyright © 2009-2018 Vanilla Forums Inc.

Vanilla Forums is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 2 of the License, or (at your option) any later version. Vanilla Forums is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with Vanilla Forums. If not, see http://www.gnu.org/licenses/. Contact Vanilla Forums Inc. at support [at] vanillaforums [dot] com

Bonk!

Just kidding, everything's awesome. dance