This means it is no longer possible to simply clone the repo into a web directory and run Vanilla. In developer parlance, the source code and the runtime code have diverged. Now to build Vanilla's runtime code, you must install Composer. This is only necessary if you are running a non-official version directly from GitHub - the releases on this site will continue to work normally because we will be pre-building those for you (using Phing, if you're interested).
As Vanilla's frontend becomes more complex it began to use frontend dependencies through
bower, then through
Recently a change was merged to
master that removed the compiled/pre-build frontend assets from git. Instead they must be built after cloning the repo. This build has been added as post-install step for composer, so assuming you have the right dependencies, a
composer install is all that you should need to get it working.
Building Vanilla's frontend has additional dependencies beyond PHP and composer. See our build tooling documentation for details.
How does this affect my usage of Vanilla
The affect of these changes will depend on how you install Vanilla.
I use the pre-built version of Vanilla
I use Vanilla cloned from the github repo
See our build tooling documentation for details. The dependencies here are required. Once they are installed running
composer install will ensure that all frontend dependencies are also installed and that all frontend assets are built.
2.7 release branch has forked and we've started using it on cloud. I expect the open source official release will be along shortly. The marquee feature is a brand new text editor with a new interface designed from the ground up. It's available as an addon, so you can move to it when you're ready, regardless of when you upgrade core. I should also note that file uploads in it are currently restricted to images, so you may not be quite ready to switch if your site does a lot of file swapping via comments.
Full release notes will accompany the actual release.
Instead use the longer form
Something which might not been known, but has been said long before: avoiding
val() is a good idea, too. Not because it will be deprecated (soon :shrug:), but simply because it is not needed oftentimes. If you now the type of the variable simply use the correct code to get the arrays element/objects property. Right now
val() is purged out of Vanilla from all the places where it is possible:
By the way: I don't know such things because someone tells me, I simply follow what's going on on the GitHub repo. If you want to stay up to date, I recommend watching the repo