23 Feb 2018

feedeZ News

The Week in Review: eZ Platform 1.13.1, Community Updates and More

News

eZ Platform 1.13.1 Released

eZ Platform 1.13.1 has been released. This is an update for eZ Platform 1.13 LTS. This release comes with many bug fixes and improvements, including to the PlatformUIBundle, content-on-the-fly prototype bundle and ezplatform-http-cache. For a full overview, check the release notes on GitHub. Note that there is also a 1.13.1.1 release.

eZ Platform Enterprise Edition is also available as 1.13.1 release. Release notes are also available on GitHub. For future releases, check our roadmap.

Community Updates

The eZ Community Board is preparing the renewal of its Board members. Keep an eye on ezplatform.com for a blog post next week announcing when nominations will open. Some of the benefits of joining the Community Board are growing your leadership skills, and also being part of the decision making process and governance of our community. If you are curious about our mission and goal, or governance of the community, read the governance framework.

A quick reminder that we launched a new and dedicated forum for eZ Platform at https://discuss.ezplatform.com. Why a new forum? We launched this new forum for several reasons. The most important one is to preserve our knowledge around eZ Platform and to make it available to everyone. Join us, share your knowledge, and ask your questions to fellow eZ Platform developers on https://discuss.ezplatform.com!

We ran a survey a while ago asking our community if they would be interested in a hackathon during this year's eZ Conference. With the response we got, we decided to not organize a hackathon this year and focus our resources to give you an excellent experience during the conference itself.

In Other News:

Resources

eZ Platform Cloud Explainer Video

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

Social Media

GDPR is around the corner but there's no need to panic! Join the webinar by @eZSystems and hear how to get ready for GDPR. https://t.co/LlTPPFNLMm pic.twitter.com/hx3r1wh1en

- Exove (@exove) February 20, 2018

Early Bird tickets for @WebSummerCamp are selling out https://t.co/z4ReKSsEQ9 We have some great speakers announced, CfP is still open, and if you have any questions, contact me #websc #ux #userresearch #php #symfony #ezplatform #javascript

- Maja Nebes (@Maja_Nebes) February 21, 2018

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: Martin Kleppe, CC)

23 Feb 2018 6:52pm GMT

14 Feb 2018

feedshare.ez.no > All forums (topics and replies)

Re: still login after logout - production environement

Hi,
I seem to have the same problem as the one you mention.
What did you do to fix it?
Thanks.

14 Feb 2018 9:00am GMT

Re: urlalias lowercase transform equivalent

This command seems to have been disappeared on the lasted ezplaform release (2.x)

14 Feb 2018 2:14am GMT

12 Feb 2018

feedshare.ez.no > All forums (topics and replies)

Re: Dynamically log user

The API has changed (eZ5.4). The token is not handled by the same service :

12 Feb 2018 3:15pm GMT

09 Feb 2018

feedeZ News

The Week in Review: Symfony Thanks, Translatable SiteAccess Names and More

News

eZ Connector Marketplace Expansion Program

The eZ Connector initiative was announced at the Barcelona Partner Meeting. This will consist of two programs: eZ Connector Competition and Build with eZ. When you join the competition to build a connector, you're in the running for a chance to win USD $2,500.

More information can be found in the official announcement, and you can register on our site.

Should Siteaccess Names be Translatable?

Sylvain Guittard from Product Management posted a question on our forum: Should SiteAccess names be translatable or not? "We plan to introduce human readable SiteAccess Names into the product. The main goal is to replace the SiteAccess code by a name easier to read, understand for the editor." If you have an opinion on this, please leave your feedback.

WSC18 Call for Papers

Web Summer Camp 2018 call for papers is officially open. "You have an interesting topic in the area of PHP, Symfony, eZ Platform, JavaScript, user experience, user research, information architecture, or user interface design?" Submit proposal by March 31st at 2018.websummercamp.com

Symfony Thanks

Javier Equiluz submitted an interesting pull request to incorporate Symfony Thanks to our code. Symfony Thanks is a Composer plugin to give thanks to your PHP dependencies in the form of a GitHub Star. When this makes it into the eZ Platform repositories, I hope as a community member you will use it to say thanks and recognize everyone's work.

In Other News:

Resources

New Community Bundles

The Community has contributed a few new Bundles this week. The first one is by Emmanuel Drouet through his "One Monday One Bundle" effort. His Bundle is about indexing binary files associated with eZ Content in SolR search index. Watch the video on YouTube or get the Bundle from Packagist.

The second Bundle is by Felix Laate called CSVImportExportBundle. It's an eZ Platform v2 bundle providing basic import and export capabilities for the admin interface. You can find the Bundle on GitHub.

Question of the Week

This week Ivo Luka─Ź posted the question: Going underscore with nice urls, by default or not? Join that discussion on our forum.

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

Social Media

[Webinar] #GDPR Is Around the Corner - Don't Panic!
Hear clear and practical advice that will get you ready for GDPR.
RSVP TODAY - Tue, March 6 - 10am EThttps://t.co/6eZhU3Ysxc pic.twitter.com/MKjXyvTcfx

- eZ Systems (@eZSystems) February 8, 2018

Working towards new business together with our long-term partners and friends from @eZSystems . pic.twitter.com/TaypAClKvh

- Kaliop Poland (@KaliopPoland) February 8, 2018

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: Anders Adermark, CC)

09 Feb 2018 5:33pm GMT

31 Jan 2018

feedeZ News

eZ Connector Marketplace Expansion Program

The eZ Connector initiative will consist of two programs: eZ Connector Competition and Build with eZ. These programs are a great opportunity for partners, developers, and third-party software vendors to build connectors that extend our content management system's capabilities. Let's dive deeper to understand these different programs, and how you can participate and benefit from these two exciting opportunities.

eZ Connector Competition

This competition is a fun opportunity that we believe will drive innovation and accelerate the growth of our connector marketplace. The first competition kicks off on February 1! You can build a connector with any application or service, the only thing that matters is that you register for the competition by providing us with your information and a summary of the connector you are entering in the competition. During the competition you will have one whole month to build your connector and, of course, you are free to bring a project already started prior to the competition-it does not have to be new work, just new to us here at eZ.

By 23:59 EST on February 28, 2018, you must deliver your final entry.

A few requirements that are worth noting: the connector should be open source so that users have the freedom to run and modify the software. It should follow the GPL license version 2, and should grant eZ Systems AS with a shared copyright just like eZ shares copyright through a Contribution License Agreement with contributors. To evaluate the work of the participant, we request that you share the results along with a blog post. The blog post should also include a demo video explaining the connector and its functionality. We will publish the blog post both on ez.no and ezplatform.com.

On March 1, the eZ Product Team will evaluate all submitted connectors and decide on the winner. The winner will be announced at the end of the first week of March, 2018. We recognize that building a connector takes a significant amount of resources. Therefore, the winner will be rewarded with a check for USD $2,500, and will receive an opportunity to advance to the Build with eZ challenge. However, all of the connectors that take part in the competition will be featured on the ez.no website, and can take advantage of our various co-marketing initiatives (webinars, events, and blog posts) that will accompany the competition.

Build with eZ

Build with eZ is the second phase of our connector program. In this part of the program, the winner of the competition will be awarded a contract to build an additional connector together with our team. During this phase, the connector you create will be selected and designed together with the eZ product team. The participant will have one month to deliver, and will receive an additional USD $5,000 for services performed in building the new connector. eZ seeks to work side-by-side with the winning vendor and will provide resources and guidance throughout the development process. Just as with the eZ Connector Competition, this new connector will need to be open source and licensed under GPL version 2. As this connector is promoted as "Build with eZ", we require this connector's code base to be hosted by the eZ organization on GitHub (https://github.com/ezsystems), and that eZ owns the copyright, as a regular contribution following the eZ Contribution License Agreement (CLA).

We believe that these two programs will help us accelerate the growth of our connector directory. Don't miss out on this great opportunity to contribute to the eZ ecosystem and partake in extending eZ Platform's capabilities.

REGISTER HERE NOW

31 Jan 2018 9:34pm GMT

12 Nov 2011

feeddrupal.org aggregator

Drupal core announcements: Core's directory structure reorganized

As of 2011-11-01, most files in Drupal core live in a 'core' subdirectory. We did this to make it easier to tell what's core vs. site-specific code (e.g. to discourage people from installing modules into the 'modules' subdirectory in the webroot) and to make it easier to upgrade to newer versions. See #22336: Move all core Drupal files under a /core folder to improve usability and upgrades for the full story and/or the API change record: Most Drupal core files now live in a "core" subdirectory.

One of the only drawbacks of this change is that bug fix patches for Drupal 7 no longer apply to Drupal 8 without being rerolled. However, generally it's easy re-roll a patch in this situation. xjm wrote up detailed instructions for re-rolling patches here: http://xjm.drupalgardens.com/blog/rerolling-drupal-8-core-patches

A more simple (but less effective in some cases) way to re-roll was written up by scor over at comment #306 of the original issue.

Please don't reopen the original issue with follow-up suggestions or bug reports -- those belong in new issues.

Core

12 Nov 2011 8:39am GMT

11 Nov 2011

feeddrupal.org aggregator

Morbus Iff: Achievements 7.x-1.4: Using print render($a) and render arrays

The Drupal Achievements module offers the ability to create achievements and badges similar to systems seen on Xbox 360, Playstation 3, Foursquare, Gowalla, GetGlue, and more. For a Drupal site, this could mean commenting a certain number of times, starting a forum topic, visiting the site every day of the week, or anything else that can be tracked and coded. The recently released 7.x-1.4 update focuses on changes that make theming easier.

In my first post about #theme_wrappers, we fixed up bad HTML in #prefix and #suffix to give themers an easier time. This post, about render arrays, is no different. In fact, most of the tweaks in Achievements 7.x-1.4 are not very obvious, or even useful, to module developers. It's only when you sit down with a themer who wants to change the entire look and feel that you realize your carefully-coded "looks good in Garland!" output is not as useful as you think.

Why render arrays are better

You've probably read about render arrays in the Drupal Developer's Handbook already, but the documentation doesn't really give a developer a decent reason why they should use them. It also doesn't talk about $content or splitting your variables into "data" and "presentation". I'll cover both below.

First, let's look at the wrong approach:

    $build['image'] = theme('image', array('path' => array('misc/druplicon.png')));

If this was passed to a theme file, the themer would simply print $image; and be done with it. The themer could even link the image if they wanted, but they wouldn't be able to add any classes or attributes to the image, since calling theme() directly always returns rendered HTML. Here's what the above looks like as a render array:

    $build['image'] = array(
      '#theme' => 'image',
      '#path' => 'misc/druplicon.png',
    );

To get this to display in the theme, we'd use print render($image); instead. In this case, the theme is telling Drupal to render the HTML, not your module. Why is this important? Ignoring the nebulous "I CAN'T ADD CSS CLASSES, SNIFF!" themer lament, consider the following small tweak to our original bad example:

    $image = theme('image', array('path' => array('misc/druplicon.png')));
    $build['image'] = l($image, 'node', array('html' => TRUE));

Here, we've simply added a link to our dummy image and the themer gets the fully rendered HTML to print out. Everything is toasty... unless the client or theme doesn't want or need the image to be linked. The themer now has no choice: they either have to use a regular expression to strip out the unwanted link or they have to recreate the $image variable in his own, well, image. Not only is that fragile (it's essentially copying module code to the theme and that code might change in a future version), but it also mixes too much logic with too little presentation. If the image's path isn't available to the theme as its own variable (it isn't, in the above example), the themer will still have to parse your rendered HTML to find the image's path first. Yuck.

Let's convert the above to a render array:

    $build['image'] = array(
      '#theme' => 'image_formatter',
      '#item' => array(
        'uri' => 'misc/druplicon.png',
      ),
      '#path' => array(
        'path' => 'node',
        'options' => array('html' => TRUE),
      ),
    );

Now, if the themer wants to remove the link, they can listen in a theme override, a preprocess, or even the dreaded hook_page_alter() and simply unset($variables['image']['#path'])'. No more link, without duplicating any upstream code or recreating things themselves. This is a real-life example, by the way - I just finished an optional submodule of Achievements which removes all links to the default leaderboards. I couldn't have easily done that if I used either of the link approaches below:

    $build['achievement_title'] = l($title, 'path/to/achievement');
    $build['achievement_title']['#markup'] = l($title, 'path/to/achievement');

But with the following render array:

    $build['achievement_title'] = array(
      '#type' => 'link',
      '#title' => $title,
      '#href' => 'path/to/achievemnt',
    );

I can make those links linkless:

  unset($variables['achievement_title']['#type']);
  $variables['achievement_title']['#markup'] = $variables['achievement_title']['#title'];

Data, presentation, and $content['a'] not $a

This doesn't mean that every single variable you pass to the theme should be a render array: there's clearly a difference between variables that represent data (an image path, the $node or $user object, a Unix timestamp, etc.) and variables that are meant for presentation (the linked image, the node's filtered teaser, a human-readable date, etc.).

There's a move afoot to more clearly indicate these two types by using a $content variable as a container for all the supplied render arrays. Drupal core does this in some places (node.tpl.php, for one), but not all, and it's slowly becoming a preferred practice in the theming world. Another benefit is the ability to use print render($content);, which says "render everything I haven't already rendered", allowing themes to display things that they, or the parent module, might not know about (new data added by a third party module in a preprocess, etc.). I've yet to implement this in Achievements, but I'll likely get there for the next release.

11 Nov 2011 6:57pm GMT

Trellon.com: Looking ahead to Drupalcon Denver

With each week that DrupalCon Denver is coming nearer, the excitement in the community grows. At Trellon, we're not immune to that excitement, and we're proud to be a Platinum sponsor of Drupalcon Denver. We're looking forward to seeing members of the Drupal community there, both old friends and new. We're excited about the opportunity that Drupalcons give us not only to learn more about the direction of Drupal, but to help shape it. We're eager to learn what new and exciting things people around the world have been doing with Drupal.

read more

11 Nov 2011 6:00pm GMT

09 Nov 2011

feedPlanet Zope.org

Updated MiniPlanet, now with meta-feed

My MiniPlanet Zope product has been working steady and stable for some years, when suddenly a user request came along. Would it be possible to get a feed of all the items in a miniplanet? With this update it became possible. MiniPlanet is an old-styl...

09 Nov 2011 9:41am GMT

07 Nov 2011

feedPlanet Zope.org

Welcome to Betabug Sirius

It has been quite some time that I announced_ that I'd be working as a freelancer. Lots of stuff had to be done in that time, but finally things are ready. I've founded my own little company and set up a small website: Welcome to Betabug Sirius!

07 Nov 2011 9:26am GMT

03 Nov 2011

feedPlanet Zope.org

Assertion helper for zope.testbrowser and unittest

zope.testbrowser is a valuable tool for integration tests. Historically, the Zope community used to write quite a lot of doctests, but we at gocept have found them to be rather clumsy and too often yielding neither good tests nor good documentation. That's why we don't use doctest much anymore, and prefer plain unittest.TestCases instead. However, doctest has one very nice feature, ellipsis matching, that is really helpful for checking HTML output, since you can only make assertions about the parts that interest you. For example, given this kind of page:

>>> print browser.contents
<html>
  <head>
    <title>Simple Page</title>
  </head>
  <body>
    <h1>Simple Page</h1>
  </body>
</html>

If all you're interested in is that the <h1> is rendered properly, you can simply say:

>>> print browser.contents
<...<h1>Simple Page</h1>...

We've now ported this functionality to unittest, as assertEllipsis, in gocept.testing. Some examples:

self.assertEllipsis('...bar...', 'foo bar qux')
# -> nothing happens

self.assertEllipsis('foo', 'bar')
# -> AssertionError: Differences (ndiff with -expected +actual):
     - foo
     + bar

self.assertNotEllipsis('foo', 'foo')
# -> AssertionError: "Value unexpectedly matches expression 'foo'."

To use it, inherit from gocept.testing.assertion.Ellipsis in addition to unittest.TestCase.


03 Nov 2011 7:19am GMT

13 Oct 2011

feedshare.ez.no > Articles and Tutorials

Building native mobile applications with the eZ Publish REST API

eZ Publish is a Web Content Management System that provides a platform to publish content via any channel. Its powerful presentation engine enables you to create websites and pages that display your content in a variety of renderings. Its powerful API directly and simply integrates your content with any web-enabled application on any device, such as the iPad, iPhone, or an Android device, without ever interfering with, or impacting the platform itself.

At the end of this tutorial, you will have learnt the basics of mobile application development for both iOS and Android platforms, consuming content from eZ Publish. CMS-side adjustments for the mobile channel will be acquired too. This cheatsheet will help you leverage the multichannel capabilities of eZ Publish, and its REST API in future projects, in a more systematic fashion.

13 Oct 2011 2:21pm GMT

16 Aug 2011

feedshare.ez.no > Articles and Tutorials

Image Maps in ezwebin Banners

Beginners guide for learning how to use image maps in the ezwebin extension.

16 Aug 2011 12:40pm GMT

07 Jul 2011

feedshare.ez.no > Articles and Tutorials

Building mobile browser and hybrid applications with eZ Publish

eZ Publish is a Web Content Management System that provides a platform to publish content via any channel. Its powerful presentation engine enables you to create websites and pages that display your content in a variety of renderings. Its powerful API directly and simply integrates your content with any web-enabled application on any device, such as the iPad, iPhone, or an Android device, without ever interfering with, or impacting the platform itself.

At the end of this tutorial, you will have learnt the basics of mobile application development for both iOS and Android platforms, consuming content from eZ Publish. CMS-side adjustments for the mobile channel will be acquired too. This cheatsheet will help you leverage the multichannel capabilities of eZ Publish, and its REST API in future projects, in a more systematic fashion.

07 Jul 2011 1:29pm GMT