Timon

> Hi @timonf , please update the change log files too, and then we can merge this PR. Thanks. @viennt Below 1.5.8 section or as a new 1.5.9 section? I...

Hi @viennt! If you like, I could create a PR :)

@viennt Any status for the open PR?

After some research I [found](https://github.com/certificationy/certificationy/commit/0f81d5f8601e2f77c365c9f403126f85bdf82e71) `versions` already. But where they are gone?

What do you think, @mickaelandrieu? I already committed a prototype of version support :)

Thanks for your answer, @mickaelandrieu! I'm still **for** versions! Currently you are able to take the exam for Symfony 2.3, 3.0 or 4.0! And you have different requirements for each...

It worked for me using the following lines: `docker-compose.yml`: ```yaml cloud_server: environment: - OVERWRITEWEBROOT=/cloud ``` **and** `config.php`: ```php 'htaccess.RewriteBase' => '/cloud', ``` ...and running `docker-compose exec -uwww-data cloud_server php occ...

> It is a reasonable request. But since the pages are internal to your team, I am wondering how much effort is it to just periodically fetch the master pages...

Hi @viennt, I finally added changelog entries for plugin version 1.5.9 and changed the version in the `composer.json` file. I also move two entries to 1.5.9 that did not exist...

I guess it's very hard to implement, because the custom field detail form (`sw-custom-field-set-detail-base`) have to be aware of the `sas_blog_entries` entity. But the known entities are hardcoded at `custom-field.service.js`...