The 16.02 (v1.2.0) release of eZ Studio is available as of March 3rd, and includes all features and improvements of 15.12.1 from February 5th.
For the release notes of the corresponding (and included) eZ Platform release, see eZ Platform 16.02 Release notes. |
Download:
As Customer with eZ Enterprise subscription: https://support.ez.no/Downloads (BUL License)
As Partner with Test & Trial software access: https://support.ez.no/Downloads (TTL License)
If none of the above, request a demo instance: http://ez.no/Forms/HTML-forms/Discover-eZ-Studio
When you are selected as a reviewer for a Content item, you receive a notification about it by email. The message contains a direct link to the draft.
As a reviewer you also receive notifications in your user profile. When you are logged in, a number appears next to your profile picture (in the top right corner of the screen) which shows how many requests for review you have received.
Click your profile and choose View notifications. You can see a Notifications window with a list of all requests:
|
|
|
For known issues head over to our known enablement issues page that covers eZ Platform and eZ Studio.
However here are two issues that were uncovered very late in the release process since they were hidden by other bugs that we would like to make you especially aware of:
Both are currently being worked on and will be fixed in patch version in the next couple of weeks.
eZStudioDemoBundle is a showcase of eZ Studio. It should not serve as a base for projects. A clean installer of Studio is on its way.
In the meantime, you can overwrite the bundle in two ways:
1. Due to Symfony2 loading mechanism, bundles are loaded last and have the highest priority, so you can place your app in a bundle and load it last in AppKernel.php. Then every Studio Demo configuration will be overwritten.
2. Disable the eZStudioDemoBundle from AppKernel.php, then only your configuration will remain. This solution generates extra work, you have to take care of content existing in Studio Demo and every template used in it (location views, block templates, page design, etc.). You can always remove all the content in Home root, then disable the Demo Bundle and you should encounter no exceptions.
In version 16.04 we will provide a clean installer without demo content and with generic landing page block templates, where you can create your design and place configuration wherever you want.
You can easily upgrade your existing Studio project in version 15.12.1 (1.1.0) using Composer.
Start from the project root. First, create a new branch from:
a) your master project branch, or
b) the branch you are upgrading on:
git checkout -b upgrade-1.2.0 |
In case of different localization of the sources, add ezsystems/ezstudio as an upstream remote:
git remote add ezstudio http://github.com/ezsystems/ezstudio.git |
Then pull the tag into your branch:
git pull ezstudio v1.2.0 |
If you had custom siteaccesses or languages set up in your installation, a conflict may appear here. This is because new siteaccesses are introduced in Studio demo in this release: "fr" for French, "de" for German and "no" for Norwegian. To avoid overriding your siteaccesses with the new ones, you need to accept your own changes in the If you have no custom siteaccesses or languages and no conflict occurs, you can do one of the following things: A) Add languages and permissions to use the newly introduced siteaccesses from the demo. To do this, log in to the application and go to the Admin Panel. Choose Languages and click Create a new language. Create a language for each of the new siteaccesses. Then, click Roles and select the Anonymous Role. Click Edit limitations next to the following function:
Select all available siteaccesses and click Save. B) Remove the new siteaccesses. |
You will get conflicts, and it is perfectly normal. The most common ones will be on composer.json and composer.lock.
The latter can be ignored, as it will be regenerated when we execute composer update later. The easiest is to checkout the version from the tag, and add it to the changes:
If you get a lot of conflicts (on the |
git checkout --theirs composer.lock && git add composer.lock |
Conflicts in composer.json need to be fixed manually. If you're not familiar with the diff output, you may checkout the tag's version, and inspect the changes. It should be readable for most:
git checkout --theirs composer.json && git diff HEAD composer.json |
You should see what was changed, as compared to your own version, in the diff output. This update changes the requirements for all of the ezsystems/ packages. Those changes should be left untouched. All of the other changes will be removals of what you added for your own project. Use git checkout -p to selectively cancel those changes:
git checkout -p composer.json |
Answer no (do not discard) to the requirement changes of ezsystems dependencies. Answer yes (discard) to removals of your changes.
Once you are done, inspect the file, either using an editor or by running git diff composer.json. You may also test the file's sanity with composer validate, and test the dependencies by running composer update --dry-run. (will output what it would do to dependencies, without applying the changes.
Once finished, run git add composer.json.
Depending on the local changes you have done, you may get other conflicts: configuration files, kernel...
There shouldn't be many, and you should be able to figure out which value is the right one for all of them:
git add conflicting-file to add the changesAt this point, you should have a composer.json file with the correct requirements. Run composer update to update the dependencies.
composer update --with-dependencies ezsystems/ezpublish-kernel ezsystems/platform-ui-bundle ezsystems/repository-forms ezsystems/studio-ui-bundle ezsystems/ezstudio-demo-bundle ezsystems/landing-page-fieldtype-bundle ezsystems/flex-workflow |
In order to restrict the possibility of unforeseen updates of 3rd party packages, we recommend by default that |
Because from this release onwards eZ Studio is compatible only with PHP 5.5 and higher, the update command above will fail if you use an older PHP version. Please update PHP to proceed. |
The 16.02 release requires an update to the database. Import vendor/ezsystems/ezpublish-kernel/data/update/mysql/dbupdate-6.1.0-to-6.2.0.sql into your database:
mysql -p -u <database_user> <database_name> < vendor/ezsystems/ezpublish-kernel/data/update/mysql/dbupdate-6.1.0-to-6.2.0.sql |
To enable the new Flex workflow notification feature, import the following file:
mysql -p -u <database_user> <database_name> < vendor/ezsystems/ezstudio-notifications/bundle/Resources/install/ezstudio-notifications.sql |
The web assets must be dumped again for the prod environment:
php app/console assetic:dump --env=prod web |
Once all the conflicts have been resolved, and composer.lock updated, the merge can be committed. Note that you may or may not keep composer.lock, depending on your version management workflow. If you do not wish to keep it, run git reset HEAD <file> to remove it from the changes. Run git commit, and adapt the message if necessary. You can now test the project, run integration tests... once the upgrade has been approved, go back to master, and merge the upgrade-1.2.0 branch:
git checkout master git merge upgrade-1.2.0 |
You should now have a new route in
|