New! Our new Issues homepage has the latest issue ticket changes. Follow the latest progress of eZ Publish!


News

How to create forms with the new Form Builder

In an earlier sneak peek, Amit Golan Gutin, Product Marketing Manager at eZ, introduced improvements around scheduling changes on your website. This week Amit provides an insight into the new Form Builder which will also be part of eZ Platform 2.3.

“eZ Platform v2.3 is a mere two weeks away and is expected to reintroduce many useful features that were missing in the previous release. One of those prominent features is the form builder. The form builder will allow users to easily create, manage and reuse forms anywhere on their website. One of our goals was also to continue improving the editorial experience by enabling users to easily edit forms.”

Read the full article on our blog.

Slack Channels Archived and Renamed

This week several unused channels on our Community Slack Workspace have been archived. Some channels were renamed, for instance #ezstudio-use to #ezplatform-enterprise and #i18n to #ezplatform-i18n. Finally, missing or incomplete channel Topics and Use descriptions were also corrected.

Reminder: Help us Translate eZ Platform

eZ Platform 2.3 will be released at the end of this month. If you are using eZ Platform in a multilingual environment, now would be the time to join our translation effort. Get your own language ready and shipped with 2.3!

We have setup a server running the demo, based on the latest version of eZ Platform. This server is shared with the public and enables in-context translation. All you need is an account on Crowdin.com and follow the tutorial shared here.

In Other News:

Resources

How to contribute to our documentation

With our Developer Documentation moved to http://doc.ezplatform.com, it is now easier for everyone to contribute through GitHub. So let’s have a look at how to do this.

You can visit the Documentation repository on GitHub, find the corresponding *.md files and make your suggestions there. Or follow your regular Git workflow cloning the repository and contributing to the documentation. Other methods could be submitting a Jira issue, posting your suggestions on our dedicated Slack doc channel or contacting the Doc Team via email. To get the full details on all these options, check out our contributing to documentation page.

Looking for a bundle compatible with eZ Platform? Check out: https://ezplatform.com/Bundles.

Social Media

Follow us on Twitter, Facebook, LinkedIn, Google+, or YouTube, and join our Community for any help with eZ Platform or community-related questions.

Find eZ at These Events

For more events, make sure to check out this list.

Each week we publish a roundup of highlights from the eZ ecosystem. If you have any news or events to share, please contact me.

(Lead image credit: Tom Ishida, CC)

09/21/2018 01:15 pm   ez.no/About-eZ/Blog   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/repository-forms Sep 21, 2018
1 commit to master
  • @ViniTou 23bb2ff
    EZP-29269: User draft is not discarded on edition cancel (#240)
09/21/2018 12:40 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/phpunit Sep 21, 2018
2 commits to master
09/21/2018 12:38 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/NetgenEzFormsBundle Sep 21, 2018
1 commit to master
  • @MarioBlazek 26f6131
    Increase memory limit on TravisCI
09/21/2018 12:30 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/ezstudio Sep 21, 2018
2 commits to master
09/21/2018 12:19 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/repository-forms Sep 21, 2018
1 commit to master
  • @ViniTou 23bb2ff
    EZP-29269: User draft is not discarded on edition cancel (#240)
09/21/2018 12:08 pm   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/NetgenEzFormsBundle Sep 21, 2018
1 commit to master
  • @MarioBlazek 26f6131
    Increase memory limit on TravisCI
09/21/2018 12:06 pm   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezstudio Sep 21, 2018
2 commits to master
09/21/2018 12:03 pm   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezplatform-xmltext-fieldtype Sep 21, 2018
2 commits to master
  • @vidarl 129e65b
    EZP-29601: As a editor I want to be able to insert html code in a ric…
  • @vidarl dbae354
    EZP-29595: ezxmltext -> richtext conversion : <header> inside <paragr…
09/21/2018 12:01 pm   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezplatform-com Sep 21, 2018
1 commit to master
  • @SylvainGuittard ab33ef3
    COM-20058: Add product feedback portal (#140)
09/21/2018 12:00 pm   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/repository-forms Sep 21, 2018
2 commits to master
  • f419d85
    README update (#253)
  • @adamwojs 9708389
    EZP-29508: As an editor I want to manage ALT field with an image asse…
09/21/2018 12:06 am   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/PlatformUIBundle Sep 21, 2018
2 commits to master
  • @andrerom 774b853
    Merge branch '1.13'
  • @konradoboza 62b681c
    EZP-29234: As a developer, I want to read about customizing REST API …
09/21/2018 12:06 am   eZecosystem @ GitHub   Mirror   Link  

In a previous blog post we covered how to create custom tags in eZ Platform (with the legacy bridge or eZ Publish 5.x). The most difficult part of that process was building the XSL to output the custom tag HTML. But there's a simpler way to do it, which allows the developer to use Twig template code instead of XSL.

 

09/20/2018 04:36 pm   Mugo Web Blog   Mirror   Link  

In a previous blog post we covered how to create custom tags in eZ Platform (with the legacy bridge or eZ Publish 5.x). The most difficult part of that process was building the XSL to output the custom tag HTML. But there's a simpler way to do it, which allows the developer to use Twig template code instead of XSL.

09/20/2018 12:41 pm   share.ez.no/blogs   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/repository-forms Sep 20, 2018
2 commits to master
  • f419d85
    README update (#253)
  • @adamwojs 9708389
    EZP-29508: As an editor I want to manage ALT field with an image asse…
09/20/2018 12:41 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/PlatformUIBundle Sep 20, 2018
2 commits to master
  • @andrerom 774b853
    Merge branch '1.13'
  • @konradoboza 62b681c
    EZP-29234: As a developer, I want to read about customizing REST API …
09/20/2018 12:39 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/EzSystemsRecommendationBundle Sep 20, 2018
2 commits to master
09/20/2018 12:24 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/ezpublish-spi Sep 20, 2018
2 commits to master
  • @brookinsconsulting 2727cb7
    Merge remote-tracking branch 'upstream/master'
  • @adamwojs ee03aa1
    EZP-29508: As an editor I want to manage ALT field with an image ass…
09/20/2018 12:20 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/ezpublish-kernel Sep 20, 2018
2 commits to master
09/20/2018 12:19 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/ezflow Sep 20, 2018
1 commit to master
  • @chs2 86fa840
    Removed include_once() to avoid "Cannot redeclare class" (#76)
09/20/2018 12:13 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/EzSystemsRecommendationBundle Sep 20, 2018
2 commits to master
09/20/2018 12:03 pm   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezpublish-spi Sep 20, 2018
1 commit to master
  • @adamwojs ee03aa1
    EZP-29508: As an editor I want to manage ALT field with an image ass…
09/20/2018 12:01 pm   eZecosystem @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/Cache Sep 20, 2018
2 commits to master
  • @derickr fbd76c9
    Merge pull request #3 from pbek/php72-deprecation-fixes
  • @pbek ef17cde
    PHP 7.2 deprecation fixes
09/20/2018 12:01 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezpublish-kernel Sep 20, 2018
2 commits to master
09/20/2018 12:01 pm   eZecosystem @ GitHub   Mirror   Link  

What problems are we trying to solve?

Our previous Form Builder was a part of the landing page manager from 1.7 LTS to v2. When we introduced our Page Builder with v2.2 to replace the landing page manager, we on-purposely decoupled the Form Builder from it and did not redevelop it. Now is the time to bring back this feature as a standalone part of our product, while improving the limitations the previous version possessed.

The first limitation was that editors did not have the ability to reuse forms from different locations. Each time editors needed to create a new form for different pages, which can be very annoying and time-consuming. This was due to forms being thought of as blocks within pages, without the ability to reuse them across different pages.

Re-using forms was identified as an important need for editors. Hence, we decided to build a user interface dedicated to that purpose. Users now have a full-screen mode, which will make it easier for them to edit compared to when they needed to edit a form as a block within a page in the Page Builder.

Besides updating these limitations, we also wanted to allow editors to manage translations, versions, and submissions. We will dive into these new capabilities later in the blog post. But until then let’s better understand better the benefits that the Form Builder manager will provide to marketers, editors, and developers.

Developers will be pleased to discover that with the new form builder they will be able to easily customize and extend form fields. More importantly, they should be delighted to discover that we decided to re-use the content repository and build forms on top of it, as a field type. This way, they can easily create different form content types with different fields and then save/publish them at different places within the repository (even if we provide a default location, such as the Media library for media, they have full freedom on their repository organization).

Moving forward marketers and editors will have a much more intuitive and simpler interface to create forms. Since forms are decoupled from the page, users can now create forms ahead of time and reuse and embed them in different locations. They can quickly create a form by dragging and dropping different fields resulting in collecting information within seconds.

Form Block

Creating a Form

Form Builder Interface

Drag and Drop Form Fields

Now let’s dive in and discover more about the different capabilities of the Form Builder manager block:

Versioning forms

Since forms are now attached to a content type and managed as content items in the repository, users will be able to restore a previous version of a form or preview a draft before publishing the form.

Translating forms

Another great benefit of using content types for forms is that editors can now translate their forms into different languages when working on a multilingual site. They will also be able to manage form submissions by language.

Using content relations and other perks from the content repository

Now that forms are content items, editors can create relations between forms and other content items in the repository. It can help see how and where forms are used. This simplifies the process of embedding forms within the online editor. Editors can benefit from all the other perks coming along with the content repository, such as placing a form at multiple locations, using the flex workflow to get approval before publishing a form or publishing a form in the future.

Managing form submissions

Managing form submissions can be messy and quite tricky sometimes. We decided to simplify this by keeping form submissions separate from the content repository. The information collected will be stored in a separate database. We believe this will be extremely beneficial as you will be able to access and download this data anytime. Storing form submissions outside the content repository will also allow companies to easily manage the collected data. We will also include a submissions tab on the administrative interface, so users can easily view such form submissions. This can also be handy when trying to be GDPR compliant. For example, in the future, we plan to create buttons that will allow editors to search and delete collected data.

Stored Submissions

Form Submission

What to expect in the future

We are very excited for the upcoming release. We believe that the Form Builder and other features will significantly improve the editorial experience. The Form Builder block will also be a great addition to the page builder which was introduced in v2.2. It is important to remember that this is only the first iteration of this new Form Builder. In the future we have more updates in the plan, such as, “developing more out-of-the-box GDPR capabilities, providing webhook and potential connectors to integrate the form submissions with 3rd party systems, providing extension and customization capabilities to let users customize the Form Builder to build advanced features such as polls, surveys or others, and to include more fields. If you have any need, opinion or idea, of what would be helpful for you in the future, please drop us a note.

Next week we will provide a sneak peek to the image asset field type that is also expected to be shipped with v2.3. Until then, 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.

09/20/2018 10:05 am   ez.no/About-eZ/Blog   Mirror   Link  

What problems are we trying to solve?

Our previous Form Builder was a part of the landing page manager from 1.7 LTS to v2. When we introduced our Page Builder with v2.2 to replace the landing page manager, we on-purposely decoupled the Form Builder from it and did not redevelop it. Now is the time to bring back this feature as a standalone part of our product, while improving some of its weaknesses the previous version possessed.

The first limitation was that editors did not have the ability to reuse forms at different places. Each time editors needed to create a new form for different pages, which can be very annoying and time-consuming. This was due to forms being thought of as blocks within pages, without the ability to reuse them across different pages.

Re-using forms was identified as an important need for editors. Hence, we decided to build a user interface dedicated to that purpose. Users now have a full-screen mode, which will make it easier for them to edit compared to when they needed to edit a form as a block within a page in the Page Builder.

Besides removing this limitation, we also wanted to allow editors to manage translations, versions, and submissions. We will dive into these new capabilities later in the blog post. But until then let’s better understand better the benefits that the Form Builder manager will provide to marketers, editors, and developers.

Developers will be pleased to discover that with the new form builder they will be able to easily customize and extend form fields. More importantly, they should be delighted to discover that we decided to re-use the content repository and build forms on top of it, as a field type. This way, they can easily create different form content types with different fields and then save/publish them at different places within the repository (even if we provide a default location, such as the Media library for media, they have full freedom on their repository organization).

Moving forward marketers and editors will have a much more intuitive and simpler interface to create forms. Since forms are decoupled from the page, users can now create forms ahead of time and reuse and embed them in different locations. They can quickly create a form by dragging and dropping different fields resulting in collecting information within seconds.

Creating a Form

Form Builder Interface

Drag and Drop Form Fields

Now let’s dive in and discover more about the different capabilities of the Form Builder manager block:

Versioning forms

Since forms are now attached to a content type and managed as content items in the repository, users will be able to restore a previous version of a form or preview a draft before publishing the form.

Translating forms

Another great benefit of using content types for forms is that editors can now translate their forms into different languages when working on a multilingual site. They will also be able to manage form submissions by language.

Using content relations and other perks from the content repository

Now that forms are content items, editors can create relations between forms and other content items in the repository. It can help see how and where forms are used. This simplifies the process of embedding forms within the online editor. Editors can benefit from all the other perks coming along with the content repository, such as placing a form at multiple locations, using the flex workflow to get approval before publishing a form or publishing a form in the future.

Managing form submissions

We keep form submissions separate from the content repository. The data collected is stored in a separate database table. Submissions data is available to the editor or site administrator from the user interface, on the "submissions" tab, to let him view or download this data. The interface is simple and fast, and makes it handy when working with a lot of forms. In the future, we plan to create more capabilities that will allow editors to search and delete collected data, to improve further the way to support GDPR.

Stored Submissions

Form Submission

What to expect in the future

We are very excited for the upcoming release. We believe that the Form Builder and other features will significantly improve the editorial experience. The Form Builder block will also be a great addition to the page builder which was introduced in v2.2. It is important to remember that this is only the first iteration of this new feature, there are still many things we could improve and new capabilities we could add. In the future we have more updates in the plan, such as, “developing more out-of-the-box GDPR capabilities, providing webhook and potential connectors to integrate the form submissions with 3rd party systems, providing extension and customization capabilities to let users customize the Form Builder to build advanced features such as polls, surveys or others, and to include more fields. If you have any need, opinion or idea, of what would be helpful for you in the future, please drop us a note.

Next week we will provide a sneak peek at the image asset field type that is also expected to be shipped with v2.3. Until then, 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.

09/20/2018 10:05 am   eZ Systems News   Mirror   Link  

Et un peu hors-sujet :

(En plus du flux RSS global, les billets veille et uniquement ceux là sont listés dans le flux RSS correspondant)

09/20/2018 07:07 am   pwet.fr/blog   Mirror   Link