New! Checkout our new Forums homepage! Follow the latest activity in eZ Publish Forums on Share.ez.no, Projects.ez.no and StackOverflow.com


@ezecosystem
ezecosystem pushed to master in ezecosystem/ezpublish-kernel Aug 17, 2018
2 commits to master
  • @kmadejski 0495e5c
    Merge branch '7.2'
  • @kmadejski da6a849
    EZP-29536: User isn't redirected to the login page when UnauthorizedE…
08/17/2018 11:58 am   eZecosystem @ GitHub   Mirror   Link  

Content Scheduler Block Capabilities

Previously, the Content Scheduler Block was called the Schedule Block. We decided to rename this feature to avoid any confusion of its purpose and functionality.

The Content Scheduler Block is for the Page Builder. When placed on the page, the Content Scheduler Block allows the editor to schedule when and which content will appear and move in the block, whether that be a news headline, new marketing campaign, new product release, or anything time sensitive.

The Content Scheduler works very similarly to a regular content collection block. The main difference is when editors add content to the block, they can now choose when to add that content, whether that be right now or sometime in the future.

When content is added right away, it’s added to the list of active content for the block. When content is added in the future, the editor needs to establish a date and time for when that content should “air,” otherwise known as the “airtime.”

When we reach airtime, the content will then be moved from the queue to the active list, pushing other content items further down in the block. To avoid an overflow of content, editors can now define a limit for the number of active content items.

For example, if an editor limits the number of active content items to 3 and the active list already shows 3 content items, then once a new content item is added, the last piece of content at the bottom of the list will be automatically pushed out of the list.

One thing we heard from eZ Platform 1.x users is that they wanted a simpler way to reorder items in the active list. We’ve now implemented a simple drag and drop function, like what can be done with the collection block.

Define block name and number of items in the Active list (display limit)

Add a content item to the queue with a specific airtime

Add several content items and some immediately visible (in the active list)

In the past, eZ Flow/Schedule Block users have utilized this feature in many ways. We received lots of feedback regarding different improvements that could be made. We plan on adding 2 new capabilities to the Content Scheduler Block in the future: pinning and swapping. Although we won’t add them as part of v2.3, we hope to include them in v2.4. We also continue to welcome any feedback you may have about the Content Scheduler Block.

Looking ahead, what does “pinning” mean? Pinning a content item is when the editor forces a content item to stay in the same position and remain displayed on the website. If new content items are added to the block, then only the unpinned items will either move down the list or be pushed out.

The other future capability is called “swapping.” Swapping is when the editor schedules a swap between one active content item and another inactive content item at a specific time and date. The new content item will then be placed in the queue until the scheduled time and date of the swap arrives.

Thanks to our users’ feedback, the Content Scheduler Block features are now much simpler than previous versions. Specifically, the “overflow” feature (which let editors connect two Schedule Blocks together) has been removed.

Simply put, this feature was not very popular, and our users told us it was not bringing them much value. As ever, our goal is to always optimize as much as we can whenever and wherever we can.

Pinning a content item

Block Scheduler

The Block Scheduler is a new feature we’re also introducing in v2.3. Unlike the Content Scheduler Block, which is a specific block, this feature will be available to every block configured on your project, including custom blocks.

With the Block Scheduler, an editor will be able to define the visibility of a block in advance by configuring the dates they would like the block to be visible or hidden from the page. The main benefit of this feature is that it makes things simpler for editors and saves them time when scheduling events.

Configuring the visibility of a block 

In the future, we plan on introducing additional capabilities to the Block Scheduler. One capability we’re thinking of developing allows editors to specify recurring visibility events. Just like you can define recurring events in a calendar, editors will also be able to define recurring visibility time slots on their site.

For example, an editor would be able to schedule a block so that it would be visible every day between 9 AM and 12 PM for the duration of one week.

Since we’re waiting until after v2.3 to prioritize its development, we would love to hear any feedback about this feature or any other possible enhancements to block visibility.

Scheduling block to be visible from 9 AM - 12 PM

Timeline Feature

Similar to the Content Scheduler Block and the Block Scheduler features, the timeline is a unique feature that none of our competitors currently offer. This tool gives control to editors by providing information on what events are scheduled for their different pages.

The timeline functionality is simple, requiring the user to just select a date and/or time on the timeline or timeline calendar, in order to see all the events and actions that are scheduled. Users can also use the timeline to preview how the page will look at a specific time and date.

Compared to previous versions, the page timeline feature has been greatly improved. The timeline not only reacts to Content Scheduler Block events, but also to other scheduled events.

In other words, the timeline can indicate the following actions for editors:

  • Addition of content to the Content Scheduler Block (as it previously did)
  • Visibility changes of any block
  • Change of content for pages that have been modified and are scheduled for publishing

In order to avoid a cluttered UI, the events’ information is disclosed progressively, only showing the most relevant information (what and when). For more detailed information, we use tooltips, so that users can check with ease about the specific details of the event scheduled.

Finally, from the Developer Experience perspective, the timeline is also designed to provide developers with the ability to add custom events to the timeline when customizing and extending eZ Platform.

Page Timeline

Custom events on the timeline

Page timeline on the page builder

What to Expect Next?

We’re confident that these new features will allow your editorial team to manage their content more efficiently and effortlessly.

We look forward to unveiling many more exciting features in this upcoming release at the end of September. We hope to include the new Form Builder as well as the new Personalization Block in the upcoming Enterprise Edition.

When it comes to the open source edition of eZ Platform, we are currently improving the Universal Discovery Widget (UDW); developing a new Image Asset field type that lets editors reuse images from Image fields; and continuously fixing bugs.

In the meantime, if you’re interested or have any questions, please feel free to leave a comment here or on discuss.ezplatform.com. Feel free to reach out to us, too, at productmanagement@ez.no.

08/17/2018 09:59 am   ez.no/About-eZ/Blog   Mirror   Link  

Content Scheduler Block Capabilities

Previously, the Content Scheduler Block was called the Schedule Block. We decided to rename this feature to avoid any confusion of its purpose and functionality.

The Content Scheduler Block is for the Page Builder. When placed on the page, the Content Scheduler Block allows the editor to schedule when and which content will appear and move in the block, whether that be a news headline, new marketing campaign, new product release, or anything time sensitive.

The Content Scheduler works very similarly to a regular content collection block. The main difference is when editors add content to the block, they can now choose when to add that content, whether that be right now or sometime in the future.

When content is added right away, it’s added to the list of active content for the block. When content is added in the future, the editor needs to establish a date and time for when that content should “air,” otherwise known as the “airtime.”

When we reach airtime, the content will then be moved from the queue to the active list, pushing other content items further down in the block. To avoid an overflow of content, editors can now define a limit for the number of active content items.

For example, if an editor limits the number of active content items to 3 and the active list already shows 3 content items, then once a new content item is added, the last piece of content at the bottom of the list will be automatically pushed out of the list.

One thing we heard from eZ Platform 1.x users is that they wanted a simpler way to reorder items in the active list. We’ve now implemented a simple drag and drop function, like what can be done with the collection block.

Define block name and number of items in the Active list (display limit)

Add a content item to the queue with a specific airtime

Add several content items and some immediately visible (in the active list)

In the past, eZ Flow/Schedule Block users have utilized this feature in many ways. We received lots of feedback regarding different improvements that could be made. We plan on adding 2 new capabilities to the Content Scheduler Block in the future: pinning and swapping. Although we won’t add them as part of v2.3, we hope to include them in v2.4. We also continue to welcome any feedback you may have about the Content Scheduler Block.

Looking ahead, what does “pinning” mean? Pinning a content item is when the editor forces a content item to stay in the same position and remain displayed on the website. If new content items are added to the block, then only the unpinned items will either move down the list or be pushed out.

The other future capability is called “swapping.” Swapping is when the editor schedules a swap between one active content item and another inactive content item at a specific time and date. The new content item will then be placed in the queue until the scheduled time and date of the swap arrives.

Thanks to our users’ feedback, the Content Scheduler Block features are now much simpler than previous versions. Specifically, the “overflow” feature (which let editors connect two Schedule Blocks together) has been removed.

Simply put, this feature was not very popular, and our users told us it was not bringing them much value. As ever, our goal is to always optimize as much as we can whenever and wherever we can.

Pinning a content item

Block Scheduler

The Block Scheduler is a new feature we’re also introducing in v2.3. Unlike the Content Scheduler Block, which is a specific block, this feature will be available to every block configured on your project, including custom blocks.

With the Block Scheduler, an editor will be able to define the visibility of a block in advance by configuring the dates they would like the block to be visible or hidden from the page. The main benefit of this feature is that it makes things simpler for editors and saves them time when scheduling events.

Configuring the visibility of a block 

In the future, we plan on introducing additional capabilities to the Block Scheduler. One capability we’re thinking of developing allows editors to specify recurring visibility events. Just like you can define recurring events in a calendar, editors will also be able to define recurring visibility time slots on their site.

For example, an editor would be able to schedule a block so that it would be visible every day between 9 AM and 12 PM for the duration of one week.

Since we’re waiting until after v2.3 to prioritize its development, we would love to hear any feedback about this feature or any other possible enhancements to block visibility.

Scheduling block to be visible from 9 AM - 12 PM

Timeline Feature

Similar to the Content Scheduler Block and the Block Scheduler features, the timeline is a unique feature that none of our competitors currently offer. This tool gives control to editors by providing information on what events are scheduled for their different pages.

The timeline functionality is simple, requiring the user to just select a date and/or time on the timeline or timeline calendar, in order to see all the events and actions that are scheduled. Users can also use the timeline to preview how the page will look at a specific time and date.

Compared to previous versions, the page timeline feature has been greatly improved. The timeline not only reacts to Content Scheduler Block events, but also to other scheduled events.

In other words, the timeline can indicate the following actions for editors:

  • Addition of content to the Content Scheduler Block (as it previously did)
  • Visibility changes of any block
  • Change of content for pages that have been modified and are scheduled for publishing

In order to avoid a cluttered UI, the events’ information is disclosed progressively, only showing the most relevant information (what and when). For more detailed information, we use tooltips, so that users can check with ease about the specific details of the event scheduled.

Finally, from the Developer Experience perspective, the timeline is also designed to provide developers with the ability to add custom events to the timeline when customizing and extending eZ Platform.

Page Timeline

Custom events on the timeline

Page timeline on the page builder

What to Expect Next?

We’re confident that these new features will allow your editorial team to manage their content more efficiently and effortlessly.

We look forward to unveiling many more exciting features in this upcoming release at the end of September. We hope to include the new Form Builder as well as the new Personalization Block in the upcoming Enterprise Edition.

When it comes to the open source edition of eZ Platform, we are currently improving the Universal Discovery Widget (UDW); developing a new Image Asset field type that lets editors reuse images from Image fields; and continuously fixing bugs.

In the meantime, if you’re interested or have any questions, please feel free to leave a comment here or on discuss.ezplatform.com. Feel free to reach out to us, too, at productmanagement@ez.no.

08/17/2018 09:59 am   eZ Systems News   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/bccie Aug 17, 2018
2 commits to master
  • @brookinsconsulting 6911901
    Merge pull request #20 from lpmi-13/typofix
  • @lpmi-13 06c635b
    fix simple typo
08/16/2018 11:57 pm   eZPublishLegacy @ GitHub   Mirror   Link  

In the realm of digital publishing, there’s no shortage of creative ideas, but not every business idea is suitable for magazine publishers. Sometimes it’s prudent to stick with tried and true innovations, or to emulate those who have had proven success.

08/16/2018 01:50 pm   Mugo Web Blog   Mirror   Link  

Like many magazine publishers, Habitat Magazine has a long history of creating quality content targeted to its specialized audience: property managers and condo board members in the New York area. But, with its potential audience maxing out at about 7,500 subscribers, Habitat has had to get creative with digital media opportunities that have enabled it to repurpose and leverage its content in order to grow. By taking a deep dive into its branded content, and by taking an incremental approach to digital innovation, Habitat has been able to create new digital revenue streams that have been critical to its survival.

08/16/2018 12:37 pm   Mugo Web Blog   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/docker-php Aug 16, 2018
1 commit to master
  • @andrerom 93724d0
    Add support for igbinary to reduce serialization size on Redis & Memc…
08/15/2018 11:57 pm   eZecosystem @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/ezpublish-legacy Aug 15, 2018
2 commits to master
  • @andrerom 870ffa1
    Merge branch '2017.12'
  • @andrerom 6321a92
    [PHP] Fix some PHP 7.2 deprecations (#1382)
08/15/2018 12:21 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/ezplatform Aug 15, 2018
2 commits to master
08/15/2018 12:18 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/Sylius Aug 15, 2018
2 commits to master
08/15/2018 12:11 pm   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezplatform Aug 15, 2018
2 commits to master
08/15/2018 12:03 pm   eZecosystem @ GitHub   Mirror   Link  

We’re super thrilled to announce that SymfonyLive USA becomes now Symfony Loves PHP USA conference!

Welcome to Symfony Loves PHP USA, the only conference dedicated to Symfony and PHP in the USA. We decided to change the conference name and its purpose to create a unique place in the USA where you can hear all the latest and best developments with Symfony and PHP! We aim to gather the American Symfony and PHP communities in San Francisco from October 11th to October 12th. We want you to come and feel welcome regardless your level of development with Symfony or PHP (beginner, advanced, intermediate).

Not registered yet? Well, check out the schedule and take your conference ticket for 2 days of conference at $289!

We're super excited to announce that the conference schedule has just been released! We're very pleased to welcome 13 speakers at the conference. Meet all the conference speakers (in alphabetical order):

  • Jordi Boggiano, Composer PHP lead and Co-founder of Packagist, will be speaking about "the Building global web apps with multi-region hosting". This session will explore various setups and case studies from his attempts at hosting sites used by global audiences.

  • Kristen Costagliola will be talking about "Orchestrating Symfony for the Enterprise". Whether you are just starting out learning Symfony, maintaining a healthy Symfony application, or expanding Symfony's presence in your company, this talk will give you tools and the questions to ask yourself to help your company succeed.

  • Michael Cullum, Symfony Security Lead, PHP-FIG Core Committee and phpBB Team, will be presenting a talk about "Trend analysis and machine learning in PHP". This talk will talk about how you can, in your Symfony applications, perform some simple trend analysis techniques to build models, analyse data to get useful information and spot anomalies.

  • Cal Evans will be speaking about "Uncle Cal's Career Advice for Developers" at the opening keynote on Friday morning! In this talk you’ll examine a few of the life-lessons Cal has learned the hard way. Some of them will be interesting, some of them insightful, some of them silly. Regardless, these lessons were generally learned by making big enough mistakes.

  • Nicolas Grekas, Symfony Core Team Member, will be talking about "Symfony Cache: a premium recipe to fast apps". With some raw examples and benchmarks, let's review how to select the best backend for your needs, wire them in your apps, do tags-based invalidation, protect against cache stampede, etc. Caching might be the most efficient strategy to fast apps.

  • Jonathan Johnson will be speaking about "Ready Set Go: Loading Single Page Apps Fast". First impressions matter. You only have a few milliseconds to make one on the web. Let's find out how to organize the way your assets load and are cached to do better and enhance your users experience.

  • Jeremy Mikola will be giving a talk about "PHP Internals for the Inquisitive Developer". Even if you have no intention of becoming a PHP core developer or creating a PECL extension, cursory knowledge of PHP's inner workings can prove useful. Discover the lifecycle of a PHP request and equip you with essential knowledge and tools!

  • Fabien Potencier, Symfony founder and project lead, will be on stage for the opening Keynote on Thursday morning! Stay tuned for more details to be announced soon.

  • Samuel Roze, Symfony Core Team member, will present a talk entitled “Symfony Messenger: Messages, Queues, Workers and more” about the new Messenger component that he created a few months ago.

  • Tugdual Saunier will speak about "Rocking Modern Security with Symfony". Let's look at some real-world examples of solving security challenges using the latest features & best-practices of Symfony's security component.

  • Dave Stokes, MySQL Community Manager, will talk about "MySQL 8 Tips and Tricks". MySQL 8 has many new features that you will learn to exploit in this session.

  • Jonathan Wage, Doctrine & Symfony contributor, will be speaking about "Doctrine for Beginners". In this talk we will take you through how to get started with Doctrine and how to take advantage of some of the more advanced features.

  • Ryan Weaver, Symfony Core Team Member, lead of Symfony Documentation, will present two talks for our great pleasure! Ryan will be talking about "Webpack Encore: Tips, Tricks, Questions & Best Practices". In this talk, we'll quickly learn the basics of Symfony's Webpack Encore. A modern frontend build system: all in the time of one talk. He will also be speaking about "Practical Guide to Service, Config, Secrets & Deployment". Symfony's configuration system has improved a lot in recent years. Let's step back and look at how we can tackle all of the most common problems using the new approaches!

Symfony and PHP fans, don’t miss the upcoming presentations, discussions, symposiums, meetups and our wonderful conference happy hour.

If you want to get the most out of the conference, we recommend you to register also for the pre-conference workshops! Get your combo ticket for the pre-conference workshops and the conference! We organized several workshops on October 9th and 10th:

  • Getting up and running with Symfony (2 days). This training helps you master some of the most advanced tools and key concepts of the Symfony framework.
  • Extending and Hacking Symfony (2 days). This training leads you to the greatest Symfony level and helps you improve and confirm your current knowledge of the Symfony framework!
  • Mastering OOD & Design Patterns (1 day). This workshop will help you better understand all the concepts and techniques to write cleaner, more robust and more testable object oriented code. This workshop is a combo with Symfony 4 Best Practices (1 day). During this workshop, you will discover the new practices recommended by the Symfony Core team.

See you at the Symfony Loves PHP conference this fall! We can't wait to meet you there! From Symfony with <3


Be trained by Symfony experts - 2018-08-22 Paris - 2018-08-27 Clichy - 2018-08-27 Clichy
08/15/2018 10:17 am   Symfony Blog   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/phpunit Aug 14, 2018
2 commits to master
08/14/2018 12:29 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/ezplatform Aug 14, 2018
2 commits to master
08/14/2018 12:11 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/Sylius Aug 14, 2018
2 commits to master
  • @pamil 1829d35
    Merge pull request #9652 from SyliusBot/crowdin/master-2018-08-14-10-43
  • @SyliusBot 7cdcd75
    [Translations] Updated translations from Crowdin
08/14/2018 12:07 pm   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezplatform Aug 14, 2018
2 commits to master
08/14/2018 11:59 am   eZecosystem @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/phpunit Aug 13, 2018
2 commits to master
08/13/2018 12:30 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/ezpublish-kernel Aug 13, 2018
2 commits to master
08/13/2018 12:12 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/ezpublish-api Aug 13, 2018
2 commits to master
08/13/2018 12:11 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/Sylius Aug 13, 2018
2 commits to master
08/13/2018 12:07 pm   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/NetgenAdminUIBundle Aug 13, 2018
2 commits to master
08/13/2018 12:04 pm   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezpublish-kernel Aug 13, 2018
2 commits to master
08/13/2018 12:00 pm   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezpublish-api Aug 13, 2018
2 commits to master
08/13/2018 12:00 pm   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezplatform-xmltext-fieldtype Aug 13, 2018
2 commits to master
  • @vidarl a1fb3a8
    EZP-29487: ezxmltext -> richtext conversion : Add command option for …
  • @vidarl 3da761a
    EZP-29484: ezxmltext -> richtext conversion : Paragraphs containing t…
  • 1 more commits »
08/13/2018 11:59 am   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezplatform-legacy Aug 13, 2018
2 commits to master
08/13/2018 11:59 am   eZecosystem @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/phpunit Aug 12, 2018
2 commits to master
08/12/2018 12:25 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/LegacyBridge Aug 12, 2018
2 commits to master
  • @andrerom dacc923
    Merge branch '1.4'
  • @andrerom f49ac16
    Fix wrapper installer failing on deeper var folder structures (defaul…
08/12/2018 12:18 pm   eZPublishLegacy @ GitHub   Mirror   Link  

This week Symfony fixed some circular reference issues and improved the performance of the lint:xliff command. In addition, the Symfony and Twig certifications announced a special offer to get you certified with a 40% discount.

Symfony development highlights

2.8 changelog:

  • 74a4cea: [HttpFoundation] fixed false-positive ConflictingHeadersException
  • ea0b508: [Security] call AccessListener after LogoutListener

3.4 changelog:

  • ba31bab: [DependencyInjection] fixed false-positive circular ref leading to wrong exceptions or infinite loops at runtime
  • 98d7a95: [DependencyInjection] fixed analyzing lazy refs involved in circular loops

4.1 changelog:

  • 3e47827: [Form] removed extra .form-group wrapper around file widget in bootstrap 4
  • 9fae8f4: [Translation] fixed performance of lint:xliff command
  • 441322f: [DependencyInjection] fixed autowire inner service

Master changelog:

  • 13dc341: [DependencyInjection] allow autoconfiguring bindings
  • f61bc24: [DependencyInjection] fixed dumping service locators
  • 550b8b8: [Config] show proposals when unsupported option is provided
  • 83a9ca6: [Config] renamed FileLoaderLoadException to LoaderLoadException
  • f96753b: [Routing] added fallback to cultureless locale for internationalized routes

Newest issues and pull requests

They talked about us

Upcoming Symfony Events

Call to Action


Be trained by Symfony experts - 2018-08-22 Paris - 2018-08-27 Clichy - 2018-08-27 Clichy
08/12/2018 03:36 am   Symfony Blog   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/LegacyBridge Aug 10, 2018
2 commits to master
08/10/2018 12:25 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/EzSystemsRecommendationBundle Aug 10, 2018
2 commits to master
  • @andrerom 5aee85d
    Merge branch '2.2'
  • @kmadejski 4b8b497
    Set proper service as lazy (#114)
08/10/2018 12:21 pm   eZPublishLegacy @ GitHub   Mirror   Link