eZ Studio 15.12.1 Release notes

Table of contents:

The first sub-release of eZ Studio 15.12 is available as of February 2nd.

Changes since 15.12

Summary of changes

• Enhanced Landing Page drag-and-drop interactions, including a better visualization of dropping blocks onto the page:

• Timeline toolbar now covers all changes in all Schedule Blocks on a given Landing Page.
• Timeline toolbar is now also available in View mode on Landing Pages:

• Added an Approval Timeline which lists all review requests for a given Content item:

• Modified template of the notification email sent to reviewers from Flex Workflow.
• Minor UI improvements (including: updated icons, labels, date picker and others):

• Added notification when copying a URL.
• Numerous bug fixes.

Full list of improvements

 

Loading …

Key	Summary	T
EZS-509	Get information about content workflow status and messages history from backend
EZS-508	Schedule block: when removing content from the future the content is not moved to the history
EZS-506	As a user, I want to see approval timeline in content editor mode
EZS-500	The timeline should display all future changes from all the schedule blocks at once
EZS-499	Add the timeline to the Page view
EZS-498	Show a dashed frame when dragging over valid target area
EZS-497	Change Schedule block's Delete label
EZS-496	Change Schedule block's Settings label
EZS-494	Datepicker add animation and CSS changes
EZS-493	When clicking on Copy URL user gets a notification that confirms the action done
EZS-487	Draggable interaction - show dashed frame in place of selected element
EZS-486	Refine dragging interaction with elements
EZS-485	Change cursor to show that an element is draggable
EZS-451	When switching from Page to Content I'm not redirected to a correct page in PlatformUI
EZS-450	Replace Slot Icon and label
EZS-449	Change the page title
EZS-412	Update Flex Workflow email template
EZS-402	Dynamic Landing page, define width & height for resizable Page Description input box
EZS-392	Moving blocks on landing pages is tricky
EZS-373	As a User, I want to be able to access the Scheduled Block toolbar at all times
EZS-326	As an editor I would like to see the now time indicator in the timeline when scheduling content inside a schedule block
EZS-185	As an editor I would like to see overflow block select field hidden when overflow is turned off

22 issues Refresh

<ac:structured-macro ac:name="jira" ac:schema-version="1" ac:macro-id="60cbf4aa-e284-45b8-9a1c-1aae0615ad83"><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-373 OR key = EZS-392 OR key = EZS-326 OR key = EZS-402 OR key = EZS-185 OR key = EZS-451 OR key = EZS-485 OR key = EZS-450 OR key = EZS-449 OR key = EZS-486 OR key = EZS-487 OR key = EZS-499 OR key = EZS-500 OR key = EZS-494 OR key = EZS-496 OR key = EZS-497 OR key = EZS-498 OR key = EZS-493 OR key = EZS-508 OR key = EZS-412 OR key = EZS-509 OR key = EZS-506 </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-373 OR key = EZS-392 OR key = EZS-326 OR key = EZS-402 OR key = EZS-185 OR key = EZS-451 OR key = EZS-485 OR key = EZS-450 OR key = EZS-449 OR key = EZS-486 OR key = EZS-487 OR key = EZS-499 OR key = EZS-500 OR key = EZS-494 OR key = EZS-496 OR key = EZS-497 OR key = EZS-498 OR key = EZS-493 OR key = EZS-508 OR key = EZS-412 OR key = EZS-509 OR key = EZS-506 |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-521	The preview height is incorrect
EZS-518	On Publish action page is reloaded twice
EZS-505	When navigating in the Page mode the URL in the browser address bar is not updating
EZS-490	Getting error when opening landing page editor
EZS-475	ContentTypes to be displayed change is not stored after publish
EZS-459	Block not found exception on publish after adding extra block
EZS-458	"button.removeTarget is not a function" error on logout
EZS-444	Blocks are not rendered in the correct order when opening a landing page in the editor
EZS-442	[IE11] The filled slots number is displayed incorrectly
EZS-441	Scroll in editing Landing Page on IE don't work, on FF works slowly
EZS-411	Flex workflow not working when receiving notification
EZS-406	Landing Page editing is blocked when page does not have any blocks (empty zones)
EZS-403	Embed block preview layout position
EZS-398	[IE] Schedule block Timeline colour rendering is broken
EZS-397	[IE] Content List & Keyword block empty field validation always fails
EZS-396	[IE] Landing Page zones layout is broken
EZS-394	[IE] Basics section layout is broken
EZS-393	I can't select the block that I just added to my page
EZS-391	Adding a gallery block to a new landing page breaks the layout view
EZS-312	Cogwheel stuck when creating "Landing Page"
EZP-25291	No `languageCode` is set when creating a new content after canceling previous new content creation

21 issues Refresh

<ac:structured-macro ac:name="jira" ac:schema-version="1" ac:macro-id="720a392c-5c55-4cfe-9c2f-c09171cc645b"><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-312 OR key = EZS-391 OR key = EZS-393 OR key = EZS-393 OR key = EZS-406 OR key = EZS-394 OR key = EZS-398 OR key = EZP-25291 OR key = EZS-397 OR key = EZS-396 OR key = EZS-441 OR key = EZS-442 OR key = EZS-444 OR key = EZS-403 OR key = EZS-458 OR key = EZS-459 OR key = EZS-475 OR key = EZS-490 OR key = EZS-505 OR key = EZS-518 OR key = EZS-521 OR key = EZS-411 </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-312 OR key = EZS-391 OR key = EZS-393 OR key = EZS-393 OR key = EZS-406 OR key = EZS-394 OR key = EZS-398 OR key = EZP-25291 OR key = EZS-397 OR key = EZS-396 OR key = EZS-441 OR key = EZS-442 OR key = EZS-444 OR key = EZS-403 OR key = EZS-458 OR key = EZS-459 OR key = EZS-475 OR key = EZS-490 OR key = EZS-505 OR key = EZS-518 OR key = EZS-521 OR key = EZS-411 |serverId=841cf523-cc54-30bc-bc5d-89e63192498a</ac:parameter><ac:parameter ac:name=": = | TOKEN_TYPE | = :">BLOCK</ac:parameter></ac:structured-macro>

 

Upgrading a 15.12 Studio project

You can easily upgrade your existing Studio project in version 15.12 (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 way 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. The 1.1.0 tag changes the requirements for all of the ezsystems/ packages. Those should be left untouched. All of the other changes should be removals of your project's additions. You can use git checkout -p to selectively cancel those changes:

Answer no (do not discard) to the requirement changes of ezsystems dependencies, and yes (discard) to removals of your changes.

Using composer require

You may also checkout your own composer.json, and run the following commands to update the ezsystems packages requirements from v1.0.x to v1.1.0:

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 composer.lock

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

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.1.0 branch: