Matias Griese

The stream is read-only because any content in plugins will be deleted on every plugin update.

Use `user-data://images`, because of `user` is also read-only :)

@kirillaristov Can you try to add extra option: `url_taxonomy_filters: false`?

Yes, it was just to confirm the issue to me. So basically you can do either/or, there's no way to filter the tree without removing parent items from the collection.

Yes, that's how it goes. It's a collection, not a nested sets with parent(s).

There is some javascript logic in the learn site for example, which displays all the pages matching to the content. I was just trying to think if there are any...

A collection isn't meant to do what you want -- it is just a flat list of objects which match the requirements. It is not meant to be anything else...

What about `/this/is/my/new/path`, it should redirect to `/some-different-path/is/my/new/path`

Instead of implementing the patch and breaking all redirects, you can do this instead: ```yaml redirects: '/this-is-my-url$': '/somepath' '/this-is-sparta$': '/some-other-path' '/this$': '/some-different-path' ```

Actually, `html()` and some other methods reset the image "by purpose". Also, the size of the image only changes only when the operations get applied. So the results are what...