* Add appyveyor config
This commit does add settings for using mssql on appveyor
but there are still some issues with timeouts. For now only
the sqlite build is enabled.
Note that the build currently (correctly) fails on windows
* Fix unittests on Windows (in wagtaildocs)
The document.file.name attribute doesn't contain a valid path separator
on windows. Use document.file.path for comparison instead.
* Created Elasticsearch 2 backend
* Added tests for Elasticsearch 2 backend
* Split models up into different indices
pages, images and documents are now in separate indices
* Prefix fields of child models to prevent mapping clashes
* Replaced index_analyzer with analyzer/search_analyzer
index_analyzer has been removed in Elasticsearch 2.0
https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking_20_mapping_changes.html#_analyzer_mappings
There's no indication in Elasticsearch's docs that this wouldn't work on Elasticsearch 1.x. However, we found that the new configuration isn't reliable on Elasticsearch 1.6 and below (causes the test_query_analyzer test to fail randomly).
* Implemented new way of representing content types in search index
Instead of using a long string of model names that is queried using a
"prefix" query, we instead use a multi-value string field and query it
using a simple "match" query.
The only reason why this isn't implemented in the Elasticsearch 1.x
backend yet is backwards compatibility
* Added another child model of SearchTest with clashing field mapping
This checks that the namespacing of fields on child models is working properly (if it doesn't the update_index tests will fail)
* Added tests for get_model_root function
* fixup! Added tests for get_model_root function
* Docs updates for Elasticsearch 2 support
Also tweak examples to use elasticsearch2 backend by default
* Test against Elasticsearch 2 on travis
The admin extensions in django treebeard 3.0 are not compatible with
Django 1.9. Although these are not used by Wagtail they are used in
other projects (e.g. Oscar), so we should allow treebeard 4.0 which
is compatible with Django 1.9.
All referencs to `six` were removed in #1411 favouring
`django.utils.six`, except for one in `tox.ini` where it was installed
as a dependency. Because it was still installed in the test environment,
a few references to `six` crept back in. These will cause an ImportError
when users do not have `six` installed.
These references have been fixed, and `six` has been removed from
`tox.ini`
Depending on libsass for all Wagtail installations was causing issues
with various operating systems, dramatically increasing installation
times, and preventing front end development adopting modern practices.
libsass has been removed as a dependency. Sass files are compiled before
release as a dependency of the `sdist` setup command. Sass compilation
is done through `gulp`. People wishing to hack on the frontend assets
should now install wagtail locally, install the node dependencies, and
run `gulp`:
$ pip install -e path/to/wagtail
$ cd path/to/wagtail
$ npm install
$ npm start
All the templates and JS files have been updated to reference the new
compiled CSS files instead of the Sass files.
Precompiled CSS for jquery-ui and similar have been moved out of the
`scss/` directory to the `css/` directory.
Karl Hobley