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.

Quick links

• Installation instructions
• Requirements

• 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

Changes since 15.12.1

Summary of changes

• Added user profile with notifications containing the number of pending requests for review.

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:

• Timeline toolbar shows all changes in all Schedule Blocks on a given Landing Page, both in View and in Edit modes.
• UI improvement: updated the look of the Items airing and Full list.

• UI improvement: sliders added to the time selection modal when selecting airtime for Schedule block.

• Various bug fixes.

Full list of improvements

 

Loading …

Key	Summary	T
EZS-557	As a user, I want to have at least two user profiles to come in the default demo bundle
EZS-543	Create a slider field view
EZS-542	Reorganize field views files structure
EZS-531	Change the Favicon for Studio
EZS-507	Update the look of the indicator list and full list
EZS-495	Timepicker add hour and minute sliders
EZS-488	Droppable interaction with final animation added
EZS-481	Improve the way that users hover over, select and move blocks within Page Mode
EZS-476	As a user, I want to be notified about new content that's sent to me for review
EZS-470	As a user, I want to be able to use the Timeline Toolbar in View Mode
EZP-25446	Add the user profile in the navigation hub

11 issues Refresh

<ac:structured-macro ac:name="jira" ac:schema-version="1" ac:macro-id="a37c9764-35d1-4086-bfe6-a4c94d0fb47b"><ac:parameter ac:name="server">eZ Systems JIRA tracker</ac:parameter><ac:parameter ac:name="columns">key,summary,type</ac:parameter><ac:parameter ac:name="maximumIssues">1000</ac:parameter><ac:parameter ac:name="jqlQuery">key = EZS-557 OR key = EZS-476 OR key = EZS-507 OR key = EZS-495 OR key = EZS-470 OR key = EZS-543 OR key = EZS-542 OR key = EZS-481 OR key = EZS-531 OR key = EZS-488 OR key = EZP-25446 </ac:parameter><ac:parameter ac:name="serverId">841cf523-cc54-30bc-bc5d-89e63192498a</ac:parameter><ac:parameter ac:name=": = | RAW | = :">server=eZ Systems JIRA tracker|columns=key,summary,type|maximumIssues=1000|jqlQuery=key = EZS-557 OR key = EZS-476 OR key = EZS-507 OR key = EZS-495 OR key = EZS-470 OR key = EZS-543 OR key = EZS-542 OR key = EZS-481 OR key = EZS-531 OR key = EZS-488 OR key = EZP-25446 |serverId=841cf523-cc54-30bc-bc5d-89e63192498a</ac:parameter><ac:parameter ac:name=": = | TOKEN_TYPE | = :">BLOCK</ac:parameter></ac:structured-macro>

 

Full list of bugfixes

 

Loading …

Key	Summary	T
EZS-559	All siteaccesses are underlined in studio
EZS-553	Content Airtime Settings reset automatically after a while
EZS-549	Timestamp appearing the date field instead of a date in the airtime config popup
EZS-547	Can't return to Home page
EZS-545	Push-out confirmation after freeing slots in Schedule block
EZS-540	Issue with adding duplicated content item in Schedule block
EZS-537	No validation on Approval Timeline page input field
EZS-536	Typo in Approval Timeline message title
EZS-523	The page preview is trying to update when user is not on a landing page
EZS-513	Getting error message when previewing the content of Content List Block

10 issues Refresh

<ac:structured-macro ac:name="jira" ac:schema-version="1" ac:macro-id="69b38c58-1491-4930-9d28-f5a7620e2c6b"><ac:parameter ac:name="server">eZ Systems JIRA tracker</ac:parameter><ac:parameter ac:name="columns">key,summary,type</ac:parameter><ac:parameter ac:name="maximumIssues">1000</ac:parameter><ac:parameter ac:name="jqlQuery">key = EZS-559 OR key = EZS-553 OR key = EZS-540 OR key = EZS-545 OR key = EZS-549 OR key = EZS-547 OR key = EZS-537 OR key = EZS-536 OR key = EZS-523 OR key = EZS-513 </ac:parameter><ac:parameter ac:name="serverId">841cf523-cc54-30bc-bc5d-89e63192498a</ac:parameter><ac:parameter ac:name=": = | RAW | = :">server=eZ Systems JIRA tracker|columns=key,summary,type|maximumIssues=1000|jqlQuery=key = EZS-559 OR key = EZS-553 OR key = EZS-540 OR key = EZS-545 OR key = EZS-549 OR key = EZS-547 OR key = EZS-537 OR key = EZS-536 OR key = EZS-523 OR key = EZS-513 |serverId=841cf523-cc54-30bc-bc5d-89e63192498a</ac:parameter><ac:parameter ac:name=": = | TOKEN_TYPE | = :">BLOCK</ac:parameter></ac:structured-macro>

 

Known Issues

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:

• EZP-25789 - Editors access to own user and read all user meta info for author field type Backlog
• EZP-25505 - UserHash is always generated for anonymous user Backlog

Both are currently being worked on and will be fixed in patch version in the next couple of weeks.

Upgrading a 15.12.1 Studio project

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:

In case of different localization of the sources, add ezsystems/ezstudio as an upstream remote:

Then pull the tag into your branch:

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:

Merging composer.json

Manual merging

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:

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:

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.

Fixing other conflicts (if any)

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:

• Edit the file, and identify the conflicting changes. If a setting you have modified has also been changed by us, you should be able to figure out which value is the right one.
• Run git add conflicting-file to add the changes

Updating

At this point, you should have a composer.json file with the correct requirements. Run composer update to update the dependencies. 

Database update

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:

To enable the new Flex workflow notification feature, import the following file:

Dump assets

The web assets must be dumped again for the prod environment:

Commit, test and merge

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: