eZ Studio 16.02 Release notes

=20

Quick links
Changes sinc= e 15.12.1=20
- Summary of chan= ges
- Full list= of improvements
- Full list of = bugfixes
Known Issues=20
- Disabl= ing Studio Demo Bundle
U= pgrading a 15.12.1 Studio project=20
- Merging com= poser.json
- Updating
- Dump assets
- Commit, test= and merge

=20

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 Februar= y 5th.

For the release notes of the corresponding (and included) eZ Platform release, see eZ Platform 16.02 Release notes.

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: htt= ps://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 co= ntains a direct link to the draft.

As a reviewer you also receive notificati= ons 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 ho= w many requests for review you have received.

Click your profile and choose View notifi= cations. You can see a Notifications window with a list of all requests:

Watch a video

Timeline toolbar shows all changes in all Schedule Blocks on a given La= nding 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 selectin= g airtime for Schedule block.

Various bug fixes.

Full list of im= provements

=20

= =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20 =20

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 =20
EZS-542	Reorganize field views files struct= ure
EZS-531	Change the Favicon for Studio =
EZS-507	Update the look of the indicator li= st and full list
EZS-495	Timepicker add hour and minute slid= ers
EZS-488	Droppable interaction with final an= imation added
EZS-481	Improve the way that users hover ov= er, select and move blocks within Page Mode
EZS-476	As a user, I want to be notified ab= out 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 =20	Add the user profile in the navig= ation hub

=20

=20 11 issues =20

=20

Full list of bugfix= es

=20

Key	Summary	T
EZS-559	All siteaccesses are underlined in = studio	=
EZS-553	Content Airtime Settings reset auto= matically 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 =20	=
EZS-545	Push-out confirmation after freeing= slots in Schedule block	=
EZS-540	Issue with adding duplicated conten= t item in Schedule block	=
EZS-537	No validation on Approval Timeline = page input field	=
EZS-536	Typo in Approval Timeline message t= itle	=
EZS-523	The page preview is trying to updat= e when user is not on a landing page	=
EZS-513	Getting error message when previewi= ng the content of Content List Block	=

=20

=20 10 issues =20

=20

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=20 Backlog
EZP-25505 - UserHash is always generated for anonymous user=20 Backlog

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

Disabling St= udio Demo Bundle

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 t= he highest priority, so you can place your app in a bundle and load it last= in AppKernel.php. Then every Studio Demo configuration will b= e overwritten.

2. Disable the eZStudioDemoBundle from AppKernel.php<= /code>, then only your configuration will remain. This solution generates e= xtra work, you have to take care of content existing in Studio Demo and eve= ry 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 with=
out demo content and with generic landing page block templates, where you c=
an create your design and place configuration wherever you want.


Upgradi=
ng 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:


From your master branch

=20
git checkout -b upgrade-1.2.0=20


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


From the upgrade-1.2.0 branch

=20
git remote add ezstudio http://github.com/ezsystems/ezstudio.git=20


Then pull the tag into your branch:


From the upgrade-1.2.0 branch

=20
git pull ezstudio v1.2.0=20



Caution!


If you had custom siteaccesses or languages set up in your installation,=
 a conflict may appear here. This is because new siteaccesses are introduce=
d 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 acc=
ept your own changes in the app/config/ezplatform.yml file.
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 intro=
duced 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 l=
anguage. Create a language for each of the new siteaccesses.
Then, click Roles and se=
lect the Anonymous Role. Click Edit limitations next to the following funct=
ion:

Select all available siteaccesses and cli=
ck 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 com=
poser update later. The easiest is to checkout the version from the tag, an=
d add it to the changes:



If you get a lot of conflicts (on the doc folder for instance), and eZ Studio was installed from the share.ez.=
no tarball, it might be because of incomplete history. You will have to=
 run git fetch ezstudio --unshallow to load the full=
 history, and run the merge again.





From the upgrade-1.2.0 branch

=20
git checkout --theirs composer.lock && git add composer.lo=
ck=20


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 ver=
sion, and inspect the changes. It should be readable for most:


From the upgrade-1.2.0 branch

=20
git checkout --theirs composer.json && git diff HEAD compo=
ser.json=20


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 o=
f the other changes will be removals of what you added for your own project=
. Use git checkout -p to selectively cancel those changes=
:

=20
git checkout -p composer.json=20


Answer no (do not discard) to the requirement cha=
nges of ezsystems dependencies. Answer yes&n=
bsp;(discard) to removals of your changes.
Once you are done, inspec=
t the file, either using an editor or by running git diff composer.js=
on. You may also test the file's sanity with composer validate=
, and test the dependencies by running composer upda=
te --dry-run. (will output what it would do to dependencies, without=
 applying the changes.

Once finished, run <= code>git add composer.json.

Fixing oth= er conflicts (if any)

Depending on the local changes you have done, you may get other conflict= s: configuration files, kernel...

There shouldn't be many, and you should be able to figure out which valu= e 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<= /li>

Updating

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

=20

composer update --with-dependencies ezsystems/ezpublish-kernel ezsy=
stems/platform-ui-bundle ezsystems/repository-forms ezsystems/studio-ui-bun=
dle ezsystems/ezstudio-demo-bundle ezsystems/landing-page-fieldtype-bundle =
ezsystems/flex-workflow

=20

In order to restrict the possibility of unforeseen updates of 3rd party = packages, we recommend by default that composer update is rest= ricted to the list of packages we have tested the update for. You may remov= e this restriction, but be aware that you might get a package combination w= e have not tested.

On PHP conflict

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.

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:

=20

mysql -p -u <database_user> <database_name> < vendor=
/ezsystems/ezpublish-kernel/data/update/mysql/dbupdate-6.1.0-to-6.2.0.sql=20

To enable the new Flex workflow notification feature, import the followi= ng file:

=20

mysql -p -u <database_user> <database_name> < vendor=
/ezsystems/ezstudio-notifications/bundle/Resources/install/ezstudio-notific=
ations.sql

=20

Dump assets

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

=20

php app/console assetic:dump --env=3Dprod web

=20

Commit, test and m= erge

Once all the conflicts have been resolved, and composer.lock updated, the merge can be committed. Note that you may or may not ke= ep composer.lock, depending on your version management wo= rkflow. If you do not wish to keep it, run git reset HEAD <fi= le> 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 bra= nch:

=20

git checkout master
git merge upgrade-1.2.0

=20

Double check the following before you test:

You should now have a new route in app/config/routing.yml:<= /p>

_ezplatformRepositoryFormsRoutes:<= br> resource: "@EzSystemsRepositoryFormsBundle/Resources/config/rout= ing.yml"