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


@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/ezplatform-demo Nov 1, 2018
2 commits to master
11/01/2018 12:10 am   eZPublishLegacy @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/ezplatform Nov 1, 2018
2 commits to master
11/01/2018 12:10 am   eZPublishLegacy @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/ezoracle Nov 1, 2018
1 commit to master
11/01/2018 12:09 am   eZPublishLegacy @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/UniqueDatatypesBundle Nov 1, 2018
2 commits to master
11/01/2018 12:08 am   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/SyliusDemo Nov 1, 2018
2 commits to master
11/01/2018 12:08 am   eZecosystem @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/ezgmaplocation-ls-extension Nov 1, 2018
2 commits to master
  • ac60e37
    quotes removed from ezgmaplocation.ini.append.php
  • 5ecedf7
    GoogleMaps API Key added for edit and view templates
11/01/2018 12:07 am   eZPublishLegacy @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/Sylius Nov 1, 2018
2 commits to master
11/01/2018 12:07 am   eZecosystem @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/ezgmaplocation Nov 1, 2018
2 commits to master
11/01/2018 12:07 am   eZPublishLegacy @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/repository-forms Nov 1, 2018
2 commits to master
11/01/2018 12:06 am   eZecosystem @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/ezdbintegrity Nov 1, 2018
2 commits to master
11/01/2018 12:06 am   eZPublishLegacy @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/netgensearchandfilterbundle Nov 1, 2018
2 commits to master
11/01/2018 12:05 am   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezstudio-installer Nov 1, 2018
2 commits to master
11/01/2018 12:02 am   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezstudio Nov 1, 2018
2 commits to master
11/01/2018 12:01 am   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezpublish-spi Nov 1, 2018
2 commits to master
11/01/2018 12:01 am   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezpublish-kernel Nov 1, 2018
2 commits to master
11/01/2018 12:00 am   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezpublish-api Nov 1, 2018
2 commits to master
11/01/2018 12:00 am   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezplatform-site-api Nov 1, 2018
2 commits to master
10/31/2018 11:59 pm   eZecosystem @ GitHub   Mirror   Link  
@ezpublishlegacy
ezpublishlegacy pushed to master in ezpublishlegacy/BehatBundle Nov 1, 2018
1 commit to master
10/31/2018 11:59 pm   eZPublishLegacy @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezplatform-demo Nov 1, 2018
2 commits to master
10/31/2018 11:59 pm   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezplatform Nov 1, 2018
2 commits to master
10/31/2018 11:59 pm   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/ezmigrationbundle Nov 1, 2018
2 commits to master
10/31/2018 11:59 pm   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/docker-php Nov 1, 2018
2 commits to master
10/31/2018 11:57 pm   eZecosystem @ GitHub   Mirror   Link  
@ezecosystem
ezecosystem pushed to master in ezecosystem/BehatBundle Nov 1, 2018
1 commit to master
10/31/2018 11:56 pm   eZecosystem @ GitHub   Mirror   Link  

This security advisory fixes a vulnerability in eZ Publish Legacy, and we recommend that you install it as soon as possible if you are using Legacy.

Installations that are using the legacy LDAP login handler or the TextFile login handler in combination with the standard legacy login handler, may in rare cases be vulnerable to a failure of the standard login handler to verify passwords correctly, allowing unauthorised access.

If your installation has never used the LDAP or TextFile login handlers, or never used legacy login at all, then it is not affected. Still, we recommend installing the update, to be on the safe side.

To install, use Composer to update to one of the "Resolving versions" mentioned above, or apply this patch manually:
https://github.com/ezsystems/ezpublish-legacy/commit/13f03a2be6c0ee4d0caaafaef05904ea9b0c4d9d

Have you found a security bug in eZ Publish or eZ Platform? See how to report it responsibly here: https://doc.ez.no/Security

10/31/2018 07:31 am   Security Advisories   Mirror   Link  

Introducing the new online Symfony Certification

We are extremely pleased to announce that the Symfony and Twig certification exams are available online! It means that you can now take the exam from home or from your office! You need your computer, a web cam and a stable Internet connection!

Fabien Potencier introduced the Symfony certification program during his keynote at SymfonyLive Paris 2012 and the first certification session was organized during the conference. At that time, the certification was only organized during official Symfony events. The exam was hold in the conference venue and proctored by the SymfonyLive team. Then different exam sessions were organized during the year at SensioLabs’ offices. The first certification was dedicated to the 2.3 version of the framework.

In October 2013, the Symfony certification was launched worldwide and available in 4,000 physical exam centers to enable much more people to take it. At the same time we introduced the « Advanced level » as an intermediary step before the « Expert level ». Since then, the certification exam was only available in one of the 4,000 worldwide exam centers available.

The Symfony 3 certification was launched in December 2015 and the Twig certification was introduced in June 2016. Lately this year, on March 30th, we introduced the Symfony 4 certification.

We are now moving forward with the certification! We wanted to enable everyone to take any exam no matter where you are in the world 1: as long as you have a computer, a web cam and a stable Internet connection, you can take it. As of today, the certification exam is only available online for any Symfony versions and Twig. You don’t have to go to any exam center, schedule an appointment and physically go there to take the exam. Now it’s faster and easier to take the exam, you can take it from your own home or office.

How do the certification exams work? Any Symfony certification lasts 90 minutes and includes 75 questions divided into 15 topics. Check here the exam topics of all the Symfony certification exams. The Twig certification lasts 60 minutes and includes 45 questions divided into 8 topics. Find here all the exam topics of the Twig certification exam.

Both certifications, the Symfony one and the Twig one, do not include any written answers or lines of code to write. You have 3 types of questions : True / False, Single answer or Multiple choice. Your online certification exam will be proctored during the entire test, the proctor will ask you to test your camera and show the room where you take the exam before starting the test. Don't forget to test and check your camera and network connection before starting!

To book your online certification exam, follow these steps:

1- Buy your certification voucher for Symfony 3 or 4 version or for Twig

2- Create your candidate account or log in to your existing account

3- Activate your voucher to schedule an exam appointment

4- Take the exam online in your own home or office and get your result immediately!

When you buy your certification voucher and activate your voucher, you have to wait for 24 hours before scheduling your exam. You can buy your certification voucher today and become a Symfony or a Twig certified developer tomorrow!

We are proud to count about 400 certified Symfony and Twig developers in our community and we’d like to congratulate again all the certified Symfony and Twig developers! You want to become a Symfony or a Twig certified developer? Book your certification voucher at the unique price of 250 € for Symfony and 149€ for Twig.

If you have any questions regarding the Symfony and Twig certification exams, please read our FAQ section where you’ll find more detailed information. Good luck!

1Exceptions of Cuba, Iran, North Korea, Sudan and Syria due to US Foreign policies.


Be trained by Symfony experts - 2018-11-5 Paris - 2018-11-5 Paris - 2018-11-7 Paris
10/31/2018 04:56 am   Symfony Blog   Mirror   Link  

Contributed by
Kévin Dunglas
in #28533.

Since the introduction of the DotEnv component in Symfony 3.3, we've been working hard to improve the experience of using env vars to configure Symfony apps. In Symfony 4.2, we've added a new loadForEnv() method to allow you define different env vars per environment.

Instead of creating a single .env file at your project's root dir, you can now create one or more env var files. The values for the env var are looked for in the following order:

  • .env + environment name + .local (.env.dev.local, .env.test.local, .env.prod.local). These are the environment-specific settings overridden locally on your machine.
  • .env.local. Used for overriding values on your local machine. This file is loaded for all environments except test.
  • .env + environment name (.env.dev, .env.test, .env.prod). These are the files that define environment-specific settings. Useful for example to override settings like the database connection for tests.
  • .env. Same file as used by current Symfony apps.

We're working on a Symfony Flex recipe to bring this new feature into the full Symfony framework (see symfony/recipes #466). Once merged, you'll need to make the following changes in your app:

  • Rename .env.dist as .env (and commit it to the shared repository).
  • Rename .env as .env.local (and remove it from the shared repository).

Be trained by Symfony experts - 2018-11-5 Paris - 2018-11-5 Paris - 2018-11-7 Paris
10/30/2018 06:46 am   Symfony Blog   Mirror   Link  

Downstream — Trip 7

On the previous trip I walked from to Staines to Teddington Lock. The start of the walk was easy to reach by a direct train from Waterloo, but it does involve a 1 km walk in Teddington. But please do make sure you get out at the right side of the station, otherwise that walk is 2 km ☺.

Day 9 — Teddington Lock to the Golden Jubilee Bridges

I didn't spend a lot of time at Teddington Lock, as I had done so a week earlier. I did notice a few signs saying "Caution! Tidal" as a reminder that the Thames downstream from Teddington Lock is tidal. At the moment it was low tide, although at Teddington that is still a little hard to see due to the presence of Richmond Lock. At Teddington Lock you can chose whether the follow the North or South Bank to the Thames Barrier. As I know that the North Bank's path has a lot of barriers and diversions, especially further East in the City, I chose to walk the Thames Path along the South Bank.

On most of today's walk I was accompanied with rowers on the Thames—for practice, teaching, and races. There must be a rowing club every other kilometre or so. On the way into Richmond the Petersham Hotel looming above the town.

Just beyond Richmond the Thames path passes along the Old Deer Park, where I encountered a Meridian Line. Before Greenwich became the Prime Meridian in 1884, the line at Richmond, which passes through the King's Observatory fulfilled this role for a few centuries.

Not far from the first Meridian Line is Richmond Lock and Footbridge. This is the last lock on the Thames, but it is not a full lock. The lock is accompanied by sluice gates which are open when the tide is at it highest—around two hours on either side of the high tide mark. During that time boats can bypass the lock gates. When the sluice gates are closed, boats have to use the lock to make their way downstream or upstream. When I walked by, the Thames was nearly at its lowest point, and hence, the sluice gates were closed. I didn't see any boats wanting to go through the lock either though.

Beyond the Old Deer Park, the Thames Path passes between the Thames and Kew Gardens. You can unfortunately not see much of it, due the dense vegetation and a wall. You can only really get a glimpse of Kew Palace. Royal Botanic Gardens, Kew, as the gardens are also called, is well worth visiting—especially in Spring.

Now that I passed the last lock at Richmond, there are no further more locks all the way to the North Sea, however, there are plenty of bridges that cross the Thames, both for car, and rail and tube traffic. It became very clear that it was low tide, as there were vast areas of the bottom visible, with plenty of people trying to hunt for treasures.

I had lunch in Putney, at The Duke's Head, where I also had a local brew from nearby Wimbledon brewery. I did pass by the Stag Brewery as well, but that only makes Budweiser, or so their sign says.

After lunch the small deviations from the Thames Part started, as there is a lot of new building works going on in Wandsworth and Battersea. The path wasn't always signed very well, or the signs were outdated due to either new developments, or completed ones with the redirections still in place. Only at the former Battersea Power Station the deviation was a little annoying, as it included going along a busy road.

After going around the SIS building, I was back on familiar territory. I have walked along the Thames East from Lambeth Bridge to Tower Bridge many times. This is also the section that becomes really busy on nice warm autumn days, so my progress was slowed down a little.

A few more bridges later, the Sun started to come closer to setting. I always like this moment in a day, as the light becomes extra yellow, which makes in my opinion for much better photos. You also get to catch the Sun's rays on buildings, such as Lambeth Palace.

Across the river from Lambeth Palace is the Palace of Westminster, where the UK's parliament sits. One of the towers is the Elizabeth Tower, which also hosts the Big Ben bell. The latter is currently out of action and wrapped in scaffolding, as the bell and its tower are being refurbished.

I finished my walk just beyond the London Eye at the Golden Jubilee Bridges. From there on it was a short walk to Waterloo station where I took the tube home. It took however nearly an hour from the bridge to the station, but that was only because I sat down at the Waterloo Tap for a restorative beverage.

Only one more walk to go!


Photos from my Adventure on the Thames Path are available on Flickr, and all videos on Vimeo. You can also see all the photos on a map.

10/30/2018 04:17 am   derickrethans.nl   Mirror   Link  

Contributed by
Nicolas Grekas
in #28970.

The debug:autowiring command displays all classes and interfaces that Symfony developers can use as type-hints for service autowiring. In previous Symfony versions, it looked like this when looking for something specific (e.g. the cache):

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
$ ./bin/console debug:autowiring cache

Autowirable Services
====================

 The following classes & interfaces can be used as type-hints when autowiring:
 (only showing classes/interfaces matching cache)

 --------------------------------------------------
  Psr\Cache\CacheItemPoolInterface
      alias to cache.app
  Psr\SimpleCache\CacheInterface
      alias to cache.app.simple
  Symfony\Component\Cache\Adapter\AdapterInterface
      alias to cache.app
  Symfony\Contracts\Cache\CacheInterface
      alias to cache.app
  Symfony\Contracts\Cache\TagAwareCacheInterface
      alias to cache.app.taggable
 --------------------------------------------------

In Symfony 4.2 we improved this command to make the information easier to understand. The same search for cache now looks like this:

As you can see, the description of what the service does now appears above it. This description is taken from the PHPdoc of the related interface. Also, the autowire by type and name feature introduced in Symfony 4.2 is displayed (e.g. CacheInterface $cacheApp).


Be trained by Symfony experts - 2018-11-5 Paris - 2018-11-5 Paris - 2018-11-7 Paris
10/29/2018 07:19 am   Symfony Blog   Mirror   Link  

This week, development activity focused on polishing the upcoming Symfony 4.2 version, which will be released in 5 weeks. We improved performance of service discovery for large applications and we optimized the way env vars are exported. We also improved the log filter in the Symfony profiler to support filtering by multiple criteria.

Symfony development highlights

This week, 71 pull requests were merged (40 in code and 31 in docs) and 31 issues were closed (18 in code and 13 in docs). Excluding merges, 35 authors made 3,601 additions and 2,063 deletions. See details for code and docs.

2.8 changelog:

  • 5c3d826: [FrameworkBundle] fixed broken exception message

3.4 changelog:

  • c2478d4: [Intl] updated the ICU data to 63.1

4.1 changelog:

  • 3dda3cc: [HttpKernel] clean away the NO_AUTO_CACHE_CONTROL_HEADER if there is no session
  • 76b2541: [Messenger] send using the routing_key for AMQP transport

Master changelog:

  • 426cf81: [Serializer] refactor and uniformize the config by introducing a default context
  • 60394bc: [Config] fixed slow service discovery for large excluded directories
  • 717ff2d: [DependencyInjection] optimized exporting variables
  • 07c46a2: [WebProfilerBundle] removed application name
  • 01dfca1: [WebProfilerBundle] added a channel log filter
  • 9d3621e: [OptionsResolver] trigger deprecation only if the option is used
  • a33725f: [FrameworkBundle] deprecated support for legacy directories in Translation commands

Newest issues and pull requests

They talked about us

Upcoming Symfony Events

Call to Action


Be trained by Symfony experts - 2018-11-5 Paris - 2018-11-5 Paris - 2018-11-7 Paris
10/28/2018 03:48 am   Symfony Blog   Mirror   Link