kirrg001 1a79aac673 Fixed collection ownership if a published post status changes to featured ... refs #9601 - implementation of resource listener updated - if you define two collections: `featured:true` (1) and `page:false` (2) you can run into the following bug: - you create a published post (owned by (2)) - you change the status to featured - still owned by (2), because the filter still matches (it's still not a static page) - this adaption fixes the behaviour - less smart logic, but less error prone		2018-06-17 10:41:05 +02:00
..
api	✨Dynamic Routing Beta (#9596)	2018-06-05 19:02:20 +02:00
data/importer/importers	🐛 Fixed unable to publish a post after slack hook import	2018-06-11 11:08:08 +02:00
helpers	Removed knex mock (#9685)	2018-06-12 20:26:16 +02:00
model	✨Dynamic Routing Beta (#9596)	2018-06-05 19:02:20 +02:00
services/url	Fixed collection ownership if a published post status changes to featured	2018-06-17 10:41:05 +02:00
web	Protected error if routes.yaml file doesn't contain any collections	2018-06-13 21:01:05 +02:00
export_spec.js	Moved ghost-version to lib	2017-12-14 22:14:55 +01:00
migration_spec.js	Sorted out the mixed usages of include and withRelated (#9425)	2018-02-15 10:53:53 +01:00
update_check_spec.js	Use Bookshelf in our test env (#9592)	2018-04-25 17:13:35 +02:00