ezplatform | Meta repository that pulls in all dependencies | Content Management System library

Looks like you have executed the composer and symfony commands directly from your host and you have setup the project using launchpad.

Try this instead:

There are two types of filesystem caches in eZ Platform:

1) Persistence cache - caches the content loaded from the database. Size of this cache directly corelates with number of content you have. If you have hundreds of thousands of content objects, this can be the bottleneck.

2) HTTP cache - created by the Symfony reverse proxy (enabled with SetEnv SYMFONY_HTTP_CACHE 1 in your vhost). If you have a lots of logged in users or your anonymous users somehow create a session, or if the caching is misconfigured somehow, this can potentially be the cause, depending on the contents of your Vary response headers sent by the app.

In any case, none of these caches are cleared automatically, unfortunatelly. You will need to clear them by yourself.

We're using this matcher config and it works okay:

Thanks for calrification and telling more about your Use-Case.

you can use object-relations attribute for the purpose of image gallery and iterate over all related objects to that field and display them. your user should just relate image objects.

in that way the user can relate as many image object as he/she wants from Media Library.

Every time you add a siteaccess in eZ, you should update the anonymous role and add the corresponding user/login access policy to the new siteaccess. Also check that the anonymous role have appropriate policies for enabling access to read required contenttypes and section.

I guess that is not how it works!

the bundle generate just an empty yaml file for you and you should fill up the content types (or any other Backend Changes you want) yourself in that yaml file and then take it and apply to your stage or Live Environment.

so unlike Symfony DoctorineMigrationBunlde, this bundle does not read the difference and produce stuff itself.

Have a look to our CjwPublishToolsBundle. https://github.com/cjw-network/CjwPublishToolsBundle https://github.com/cjw-network/CjwPublishToolsBundle/blob/master/Services/TwigConfigFunctionsService.php

Here we have 2 wrapper twig functions

You don't have to create a controller for each Content Type. What you want, if I may, is to inject data into the view.

Using a custom controller is one of the options, for generic stuff that you want to inject you can also use https://doc.ez.no/display/DEVELOPER/Injecting+parameters+in+content+views

We have bundled this concept (among other here: https://github.com/Novactive/NovaeZExtraBundle) with a concept of ChildrenProvider.

Also, you mentioned you wanted to inject information related to the header and the footer in the view to get them in the layout. It sounds weird. With eZ but also just with Symfony you can render a controller from a view, them you can render the header and render the footer independently from the view. (that is probably what you should do)

For the children though, I like to use the listener instead of the custom controller. It is managed in the Novactive bundle but be careful if you do it on your own, the pre_content_view listener will trigger on each view (line, full, etc..) And usually, you want to inject stuff in the view full only.

The distribution bundle required in the root composer.json must be updated. On the 5.4.x update instructions page for eZ Platform, you will see for version 5.4.2 that it must be bumped to ~3.0.

Running the composer require command from this chapter may therefore fix your error, but it is hard to be 100% sure. Let me know.